From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: vyasevic@redhat.com
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: VLAN filtering/VLAN aware bridge problems
Date: Thu, 29 Aug 2013 14:50:27 +0200 [thread overview]
Message-ID: <521F4393.1020907@profihost.ag> (raw)
Hello,
currently i'm running vanilla 3.8.8 kernel with some tap devices using
VLANs on top of a bridge on top of a bond.
This works fine and everything is great.
Now i started to test 3.10.9 and all my VLANs stopped working no matter
i disable or enable CONFIG_BRIDGE_VLAN_FILTERING.
The packets never reach the TAP device.
Here is an output of ip a l (vlan 3021):
ip a l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc
mq master bond0 state UP qlen 1000
link/ether 00:25:90:84:de:a8 brd ff:ff:ff:ff:ff:ff
3: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq
master bond5 state UP qlen 10000
link/ether 90:e2:ba:33:45:0c brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc
mq master bond0 state UP qlen 1000
link/ether 00:25:90:84:de:a8 brd ff:ff:ff:ff:ff:ff
5: eth2: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc
mq master bond1 state UP qlen 1000
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
6: eth5: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq
master bond5 state UP qlen 10000
link/ether 90:e2:ba:33:45:0c brd ff:ff:ff:ff:ff:ff
7: eth3: <BROADCAST,MULTICAST,PROMISC,SLAVE,UP,LOWER_UP> mtu 1500 qdisc
mq master bond1 state UP qlen 1000
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc
noqueue master vmbr0 state UP
link/ether 00:25:90:84:de:a8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe84:dea8/64 scope link
valid_lft forever preferred_lft forever
9: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc
noqueue master vmbr1 state UP
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe84:deaa/64 scope link
valid_lft forever preferred_lft forever
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP
link/ether 00:25:90:84:de:a8 brd ff:ff:ff:ff:ff:ff
inet 178.250.9.30/25 brd 178.250.9.127 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::225:90ff:fe84:dea8/64 scope link
valid_lft forever preferred_lft forever
11: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe84:deaa/64 scope link
valid_lft forever preferred_lft forever
12: bond5: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc
noqueue state UP
link/ether 90:e2:ba:33:45:0c brd ff:ff:ff:ff:ff:ff
inet 10.255.0.30/24 brd 10.255.0.255 scope global bond5
valid_lft forever preferred_lft forever
inet6 fe80::92e2:baff:fe33:450c/64 scope link
valid_lft forever preferred_lft forever
15: vmbr1.3020@vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master vmbr1v3020 state UP
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe84:deaa/64 scope link
valid_lft forever preferred_lft forever
16: vmbr1v3020: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::f036:92ff:fe40:7224/64 scope link
valid_lft forever preferred_lft forever
19: tap320i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
htb master vmbr0 state UNKNOWN qlen 500
link/ether fe:fa:14:cc:75:b2 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcfa:14ff:fecc:75b2/64 scope link
valid_lft forever preferred_lft forever
20: tap320i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
htb master vmbr1v3021 state UNKNOWN qlen 500
link/ether 8a:f3:9b:47:c7:88 brd ff:ff:ff:ff:ff:ff
inet6 fe80::88f3:9bff:fe47:c788/64 scope link
valid_lft forever preferred_lft forever
21: vmbr1.3021@vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master vmbr1v3021 state UP
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:90ff:fe84:deaa/64 scope link
valid_lft forever preferred_lft forever
22: vmbr1v3021: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP
link/ether 00:25:90:84:de:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::9868:5eff:fe9d:bf56/64 scope link
valid_lft forever preferred_lft forever
Greets,
Stefan
next reply other threads:[~2013-08-29 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 12:50 Stefan Priebe - Profihost AG [this message]
2013-08-29 20:45 ` VLAN filtering/VLAN aware bridge problems Vlad Yasevich
2013-08-30 7:24 ` Stefan Priebe - Profihost AG
2013-08-30 14:13 ` Vlad Yasevich
2013-08-30 15:01 ` Stefan Priebe - Profihost AG
2013-08-30 15:01 ` Stefan Priebe - Profihost AG
2013-09-10 14:11 ` Vlad Yasevich
2013-11-12 21:31 ` Stefan Priebe
2013-11-12 23:25 ` Vlad Yasevich
2013-11-13 7:28 ` Stefan Priebe - Profihost AG
2013-11-13 14:49 ` 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=521F4393.1020907@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.