On Wed, Oct 20, 1999 at 05:22:32PM -0500, Guy Harris wrote:
>
>
> > I'm also not sure this is how y'all want to be handling nested protocol
> > stacks. I have ethertype() call dissect_vlan(), and dissect_vlan calls
> > ethertype() again after it pulls the VLAN header and info off.
>
> Well, there's the discussion of tunneling that we've been having, but
> I'm not sure what other issues there are - I guess you could consider
> having "ethertype()" special-case ETHERTYPE_VLAN, and dissect the VLAN
> info and process the encapsulated protocol directly, but I'm not sure
> what that buys you.
Just thinking about the proto_tree stuff, as Jun-ichiro and I and others
were discussing, it would be best to have the user decide how he
wants to view the data. Does he want the second ethertype() to be on-par
with the first, or a child of vlan()? Let him decide, and be able to change
it at whim.
I haven't put in code to handle this, but I want to work on it after 0.7.6
is released. Until them, you can decide how you want to represent
the VLAN data.
--gilbert
