public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: netdev@vger.kernel.org
Subject: bridge vlan_filtering don't work with tap devices (qemu guests)
Date: Mon, 23 Dec 2013 17:02:40 +0100 (CET)	[thread overview]
Message-ID: <717e26b0-fda3-4c97-81a6-45e67462cb6b@mailpro> (raw)
In-Reply-To: <04e69925-f469-49b2-9988-9077eb7d50d7@mailpro>

Hello,

I'm trying to use vlan_filtering on bridge.

setup is : 2 qemu virtual machines (tap0 and tap1), plugged in a bridge br0.
           virtual machines don't tag packets.


qemuvm1 eth0 --tap0----->br0<-------tap1---qemuvm2 eth0.


with vlan_filtering disable, both vms can ping together.


If I enabled filtering

#echo 1 > /sys/class/net/br0/bridge/vlan_filtering

Both vms cannot ping together anymore.

So, I have tried to put vlan on tap interfaces with

#bridge vlan add dev tap0 vid 10
#bridge vlan add dev tap1 vid 10
#bridge vlan show
port	vlan ids
br0	None
tap0	10
tap1    10



But, it doesn't work.

tcpdump on bridge (tcpdump -i br0 -e -n) or in destination qemu (tcpdump -i eth0 -e -n) , don't see any packet

any idea ? 

Regards,

Alexandre Derumier

       reply	other threads:[~2013-12-23 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <04e69925-f469-49b2-9988-9077eb7d50d7@mailpro>
2013-12-23 16:02 ` Alexandre DERUMIER [this message]
2013-12-24 12:45   ` bridge vlan_filtering don't work with tap devices (qemu guests) Toshiaki Makita
2013-12-24 19:28     ` Alexandre DERUMIER
2013-12-26 13:57       ` Alexandre DERUMIER
2013-12-27  8:28         ` Toshiaki Makita
2013-12-27  9:46           ` Alexandre DERUMIER
2013-12-27 16:17             ` Alexandre DERUMIER
2013-12-28 13:00               ` Toshiaki Makita
2014-01-03 15:33                 ` Vlad Yasevich

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=717e26b0-fda3-4c97-81a6-45e67462cb6b@mailpro \
    --to=aderumier@odiso.com \
    --cc=netdev@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