From: Manel Guerrero Zapata <manel.guerrero-zapata@nokia.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.4.0 TCP caches ip route
Date: Mon, 29 Oct 2001 15:03:13 +0200 [thread overview]
Message-ID: <3BDD5391.6BF30E81@nokia.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110291047040.2963-100000@imladris.surriel.com>
Hi,
I'm using 2.4.0 (but I thing that this is probably a 2.4.X problem).
If a execute a telnet command to certain address (like 10.0.0.1).
And the routing table says that packets for 10.0.0.1 should be
routed to the device dummy0,
The telnet keeps trying to connect. (till here everything is cool).
And then I change the routing table so now it should
send those packets to the ppp0 (where 10.0.0.1 is), but the
connexion does not get stablished anyway (till I get timeout).
The problem seems to be that the kernel
caches that the device for the connexion should be dummy0.
If then, I cancel the telnet and start it again
now (of course) it stablishes a telnet conexion though the ppp0.
This problem does not occur if I use ping instead of telnet
(probably because ping uses no socket).
Should not be a mechanism that flushes caches when routing
table changes?
If the cached info is attached to the socket structure
probably this flushing thing is not quite feasible, am I wrong?
I know you usually don't expect the device though your tcp
connection goes to change on the fly, but that actually can
happend, and maybe (IMHO) should be supported.
Maybe I'm missing something. (probably ;) )
Regards,
Manel Guerrero
next prev parent reply other threads:[~2001-10-29 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 12:34 HIGMEM, SMP, 2.4.13 and Cerberus Joan Batet
2001-10-29 12:47 ` Rik van Riel
2001-10-29 13:03 ` Manel Guerrero Zapata [this message]
2001-10-29 13:41 ` 2.4.0 TCP caches ip route Martin Eriksson
[not found] <3BDDB88C.1040009@blue-labs.org>
2001-10-30 8:58 ` Manel Guerrero Zapata
2001-10-30 13:43 ` Manel Guerrero Zapata
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=3BDD5391.6BF30E81@nokia.com \
--to=manel.guerrero-zapata@nokia.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