From: "Greg Scott" <GregScott@Infrasupport.com>
To: <netdev@vger.kernel.org>
Cc: "Lynn Hanson" <LynnHanson@eaganhills.org>,
"Joe Whalen" <JoeWhalen@eaganhills.org>,
"Graham Parenteau" <adfgrahame1@gmail.com>,
"David Lamparter" <equinox@diac24.net>
Subject: RE: Bridging behavior apparently changed around the Fedora 14 time
Date: Thu, 21 Jul 2011 23:39:42 -0500 [thread overview]
Message-ID: <925A849792280C4E80C5461017A4B8A2A04149@mail733.InfraSupportEtc.com> (raw)
In-Reply-To: 925A849792280C4E80C5461017A4B8A2A0413A@mail733.InfraSupportE tc.com
> Whoa. And here I was almost ashamed of running 2.6.38. I'm sorry, but
I
> think you need to go bug RedHat.
Per your suggestion, I just put together a Red Hat bugzilla report and
documented the behavior to the best of my ability. It's listed as bug
#724862 in bugzilla.redhat.com.
- Greg
next prev parent reply other threads:[~2011-07-22 4:39 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
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 [this message]
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=925A849792280C4E80C5461017A4B8A2A04149@mail733.InfraSupportEtc.com \
--to=gregscott@infrasupport.com \
--cc=JoeWhalen@eaganhills.org \
--cc=LynnHanson@eaganhills.org \
--cc=adfgrahame1@gmail.com \
--cc=equinox@diac24.net \
--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).