Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Jan 2001 06:59:25 -0800
From:      Julian Elischer <julian@elischer.org>
To:        Thierry Herbelot <thierry.herbelot@free.fr>
Cc:        Wes Peters <wes@softweyr.com>, net@freebsd.org
Subject:   Re: Problems with VLAN and natd.
Message-ID:  <3A51ECCD.CD34B446@elischer.org>
References:  <200101020501.AAA58976@tsunami.waterspout.com> <3A517429.91B2F251@softweyr.com> <3A517522.EEF1A4B9@free.fr> <3A517A48.A0BD6439@softweyr.com> <3A517F87.B130AC0F@free.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
Thierry Herbelot wrote:
> 
> Wes Peters wrote:
> >
> > Thierry Herbelot wrote:
> > >
> > > Wes Peters wrote:
> > > >
> > > [SNIP]
> > > >
> > > > Doing link-layer encapsulation modules is really not very difficult.
> > > > I've written pretty much the full complement, covering ethernet (10,
> > > > 100, and 1000), FDDI/CDDI, token ring, ATM, and Frame Relay.  (Chuck,
> > >
> > > What about a netgraph-enabled ATM NIC driver ? (this seems the missing
> > > piece to get bridged Ethernet over RFC1483 encapsulation on ATM)
> >
> > If the top of all the network interface drivers is a netgraph connection,
> 
> we agree on it : FreeBSD needs a netgraphified hfa(4) : I've seen one or
> two trys to get it done (the trouble is not many of our commiters know
> well enough both ATM and netgraph to actually do it, and the ones who do
> are so busy with other, more interesting challenges)
> 
>         TfH
> 
> PS : at one time, I would even have tried getting some money from my
> company to pay a consultant do it (there are not many of them in France,
> though)

If I could get together with someone who knows the ATM code and can test it,
I'd LOVE to help netgraphify the ATM interfaces and protocols.
It's really quite easy. (and can be made to co-exist with exisiting interfaces
(see the current ethernet hooks)

> 
> > any encapsulation should be straightforward.  In the Xylan switch, we
> 
> At work, I'm using a 1100 LSS : is it the same as the one you worked on
> ?
> 
> > actually did the conversion on the outbound network interface module,
> > so the packet was never converted unless it had to be.  We could mimic
> > that behavior, assuming the output device would check the packet to
> > see if it needs to be converted, and if so call a module to strip it
> > down to the bare packet, then another to add the correct encapsulation.
> >
> > --
> >             "Where am I, and what am I doing in this handbasket?"
> >
> > Wes Peters                                                         Softweyr LLC
> > wes@softweyr.com                                           http://softweyr.com/
> 
> --
> Thierry Herbelot
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-net" in the body of the message

-- 
      __--_|\  Julian Elischer
     /       \ julian@elischer.org
    (   OZ    ) World tour 2000
---> X_.---._/  from Perth, presently in:  Budapest
            v


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A51ECCD.CD34B446>