From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Chini, Georg (HP App Services)" <georg.chini@hp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Kernel 3.6 drops network packets instead of forwarding
Date: Sat, 06 Oct 2012 15:53:36 +0200 [thread overview]
Message-ID: <1349531616.21172.1069.camel@edumazet-glaptop> (raw)
In-Reply-To: <B3A09DD14C7DC341B8B4D309FE5DD1BE1513FA4B@G2W2525.americas.hpqcorp.net>
On Sat, 2012-10-06 at 11:52 +0000, Chini, Georg (HP App Services) wrote:
> Hello,
>
> I have a network issue with kernel 3.6. My machine is set
> up as router and with 3.6 it sometimes silently drops reply
> packets instead of forwarding.
> Example tcpdump on the router for ping www.heise.de from a
> machine in my network (NAT is done elsewhere):
>
> 12:37:54.746627 IP 192.168.255.150 > 193.99.144.85: ICMP echo request, id 16414, seq 1, length 64 (eth0)
> 12:37:54.746681 IP 192.168.255.150 > 193.99.144.85: ICMP echo request, id 16414, seq 1, length 64 (GRE tunnel)
> 12:37:54.782195 IP 193.99.144.85 > 192.168.255.150: ICMP echo reply, id 16414, seq 1, length 64 (GRE tunnel)
> 12:37:54.782335 IP 193.99.144.85 > 192.168.255.150: ICMP echo reply, id 16414, seq 1, length 64 (eth0)
> 12:37:55.785974 IP 192.168.255.150 > 193.99.144.85: ICMP echo request, id 16416, seq 1, length 64 (eth0)
> 12:37:55.786023 IP 192.168.255.150 > 193.99.144.85: ICMP echo request, id 16416, seq 1, length 64 (GRE tunnel)
> 12:37:55.822529 IP 193.99.144.85 > 192.168.255.150: ICMP echo reply, id 16416, seq 1, length 64 (GRE tunnel)
> NO forwarded packet on eth0
>
> Then this goes on for an arbitrary period (between a few seconds and
> more then half an hour) and suddenly returns to normal. During that
> time no communication is possible between a host on my network and
> any external host. Connections from the router itself still work.
> With kernel 3.4.3 everything works fine. Had the same issue with
> -rc6 and -rc7.
>
> There are no messages in the logs. Any idea what might cause this
> or how I can debug it any further?
> I will supply more details on my setup if needed. Please CC me in
> your reply as I am not subscribed to the list.
Looks like the bug fixed by :
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=f4ef85bbda96324785097356336bc79cdd37db0a
(David Miller will send it to stable team shortly)
next prev parent reply other threads:[~2012-10-06 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 11:52 Chini, Georg (HP App Services)
2012-10-06 13:53 ` Eric Dumazet [this message]
2012-10-06 17:52 ` AW: " Chini, Georg (HP App Services)
2012-10-07 6:37 ` Eric Dumazet
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=1349531616.21172.1069.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=georg.chini@hp.com \
--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
all inboxes | Powered by JetHome®