[ramesh kandula <ramesh_v_kandula@xxxxxxxxx>]

I have been using ethereal for over a year now. Made
some modofications to ethereal for a startup. Anyway I
am jobless for the next two weeks. I would like to
help in the current ethereal development. Please, let
me know how I can help.

Thanks,
Ramesh. 
--- ethereal-dev-request@xxxxxxxxxxxx wrote:
> Send Ethereal-dev mailing list submissions to
> 	ethereal-dev@xxxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web,
> visit
> 
>
http://www.ethereal.com/mailman/listinfo/ethereal-dev
> or, via email, send a message with subject or body
> 'help' to
> 	ethereal-dev-request@xxxxxxxxxxxx
> 
> You can reach the person managing the list at
> 	ethereal-dev-owner@xxxxxxxxxxxx
> 
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of Ethereal-dev digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: New dissector: IAX2 (Inter-Asterisk
> eXchange 2)	VoIP
>       protocol support (Guy Harris)
>    2. Re: patch for wiretap lib: read EyeSDN USB S0
> (Guy Harris)
>    3. Re: Highlight the correct bytes in byte view
> for	Manufacturer
>       info Pa cket-h245.c , -h225.c ( Patch ) (Guy
> Harris)
>    4. Re: SoulSeek Dissector breaks MSVC build (Guy
> Harris)
>    5. RE: GSM MAP Operation Code TAP (Michael Lum)
>    6. Re: New postgresql dissector (Ober Heim)
>    7. Proposal: Menu structure for protocol specific
> things
>       (Ulf Lamping)
>    8. Re: New postgresql dissector
> (jaime.fournier@xxxxxxxx)
>    9. Re: New postgresql dissector (Edwin Calo)
>   10. Change of email address (Andreas Sikkema)
>   11. Re: New postgresql dissector (Joerg Mayer)
> 
> 
>
----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 13 Feb 2004 11:16:51 -0800
> From: Guy Harris <guy@xxxxxxxxxxxx>
> Subject: Re: [Ethereal-dev] New dissector: IAX2
> (Inter-Asterisk
> 	eXchange 2)	VoIP protocol support
> To: Ethereal development <ethereal-dev@xxxxxxxxxxxx>
> Message-ID:
> <2DB8E38E-5E59-11D8-B229-000A958097E4@xxxxxxxxxxxx>
> Content-Type: text/plain; charset=US-ASCII;
> format=flowed
> 
> 
> On Feb 13, 2004, at 3:27 AM, Alastair Maw wrote:
> 
> > Another small fix, to make DTMF digit recognition
> work properly. 
> > Please find attached.
> 
> I checked in the version you sent me privately, as
> it appeared to be a 
> superset of this patch.
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 13 Feb 2004 11:28:08 -0800
> From: Guy Harris <guy@xxxxxxxxxxxx>
> Subject: Re: [Ethereal-dev] patch for wiretap lib:
> read EyeSDN USB S0
> To: Ethereal development <ethereal-dev@xxxxxxxxxxxx>
> Message-ID:
> <C136DB1A-5E5A-11D8-B229-000A958097E4@xxxxxxxxxxxx>
> Content-Type: text/plain; charset=US-ASCII;
> format=flowed
> 
> 
> On Feb 13, 2004, at 6:22 AM, Rolf Fiedler wrote:
> 
> > From: Guy Harris <guy@xxxxxxxxxxxx>
> >> eyesdn.c:86: warning: `eyesdn_rec_magic' defined
> but not used
> >
> > Yes, the magic for a record is only 0xff (single
> byte) and I must have 
> > put that
> > in literally without referencing the array.
> 
> OK, I've gotten rid of that variable (and some
> unused #defines).
> 
> > No, that should be an array of unsigned char. I
> did not notice this 
> > during testing,
> > it is a leftover from the toshiba wiretap module
> that I started from.
> > Maybe I was lucky/unlucky to not have byte with
> most significant bit  
> > set during my tests.
> > Thanks for finding this.
> > Should I fix it or is it already done in CVS?
> 
> It's already fixed in CVS.
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 13 Feb 2004 11:34:00 -0800
> From: Guy Harris <guy@xxxxxxxxxxxx>
> Subject: Re: [Ethereal-dev] Highlight the correct
> bytes in byte view
> 	for	Manufacturer info Pa cket-h245.c , -h225.c (
> Patch )
> To: Ethereal development <ethereal-dev@xxxxxxxxxxxx>
> Message-ID:
> <92E9E964-5E5B-11D8-B229-000A958097E4@xxxxxxxxxxxx>
> Content-Type: text/plain; charset=US-ASCII;
> format=flowed
> 
> 
> On Feb 13, 2004, at 4:51 AM, Anders Broman (TN/EAB)
> wrote:
> 
> > Highlight the correct bytes in byte view for
> Manufacturer info in 
> > Packet-h245.c ,-h225.c
> 
> Checked in.
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 13 Feb 2004 11:37:36 -0800
> From: Guy Harris <guy@xxxxxxxxxxxx>
> Subject: Re: [Ethereal-dev] SoulSeek Dissector
> breaks MSVC build
> To: Ethereal development <ethereal-dev@xxxxxxxxxxxx>
> Message-ID:
> <13D29C7F-5E5C-11D8-B229-000A958097E4@xxxxxxxxxxxx>
> Content-Type: text/plain; charset=US-ASCII;
> format=flowed
> 
> 
> On Feb 12, 2004, at 11:45 PM, Kendy Kutzner wrote:
> 
> > On 2004-02-12T13:01:46-0800, Guy Harris wrote:
> >> Checked in, with a change to use "tvb_memdup()"
> to make a copy of the
> >> compressed data (so that, if not all the data is
> present, an exception
> >> is thrown before anything is allocated).
> >>
> >> Is that copy required?
> >
> > On x86, IMHO it isn't. On other platforms, I'm not
> sure. Pointer
> > alignment?
> 
> As far as I know, the buffer handed to
> "uncompress()" isn't required to 
> be aligned - it's just a sequence of bytes.
> 
> > Byte ordering?
> 
> It's just a sequence of bytes, so that shouldn't
> matter - and copying 
> it wouldn't help in any case.
> 
> > Are the tvb guaranteed to be contiguous?
> 
> "tvb_get_ptr()" returns a pointer to a contiguous
> chunk of data with 
> the specified length.
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Fri, 13 Feb 2004 08:27:27 -0800
> From: "Michael Lum" <mlum@xxxxxxxxxxxxx>
> Subject: RE: [Ethereal-dev] GSM MAP Operation Code
> TAP
> To: "'Guy Harris'" <guy@xxxxxxxxxxxx>,	"'Ethereal
> development'"
> 	<ethereal-dev@xxxxxxxxxxxx>
> Message-ID:
> <001101c3f24e$4cb706e0$880810ac@xxxxxxxxxxxxx>
> Content-Type: text/plain;	charset="US-ASCII"
> 
> I'm sorry Guy, it's related to the environment.
> 
> The companies development machines don't have all of
> the 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html