kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ron Vachiyer <ronvach@abacom.com>
To: KVM devel mailing list <kvm@vger.kernel.org>
Subject: Stripped 802.1q from frames
Date: Fri, 09 Aug 2013 16:47:19 -0400	[thread overview]
Message-ID: <52055557.5060701@abacom.com> (raw)

Hello,

I have a curious behaviour I am seeing on my two KVM hosts running under 
CentOS6.4 on HP Hardware (bnx2 NICs in both cases), virtio is configured 
for the guest networking.

The hosts are connected to Cisco switches on a trunk port.  I have noted 
that flooded frames from 802.1q VLANs not native to any interface on the 
KVM hosts are stripped of their 802.1q tags and forwarded to guests 
configured to use the bridge0 or macvtap interface on the host (whatever 
native VLAN that host is in).  KVM guests that are utilizing a different 
802.1q-tagged bridge interface on the host do not see this behaviour.

At first I believed it was an issue with the host that was bonding two 
NICs, however the second host on a single eth0 interface is seeing the 
same thing.  I have run a packet capture on a guest and the host 
simultaneously and confirmed that although the host will receive a frame 
from the Cisco switch tagged for example VID:08, for which the kvm host 
does not have an interface, libpcap shows the 802.1q tag on the frame.  
However, that very same frame somehow gets stripped of that tag, and the 
guest has visibility to this frame but without the tag.

I first noticed this when a guest I was installing using SLAAC 
autoconfigured itself with a IPv6 address from another VLAN not 
configured on the KVM host.

Google has not shown me any links to this, therefore could this be a 
configuration snafu or is there somewhere else I could look to fix this?

Thanks,

Ron.


                 reply	other threads:[~2013-08-09 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52055557.5060701@abacom.com \
    --to=ronvach@abacom.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).