netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Cc: netdev@vger.kernel.org
Subject: Re: bridge vlan_filtering don't work with tap devices (qemu guests)
Date: Thu, 26 Dec 2013 14:57:21 +0100 (CET)	[thread overview]
Message-ID: <eb3c68d9-fa1b-402a-9416-1ea38a78b68b@mailpro> (raw)
In-Reply-To: <338a04d5-a1bc-4446-b03b-e59fddcb65e8@mailpro>

Hello Again,

One more question :

If I use tcpdump on br0, I don't see any tagged vlan10 packets on the bridge.
with 
# bridge vlan add dev tap0 vid 10 pvid untagged 
# bridge vlan add dev tap1 vid 10 pvid untagged 


What I would like to do, is tagging vlan10, incoming (untagged) packets from tap0 and tap1.

Is it possible ?

With openvswitch, I can do it simply with "ovs-vsctl set port tap0 tag=10"

----- Mail original ----- 

De: "Alexandre DERUMIER" <aderumier@odiso.com> 
À: "Toshiaki Makita" <makita.toshiaki@lab.ntt.co.jp> 
Cc: netdev@vger.kernel.org 
Envoyé: Mardi 24 Décembre 2013 20:28:55 
Objet: Re: bridge vlan_filtering don't work with tap devices (qemu guests) 

>>If you want to send untagged frames, please try to make configuration 
>>like this: 
>># bridge vlan add dev tap0 vid 10 pvid untagged 
>># bridge vlan add dev tap1 vid 10 pvid untagged 
>> 
>>Thanks, 
>>Toshiaki Makita 

Thank you ! It's working now. 
I thinked that "untagged" was for not tagging from the bridge, I understand now. 

Thanks again and merry Xmas ! 


----- Mail original ----- 

De: "Toshiaki Makita" <makita.toshiaki@lab.ntt.co.jp> 
À: "Alexandre DERUMIER" <aderumier@odiso.com> 
Cc: netdev@vger.kernel.org 
Envoyé: Mardi 24 Décembre 2013 13:45:05 
Objet: Re: bridge vlan_filtering don't work with tap devices (qemu guests) 

On Mon, 2013-12-23 at 17:02 +0100, Alexandre DERUMIER wrote: 
> 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 

If you want to send untagged frames, please try to make configuration 
like this: 
# bridge vlan add dev tap0 vid 10 pvid untagged 
# bridge vlan add dev tap1 vid 10 pvid untagged 

Thanks, 
Toshiaki Makita 

> #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 
> -- 
> To unsubscribe from this list: send the line "unsubscribe netdev" in 
> the body of a message to majordomo@vger.kernel.org 
> More majordomo info at http://vger.kernel.org/majordomo-info.html 
-- 
To unsubscribe from this list: send the line "unsubscribe netdev" in 
the body of a message to majordomo@vger.kernel.org 
More majordomo info at http://vger.kernel.org/majordomo-info.html 

  reply	other threads:[~2013-12-26 13:57 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 ` bridge vlan_filtering don't work with tap devices (qemu guests) Alexandre DERUMIER
2013-12-24 12:45   ` Toshiaki Makita
2013-12-24 19:28     ` Alexandre DERUMIER
2013-12-26 13:57       ` Alexandre DERUMIER [this message]
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=eb3c68d9-fa1b-402a-9416-1ea38a78b68b@mailpro \
    --to=aderumier@odiso.com \
    --cc=makita.toshiaki@lab.ntt.co.jp \
    --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;
as well as URLs for NNTP newsgroup(s).