Date: Mon, 19 Mar 2012 13:12:25 -0400 From: jammin2night <freebsd@mikej.com> To: <freebsd-net@freebsd.org> Subject: RE: Cloning VLAN interfaces Message-ID: <2ef74c561a597ebd6508625698a9563f@mail.mikej.com> In-Reply-To: <4f6765b4.0e70cc0a.351f.3bfb@mx.google.com> References: <51f939ac5fb636ae90ba1b0fd628e40b@mail.mikej.com> <4f6765b4.0e70cc0a.351f.3bfb@mx.google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for you reply! All goes well until:
(root@charon) ~# ngctl name re0-hub: downstream re0-vlan
ngctl: usage: name <path> <name>
(root@charon) ~#
(root@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@charon) ~#
On 19.03.2012 12:58, rozhuk.im@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@freebsd.org [mailto:owner-freebsd-
>> net@freebsd.org] On Behalf Of jammin2night
>> Sent: Tuesday, March 20, 2012 1:11 AM
>> To: freebsd-net@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@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@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to
>> "freebsd-net-unsubscribe@freebsd.org"
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to
> "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ef74c561a597ebd6508625698a9563f>