Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-31 Thread Kevin A. Noll
-1936 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joerg Mayer Sent: Wednesday, May 30, 2007 10:42 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode... On Wed, May 30, 2007 at 09:17

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-30 Thread Kevin A. Noll
port list for Wireshark Subject: Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode... On Wed, May 30, 2007 at 09:17:59AM -0400, Kevin A. Noll wrote: > I've been compiling with the 0.99.5 tarball. > > I appreciate any suggestions anyone may have. - Terminate all value string

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-30 Thread Joerg Mayer
On Wed, May 30, 2007 at 09:17:59AM -0400, Kevin A. Noll wrote: > I've been compiling with the 0.99.5 tarball. > > I appreciate any suggestions anyone may have. - Terminate all value strings with an entry of { 0, NULL }, wlccp_tlv_typeIDs, wlccp_aaa_msg_type_vs and others lack this. - You do a

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-29 Thread Joerg Mayer
On Tue, May 29, 2007 at 09:54:56AM -0400, Kevin A. Noll wrote: > I am building on Suse Linux. Me too. > I'd be happy to post the entire dissector and a sample capture file if > someone has the time to look at it. Yes please as long as the capture file isn't excessivly large. Ciao Joerg --

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-29 Thread Kevin A. Noll
TED] On Behalf Of Jeff Morriss Sent: Monday, May 28, 2007 9:48 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode... Kevin A. Noll wrote: > I am progressing on my updated WLCCP dissector, but I've run into > another >

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-28 Thread Jeff Morriss
Kevin A. Noll wrote: > > I think I've figured out that I am getting the DISSECTOR_ASSERT because of > something related to the dissector being near the end of the tvbuff. > However, I've tried several things to try to debug exactly what occuring, > but I can't get the error to go away. > > This

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-28 Thread Jeff Morriss
Kevin A. Noll wrote: > I am progressing on my updated WLCCP dissector, but I've run into another > (amateur) issue. This protocol allows TLVs to be tacked on to the end of a > packet with no indication of how many or how long they are until you start > reading the TLVs and iterate through them un

Re: [Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-28 Thread Kevin A. Noll
fix my error. Thanks! --kan-- -- Kevin A. Noll, KD4WOZ CCIE, CCDP Versatile, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin A. Noll Sent: Sunday, May 27, 2007 11:39 PM To: 'Developer support list for Wireshark' Subject: [

[Wireshark-dev] DISSECTOR_ASSERT_NOT_REACHED in WLCCP decode...

2007-05-27 Thread Kevin A. Noll
I am progressing on my updated WLCCP dissector, but I've run into another (amateur) issue. This protocol allows TLVs to be tacked on to the end of a packet with no indication of how many or how long they are until you start reading the TLVs and iterate through them until you get to the end of the