Utilizing VLANs

Discussions related to using VirtualBox on Windows hosts.
Post Reply
davez0rz
Posts: 1
Joined: 18. Jan 2019, 15:05

Utilizing VLANs

Post by davez0rz »

Hi All,

I've seen information on using VLAN tagging/untags to virtual machines but it seems the network adapter or virtualbox (can't tell which) is stripping all VLAN tags. I know the VLAN tags work as I've already tested this with raspberry pi's. My problem is once I deploy some additional systems (of course this is a home lab) I will be using CentOS, not raspbian.

I have a secondary PCI NIC in my desktop that I use specifically for VM networks. This is connected to an Ubiquiti EdgeSwitch on a trunk port that can see all VLANs with a native of VLAN 500 (for raspberry Pi's). The Pi's (being untagged for VLAN 500 and trunk for 500, 600, 601) will typically see the following:

Code: Select all

12:55:14.810990 54:bf:64:34:86:2b > fc:ec:da:05:f3:53, ethertype 802.1Q (0x8100), length 346: vlan 600, p 0, ethertype IPv4, 10.2.52.100.68 > 10.2.52.2.67: BOOTP/DHCP, Request from 54:bf:64:34:86:2b, length 300
12:55:18.970542 54:bf:64:34:86:2b > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 347: vlan 600, p 0, ethertype IPv4, 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 54:bf:64:34:86:2b, length 301
12:55:19.974671 54:bf:64:34:86:2b > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 372: vlan 600, p 0, ethertype IPv4, 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 54:bf:64:34:86:2b, length 326
When I connect my secondary NIC to the trunk port and try to boot a pi (or any other device) on VLAN 600, I see no VLAN tags; eg:

Code: Select all

[root@dhcpd ~]# tcpdump -i eth0 -nn -e port 67 or port 68
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
07:47:47.398298 b8:27:eb:8e:76:ec > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:8e:76:ec, length 300
07:47:54.626029 b8:27:eb:8e:76:ec > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:8e:76:ec, length 300
07:48:20.329393 b8:27:eb:8e:76:ec > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:8e:76:ec, length 300
07:48:28.865879 b8:27:eb:8e:76:ec > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:8e:76:ec, length 300
07:48:40.593907 b8:27:eb:8e:76:ec > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:8e:76:ec, length 300
I've seen some articles online referencing a "vlan package" but I can't seem to find this package anywhere.

Any ideas what is preventing the tags from coming through?
Post Reply