FreeLists / openbeosnetteam / [openbeosnetteam] Re: PPP API

["Philippe Houdoin" <philippe.houdoin@xxxxxxx>]

Nathan anwser:
> > For input, the Net::Layer::ParentType() give the layer name from 
> > which 
> > we accept (or is it only "expect" here?)
> > input, like in your sample ppp/pppoe layer, which return 
> > ParentType() 
> > of "ethernet/*"?
> 
> This is an old version of the architecture, which let you supply, in 
> ParentType() a regex for the sorts of things you want under you. I 
> prefer the above-mentioned naming architecture to the way it exists 
> in 
> the code I submitted.

Oh, okay.
But, in this design, how input packets are demuplexed?
Your sample code seems to imply that each above layer will be hand the 
packet.
For example:

If it's a TCP packet:
ethernet/vt86c100/0 -> ip/ethernet , arp/ethernet, ppp/ethernet 
ip/ethernet -> icmp/ip, udp/ip, tcp/ip
tcp/ip -> socket/tcp

If it was a TCP packet sent thru a PPPoE connection:
ppp/ethernet -> discovery/ppp, lcp/ppp, ip/ppp
ip/ppp -> icmp/ip, udp/ip, tcp/ip
tcp/ip -> socket/tcp

Something similar?

I like this stack assembly design, but I'm worried about performance, 
due to time waste in 
non-concerned layer(s) at each layer level.

-Philippe

--
Fortune Cookie Says:

Arbitrary systems, pl.n.:
        Systems about which nothing general can be said, save "nothing
general can be said."