Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm trying to debug an issue involving a KVM virtual machine instance where the instance doesn't respond to network requests when the source is on another physical machine, which is on the same subnet as the virtual machine instance connected via Linux bridging.

(This is happening in the context of an OpenStack deployment, Folsom edition, on Ubuntu 12.04, configured using nova-network for FlatDHCP mode, not multi-host. This problem only occurs with CentOS guests, not Ubuntu guests).

When I did a tcpdump inside of the CentOS guest, I discovered that the inbound packets are being tagged with "vlan 0". For example, if I manually configure an IP address of inside of the guest and then do an "arping -i eth1" from another machine, with tcpdump I see "vlan 0"

# tcpdump -i eth0 -XX -vv -e
14:29:29.907212 54:78:1a:86:50:c9 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 0, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has (Broadcast) tell, length 46
    0x0000:  ffff ffff ffff 5478 1a86 50c9 8100 0000  ......Tx..P.....
    0x0010:  0806 0001 0800 0604 0001 5478 1a86 50c9  ..........Tx..P.
    0x0020:  0a28 0001 ffff ffff ffff 0a28 0005 0000  .(.........(....
    0x0030:  0000 0000 0000 0000 0000 0000 dac7 07ed  ................

If I load the 8021q module, the guest will respond to the ARP request properly, although it won't respond properly to DHCP, and the resulting UDP packets are tagged vlan 0.

If I do a similar tcpdump on the Ubuntu 12.04 compute host on the vnet1 interface that corresponds to the virtual machine, I don't see the vlan 0 tags:

# tcpdump -i vnet1 -XX -vv -e
tcpdump: WARNING: vnet1: no IPv4 address assigned
tcpdump: listening on vnet1, link-type EN10MB (Ethernet), capture size 65535 bytes
15:59:34.023145 54:78:1a:86:50:c9 (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has (Broadcast) tell, length 46
    0x0000:  ffff ffff ffff 5478 1a86 50c9 0806 0001  ......Tx..P.....
    0x0010:  0800 0604 0001 5478 1a86 50c9 0a28 0001  ......Tx..P..(..
    0x0020:  ffff ffff ffff 0a28 0005 0000 0000 0000  .......(........
    0x0030:  0000 0000 0000 0000 dac7 07ed            ............

In between the two physical machines is a Cisco Nexus 3000 switch.

Edit: The switch is configured with only one vlan (vlan 1), which is the native VLAN. All ports on the switch are in access mode. Here's what a typical port looks like:

# show interface switchport
Name: Ethernet1/1
  Switchport: Enabled
  Switchport Monitor: Not enabled
  Operational Mode: access
  Access Mode VLAN: 1 (default)
  Trunking Native Mode VLAN: 1 (default)
  Trunking VLANs Enabled: 1
  Administrative private-vlan primary host-association: none
  Administrative private-vlan secondary host-association: none
  Administrative private-vlan primary mapping: none
  Administrative private-vlan secondary mapping: none
  Administrative private-vlan trunk native VLAN: none
  Administrative private-vlan trunk encapsulation: dot1q
  Administrative private-vlan trunk normal VLANs: none
  Administrative private-vlan trunk private VLANs: none
  Operational private-vlan: none
  Unknown unicast blocked: disabled
  Unknown multicast blocked: disabled

Why would these vlan 0 tags get added to the frames like this? Could it be that the switch is adding these tags, but Ubuntu somehow doesn't see them when it passes the frames on to the CentOS guest? Or could it be the CentOS kernel adding the tags to incoming frames? If so, why would that happen?

share|improve this question
Truth be told, this is a wild stab in the dark, but you aren't applying and QoS/CoS tags anywhere are you per chance? Often VLAN 0 is set when you want to add a PCP value to an Ethernet frame for QoS, but you aren't using any VLAN (so VLAN 0). Even though in your TCP dump it says VLAN 0 priority 0, are you using QoS in your deployment but not on this guest, so it's tagging it with priority 0 and thusly VLAN 0? – jwbensley Apr 8 '13 at 20:23
The switch could be adding the tags. What does your VLAN topology look like? – Ryan Apr 8 '13 at 22:35
Do you have an ifcfg-eth0.0 file in /etc/sysconfig/network-scripts/? – Ryan Apr 8 '13 at 22:43
I only have one VLAN on the switch, the native VLAN. All of the ports are in access mode (I edited above). There's no ifcfg-eth0.0 in /etc/sysconfig/network-scripts. How can I tell if my Cisco Nexus switch is adding CoS tags? – Lorin Hochstein Apr 8 '13 at 23:47

1 Answer 1

Faced similar situation today on centos 6 ,an upgrade to latest kernel fixes this.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.