tunneling L2 tagged traffic over IP
Ian Smith
smithi at nimnet.asn.au
Tue Apr 28 13:01:55 UTC 2015
In freebsd-questions Digest, Vol 569, Issue 1, Message: 10
On Mon, 27 Apr 2015 15:33:55 +0600 Victor Sudakov <vas at mpeks.tomsk.su> wrote:
> Victor Sudakov wrote:
> > Nikos Vassiliadis wrote:
> > > >
> > > > Could you advise a solution for tunneling L2 (Ethernet) traffic over IP?
> > > >
> > > > There is a solution in bridge(4) using the EtherIP protocol, but it
> > > > works with untagged frames only. I need to tunnel 802.1q tagged frames
> > > > as well.
> > > >
> > > > Any ideas?
> > > >
> > > >
> > > You can do this with netgraph. Check this post:
> > >
> > > http://lists.freebsd.org/pipermail/freebsd-net/2005-October/008861.html
> > >
> >
> > It's a modification of the /usr/share/examples/netgraph/ether.bridge
> > script. How do you know that it would pass 802.1q tagged frames? It
> > references a "fxp0" interface which passes untagged traffic unless a
> > vlan(4) interface is configured on top thereof.
>
> The script does not work. It prints error messages like
>
> + LINKNUM=1
> + ngctl mkpeer bnet0: ksocket link1 inet/dgram/udp
> + ngctl msg ng0:inet bind inet/10.14.143.136:4028
> ngctl: send msg: No such file or directory
> + ngctl msg ng0:inet connect inet/10.14.140.125:4028
> ngctl: send msg: No such file or directory
> + expr 1 + 1
> + LINKNUM=2
>
> and does not generate any traffic. Perhaps it needs some debugging. I
> am still looking for a solution, thanks in advance to all who has
> anything to say.
>
> In the meanwhile, I have tried bridging ethernet NICs and tap(4), and
> connected two tap(4) devices with net/vtun. It works, but again, only
> for untagged frames.
I suggest posting these questions to freebsd-net@ where all the hardcore
netheads hang out, most of whom would have no time to follow questions at .
Certainly that's where the netgraph guy(s?) may be found.
cheers, Ian
More information about the freebsd-questions
mailing list