The same way that the hexdump decodor knows anything about the
encapsulation type of the packet --- it would have to be marked as such
in the hex dump via manual editing.
--gilbert
----- Original Message -----
From: "Ashok Narayanan" <ashokn@xxxxxxxxx>
To: "Gilbert Ramirez" <gram@xxxxxxxxxx>
Cc: <ethereal-dev@xxxxxxxxxxxx>
Sent: Thursday, April 26, 2001 4:17 PM
Subject: Re: [Ethereal-dev] Can we decode hex dumps?
>
> Yeah, but how does the hexdump decoder know that the packet is RSVP? Or,
if a
> protocol registers itself with an encap, can we then select it directly
from
> the "decode as" menu?
>
> -Asho
>
> On Thu, 26 Apr 2001 16:12:06 -0500, "Gilbert Ramirez" <gram@xxxxxxxxxx>
wrote:
>
> >
> > ----- Original Message -----
> > From: "Ashok Narayanan" <ashokn@xxxxxxxxx>
> > To: "Gilbert Ramirez" <gram@xxxxxxxxxx>
> > Cc: <ethereal-dev@xxxxxxxxxxxx>
> > Sent: Thursday, April 26, 2001 3:28 PM
> > Subject: Re: [Ethereal-dev] Can we decode hex dumps?
> >
> >
> > >
> > > Another question: Is it possible to directly give a packet to Layer 3
or
> > even
> > > to a protocol? I'm thinking of a scenario where I have got a hex dump
of a
> >
> > > Thoughts? Alternatives?
> >
> > Provide a WTAP_ENCAP_* type for every protocol, and have every
> > protocol register themselves with the "wtap_encap" dissector.
> > In your example, wiretap would return encapsulation type
> > WTAP_ENCAP_RSVP, and the rsvp dissector would have
> > registered itself with the wtap_encap dissector table.
> >
> > --gilbert
>
>
>
>
>
> --- Asok the Intern ----------------------------------------
> Ashok Narayanan
> IOS Network Protocols, Cisco Systems
> 250 Apollo Drive, Chelmsford, MA 01824
> Ph: 978-244-8387. Fax: 978-244-8126 (Attn: Ashok Narayanan)
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
