From: "Sebastian J. Bronner" <sebastian.bronner@d9t.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, Daniel Kraft <daniel.kraft@d9t.de>
Subject: Re: bridge not routing packets via source bridgeport
Date: Tue, 04 Jan 2011 09:25:52 +0100 [thread overview]
Message-ID: <4D22D990.7030409@d9t.de> (raw)
In-Reply-To: <1294080135.2892.1152.camel@edumazet-laptop>
On 03.01.2011 19:42, Eric Dumazet wrote:
> Le lundi 03 janvier 2011 à 18:52 +0100, Sebastian J. Bronner a écrit :
>> we recently upgraded from 2.6.32.25 to 2.6.35.24 and discovered that our
>> virtual machines can no longer access their own external IP addresses.
>> Testing revealed that 2.6.34 was the last version not to have the
>> problem. 2.6.36 still had it. But on to the details.
[ Details snipped ]
> random guess: maybe rp_filter hits you ?
>
>
> With 2.6.36, a new SNMP counter was added,
> "netstat -s | grep IPReversePathFilter"
Thanks for your guess, Eric.
Unfortunately, that didn't change anything.
According to the documentation at
http://lartc.org/howto/lartc.kernel.html
that parameter is to prevent _responses_ leaving through a different
interface that the original packet came in on. So, I wouldn't expect it
to have any impact on _routed packets_.
In my original e-mail, I forgot to mention something I noticed while
debugging:
If i put the bridge into promiscuous mode, then suddenly the packets are
routed.
# ip link set promisc on dev virbr1
Cheers,
Sebastian
--
*Sebastian J. Bronner*
Administrator
D9T GmbH - Magirusstr. 39/1 - D-89077 Ulm
Tel: +49 731 1411 696-0 - Fax: +49 731 3799-220
Geschäftsführer: Daniel Kraft
Sitz und Register: Ulm, HRB 722416
Ust.IdNr: DE 260484638
http://d9t.de - D9T High Performance Hosting
info@d9t.de
next prev parent reply other threads:[~2011-01-04 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 17:52 bridge not routing packets via source bridgeport Sebastian J. Bronner
2011-01-03 18:42 ` Eric Dumazet
2011-01-04 8:25 ` Sebastian J. Bronner [this message]
2011-03-23 10:12 ` Sebastian J. Bronner
2011-03-23 19:27 ` David Miller
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=4D22D990.7030409@d9t.de \
--to=sebastian.bronner@d9t.de \
--cc=daniel.kraft@d9t.de \
--cc=eric.dumazet@gmail.com \
--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 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.