From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel@vger.kernel.org
Cc: davem@davemloft.net
Subject: ipv4 regression in 2.6.31 ?
Date: Mon, 14 Sep 2009 15:09:35 +0200 [thread overview]
Message-ID: <20090914150935.cc895a3c.skraw@ithnet.com> (raw)
Hello all,
today we experienced some sort of regression in 2.6.31 ipv4 implementation, or
at least some incompatibility with former 2.6.30.X kernels.
We have the following situation:
---------- vlan1@eth0 192.168.2.1/24
/
host A 192.168.1.1/24 eth0 -------<router> host B
\
---------- eth1 192.168.3.1/24
Now, if you route 192.168.1.0/24 via interface vlan1@eth0 on host B and let
host A ping 192.168.2.1 everything works. But if you route 192.168.1.0/24 via
interface eth1 on host B and let host A ping 192.168.2.1 you get no reply.
With tcpdump we see the icmp packets arrive at vlan1@eth0, but no icmp echo
reply being generated neither on vlan1 nor eth1.
Kernels 2.6.30.X and below do not show this behaviour.
Is this intended? Do we need to reconfigure something to restore the old
behaviour?
--
Regards,
Stephan
next reply other threads:[~2009-09-14 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 13:09 Stephan von Krawczynski [this message]
2009-09-14 13:57 ` ipv4 regression in 2.6.31 ? Eric Dumazet
2009-09-14 15:10 ` Stephan von Krawczynski
2009-09-14 15:21 ` Eric Dumazet
2009-09-14 15:55 ` Stephan von Krawczynski
2009-09-14 16:10 ` Paravirtualization Richard B. Johnson
2009-09-14 16:10 ` ipv4 regression in 2.6.31 ? Eric Dumazet
2009-09-14 16:31 ` Stephen Hemminger
2009-09-15 0:01 ` Julian Anastasov
2009-09-15 8:13 ` Jarek Poplawski
2009-09-15 22:57 ` Stephen Hemminger
2009-09-16 5:23 ` Jarek Poplawski
2009-09-16 17:00 ` Stephen Hemminger
2009-09-18 8:30 ` Stephan von Krawczynski
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=20090914150935.cc895a3c.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@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