All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: cache forver in 3.2.0-rc2-00400-g866d43c ?
Date: Wed, 23 Nov 2011 19:31:08 +0100	[thread overview]
Message-ID: <201111231931.08596.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <1322072541.2775.1.camel@edumazet-laptop>

On Wednesday 23 of November 2011, Eric Dumazet wrote:
> Le mercredi 23 novembre 2011 à 19:10 +0100, Arkadiusz Miśkiewicz a
> 
> écrit :
> > Hello,
> > 
> > I'm using  my notebook in two different networks, suspending and resuming
> > from ram between.
> > 
> > Network A (192.168.1.0/24) has server with IP 87.204.99.133 in the same
> > lan. Now when I suspend, go to totally different network B (different
> > provider, different lan, 192.168.0.0/24) and resume then I'm unable to
> > connect to 87.204.99.133.
> > 
> > Looks like network stack thinks that 87...133 is still directly reachable
> > on eth1and I'm unable to make it forget that.
> > 
> > [root@t400 ~]# ip ne flush dev eth1; ip r flush table cache
> > [root@t400 ~]# ip r show table cache to 87.204.99.133
> > [root@t400 ~]# ping -c 1 87.204.99.133
> > PING 87.204.99.133 (87.204.99.133) 56(84) bytes of data.
> > From 192.168.0.5: icmp_seq=1 Destination Host Unreachable
> > 
> > --- 87.204.99.133 ping statistics ---
> > 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
> > 
> > zsh: exit 1     ping -c 1 87.204.99.133
> > [root@t400 ~]# ip r show table cache to 87.204.99.133
> > 87.204.99.133 dev eth1  src 192.168.0.5
> > 
> >     cache <redirected>  ipid 0x2838 rtt 17ms rttvar 12ms cwnd 10
> > 
> > 87.204.99.133 from 192.168.0.5 dev eth1
> > 
> >     cache <redirected>  ipid 0x2838 rtt 17ms rttvar 12ms cwnd 10
> > 
> > [root@t400 ~]# ip ne show to 87.204.99.133
> > 87.204.99.133 dev eth1  FAILED
> > 
> > tcpdump in meantime sees this:
> > 19:06:26.907153 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> > 87.204.99.133 tell 192.168.0.5, length 28
> > 19:06:27.908379 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> > 87.204.99.133 tell 192.168.0.5, length 28
> > 19:06:28.907084 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> > 87.204.99.133 tell 192.168.0.5, length 28
> > 19:06:29.907145 IP (tos 0xc0, ttl 64, id 34465, offset 0, flags [none],
> > proto ICMP (1), length 112)
> > 
> >     192.168.0.5 > 192.168.0.5: ICMP host 87.204.99.133 unreachable,
> >     length 92
> >     
> >         IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto ICMP (1),
> > 
> > length 84)
> > 
> >     192.168.0.5 > 87.204.99.133: ICMP echo request, id 17590, seq 1,
> >     length 64
> > 
> > Any ideas?
> > 
> > Thanks,
> 
> Hmm, could you check you have this fix in your tree ?
> 
> http://git2.kernel.org/?p=linux/kernel/git/davem/net.git;a=commit;h=9cc20b2
> 68a5a14f5e57b8ad405a83513ab0d78dc

Mine 00400-g866d43c was after 6fe4c6d466e95d31164f14b1ac4aefb51f0f4f82 (which 
is merge of ipv4: fix redirect handling), so I have it.

(I'm using pure linus git repo)
-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

  reply	other threads:[~2011-11-23 18:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 18:10 cache forver in 3.2.0-rc2-00400-g866d43c ? Arkadiusz Miśkiewicz
2011-11-23 18:22 ` Eric Dumazet
2011-11-23 18:31   ` Arkadiusz Miśkiewicz [this message]
2011-11-23 18:37     ` Eric Dumazet
2011-11-23 19:44       ` Eric Dumazet
2011-11-23 20:35         ` Arkadiusz Miśkiewicz
2011-11-25 17:53           ` Arkadiusz Miśkiewicz
2011-11-26 22:10             ` Eric Dumazet
2011-11-26 22:13             ` [PATCH] inet: Eric Dumazet
2011-11-26 22:16               ` Eric Dumazet
2011-11-27  0:17                 ` 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=201111231931.08596.a.miskiewicz@gmail.com \
    --to=a.miskiewicz@gmail.com \
    --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.