From: Alexandre DERUMIER <aderumier-U/x3PoR4x10AvxtiuMwx3w@public.gmane.org>
To: netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: pve-devel <pve-devel-KmHT29P9Uc/4CZzEM2C48g@public.gmane.org>
Subject: bridge vlan range, kernel 4.1 : "message truncated" warning when too much vlans defined
Date: Wed, 29 Jul 2015 20:24:49 +0200 (CEST) [thread overview]
Message-ID: <1522237479.23555412.1438194289391.JavaMail.zimbra@oxygem.tv> (raw)
Hi,
I'm currently testing vlan range on bridge filtering with kernel 4.1.
If I defined too much vlans, or too big vlan range,
I have a warning "message truncated", even if I'm using "-c"
# bridge -c vlan
Message truncated
port vlan ids
eth2 1 PVID Egress Untagged
bond0 1 PVID Egress Untagged
2-1850
vmbr0 1 PVID Egress Untagged
94
or
# bridge -c vlan
Message truncated
port vlan ids
eth2 1 PVID Egress Untagged
2-900
bond0 1 PVID Egress Untagged
2-900
vmbr0 1 PVID Egress Untagged
94
Also, more important, this is also impact "ip", and truncate the output
#ip link
Message truncated
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9000 qdisc pfifo_fast master vmbr1 state DOWN mode DEFAULT group default qlen 1000
link/ether 00:15:17:80:29:e6 brd ff:ff:ff:ff:ff:ff
3: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:15:17:80:29:e7 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
link/ether 00:1a:a0:3c:98:c5 brd ff:ff:ff:ff:ff:ff
5: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast master ovs-system state UP mode DEFAULT group default qlen 1000
link/ether 68:05:ca:09:c3:7c brd ff:ff:ff:ff:ff:ff
6: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast master ovs-system state UP mode DEFAULT group default qlen 1000
link/ether 68:05:ca:09:c3:7d brd ff:ff:ff:ff:ff:ff
7: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
link/ether 00:1a:a0:3c:98:c5 brd ff:ff:ff:ff:ff:ff
8: ovs-system@NONE: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default
link/ether 7e:dd:5d:ea:ef:26 brd ff:ff:ff:ff:ff:ff
9: vmbr10@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/ether 68:05:ca:09:c3:7d brd ff:ff:ff:ff:ff:ff
10: bond1@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/ether 8a:c3:da:b0:9d:87 brd ff:ff:ff:ff:ff:ff
11: bond0@NONE: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default
link/ether 00:1a:a0:3c:98:c5 brd ff:ff:ff:ff:ff:ff
12: vmbr0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 00:1a:a0:3c:98:c5 brd ff:ff:ff:ff:ff:ff
13: vmbr0.94@vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 00:1a:a0:3c:98:c5 brd ff:ff:ff:ff:ff:ff
---->should have more interfaces here
Is it a known bug ?
Regards,
Alexandre Derumier
next reply other threads:[~2015-07-29 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 18:24 Alexandre DERUMIER [this message]
2015-07-30 2:03 ` bridge vlan range, kernel 4.1 : "message truncated" warning when too much vlans defined Arad, Ronen
2015-07-30 5:31 ` Alexandre DERUMIER
2015-09-10 6:40 ` [pve-devel] " Alexandre DERUMIER
2015-09-10 22:26 ` roopa
2015-09-10 22:58 ` David Miller
2015-09-11 0:02 ` roopa
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=1522237479.23555412.1438194289391.JavaMail.zimbra@oxygem.tv \
--to=aderumier-u/x3por4x10avxtiumwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pve-devel-KmHT29P9Uc/4CZzEM2C48g@public.gmane.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).