Cloning VLAN interfaces
rozhuk.im at gmail.com
rozhuk.im at gmail.com
Mon Mar 19 18:19:20 UTC 2012
Remove space: name re0-hub:downstream re0-vlan
> -----Original Message-----
> From: owner-freebsd-net at freebsd.org [mailto:owner-freebsd-
> net at freebsd.org] On Behalf Of jammin2night
> Sent: Tuesday, March 20, 2012 2:12 AM
> To: freebsd-net at freebsd.org
> Subject: RE: Cloning VLAN interfaces
>
> Thanks for you reply! All goes well until:
>
> (root at charon) ~# ngctl name re0-hub: downstream re0-vlan
> ngctl: usage: name <path> <name>
> (root at charon) ~#
>
>
> (root at charon) ~# ngctl list
> There are 6 total nodes:
> Name: <unnamed> Type: vlan ID: 0000001c Num
> hooks:
> 1
> Name: em0 Type: ether ID: 00000002 Num
> hooks:
> 0
> Name: re0 Type: ether ID: 00000001 Num
> hooks:
> 2
> Name: vlan10 Type: ether ID: 00000003 Num
> hooks:
> 0
> Name: ngctl4248 Type: socket ID: 00000027 Num
> hooks:
> 0
> Name: re0-hub Type: hub ID: 00000017 Num
> hooks:
> 3
> (root at charon) ~#
>
>
>
> On 19.03.2012 12:58, rozhuk.im at gmail.com wrote:
> > #!/bin/sh
> >
> > ngctl shutdown re0:lower
> > ngctl shutdown re0:upper
> >
> > ngctl mkpeer re0: hub lower lower
> > ngctl name re0:lower re0-hub
> > ngctl connect re0: re0-hub: upper upper
> >
> > ngctl mkpeer re0-hub: vlan downstream downstream ngctl name re0-hub:
> > downstream re0-vlan ngctl mkpeer re0-vlan: eiface vlan10 ether ngctl
> > msg re0-vlan: addfilter '{ vlan=10 hook="vlan10" }'
> >
> >
> >> -----Original Message-----
> >> From: owner-freebsd-net at freebsd.org [mailto:owner-freebsd-
> >> net at freebsd.org] On Behalf Of jammin2night
> >> Sent: Tuesday, March 20, 2012 1:11 AM
> >> To: freebsd-net at freebsd.org
> >> Subject: Cloning VLAN interfaces
> >>
> >> FreeBSD charon 9.0-STABLE FreeBSD 9.0-STABLE #14 r233107: Sun Mar 18
> >> 05:26:58 EDT 2012 root at charon:/usr/obj/usr/src/sys/CHARON amd64
> >>
> >> Hello:
> >>
> >> I have a machine that has a 802.1q trunk attached which works fine.
> >> I
> >> can create VLAN interfaces, apply an IP address to them and all is
> >> good.
> >>
> >> I have VirtualBox running on this machine and need to present an
> >> interface to a VM that does not support trunking natively. I've
> >> googled and searched the archive trying to figure out how to create
> >> an interface that VirtualBox will use where the 802.1Q tags are
> >> removed but have not had any success.
> >>
> >> I attempted to create a netgraph interface like:
> >>
> >> #!/bin/sh
> >>
> >> ngctl shutdown re0:
> >> ngctl mkpeer re0: vlan lower downstream ngctl name re0:lower vlan
> >> ngctl connect re0: vlan: upper upstream ngctl mkpeer vlan: eiface
> >> vlan10 ether ngctl msg vlan: addfilter '{ vlan=10 hook="vlan10" }'
> >>
> >> but this nuked my VLAN10 interface. Using tcpdump I saw no traffic
> >> on interface VLAN10 or interface ngeth0. I probably going about this
> >> all wrong or just don't get the netgraph hooks.
> >>
> >> If there is an example as to how to this this I just missed it.
> >>
> >> Any pointers on how to accomplish this?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> freebsd-net at freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> >> To unsubscribe, send any mail to
> >> "freebsd-net-unsubscribe at freebsd.org"
> >
> > _______________________________________________
> > freebsd-net at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> > To unsubscribe, send any mail to
> > "freebsd-net-unsubscribe at freebsd.org"
>
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
More information about the freebsd-net
mailing list