From: "Greg Scott" <GregScott@Infrasupport.com>
To: "Stephen Hemminger" <shemminger@vyatta.com>
Cc: <netdev@vger.kernel.org>,
"Lynn Hanson" <LynnHanson@eaganhills.org>,
"Joe Whalen" <JoeWhalen@eaganhills.org>
Subject: RE: Bridging behavior apparently changed around the Fedora 14 time
Date: Mon, 11 Jul 2011 16:08:14 -0500 [thread overview]
Message-ID: <925A849792280C4E80C5461017A4B8A2A040F6@mail733.InfraSupportEtc.com> (raw)
In-Reply-To: 20110711134938.5178797c@nehalam.ftrdhcpuser.net
> What about console dmesg output.
I should probably turn off all firewall logging so I don't fill the ring
buffer with my log messages in, like, the first couple minutes after a
boot. :)
> Please retest with a standard upstream kernel (like 2.6.39.2).
That's gonna take a while to put together a whole test environment with
the latest kernel.org kernel.
> The bridge itself puts the device into promiscuous mode already.
Uhmmmm - no it didn't. Remember, I put br0 into promiscuous mode myself
by hand - take a look at this. Note eth0 and eth1 are not in
promiscuous mode. I wonder how it would behave if I put the physical
devices into promiscuous mode and left br0 alone? This I can easily
test during off hours.
[root@ehac-fw2011 gregs]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
DOWN qlen 1000
link/ether 00:0e:7f:2d:d0:6e brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:03:47:3a:59:79 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:0d:88:31:d8:24 brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc prio
state UNKNOWN
link/ether 00:03:47:3a:59:79 brd ff:ff:ff:ff:ff:ff
[root@ehac-fw2011 gregs]#
- Greg
next prev parent reply other threads:[~2011-07-11 21:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 18:25 Bridging behavior apparently changed around the Fedora 14 time Greg Scott
2011-07-11 20:07 ` Stephen Hemminger
2011-07-11 20:41 ` Greg Scott
2011-07-11 20:49 ` Stephen Hemminger
2011-07-11 21:08 ` Greg Scott [this message]
2011-07-11 21:10 ` Stephen Hemminger
2011-07-11 21:16 ` Ben Greear
2011-07-12 3:06 ` Greg Scott
2011-07-11 21:16 ` Greg Scott
2011-07-11 21:24 ` Stephen Hemminger
2011-07-12 0:02 ` David Lamparter
2011-07-12 2:38 ` Greg Scott
2011-07-12 3:39 ` David Lamparter
2011-07-12 14:30 ` Greg Scott
2011-07-12 14:54 ` David Lamparter
2011-07-12 16:28 ` Greg Scott
2011-07-21 4:40 ` Greg Scott
2011-07-21 15:01 ` Greg Scott
[not found] ` <925A849792280C4E80C5461017A4B8A2A0413A@mail733.InfraSupportE tc.com>
2011-07-22 4:39 ` Greg Scott
2011-07-22 6:20 ` Greg Scott
2011-09-15 22:48 ` Very confused about broute DROP Greg Scott
2011-09-15 23:08 ` Christian Benvenuti (benve)
2011-09-16 3:19 ` Greg Scott
2011-09-16 4:23 ` Christian Benvenuti (benve)
2011-09-16 14:55 ` Greg Scott
2011-09-18 1:47 ` Greg Scott
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=925A849792280C4E80C5461017A4B8A2A040F6@mail733.InfraSupportEtc.com \
--to=gregscott@infrasupport.com \
--cc=JoeWhalen@eaganhills.org \
--cc=LynnHanson@eaganhills.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 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).