public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manel Guerrero Zapata <manel.guerrero-zapata@nokia.com>
To: ext David Ford <david@blue-labs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 TCP caches ip route
Date: Tue, 30 Oct 2001 10:58:19 +0200	[thread overview]
Message-ID: <3BDE6BAB.F7100545@nokia.com> (raw)
In-Reply-To: <3BDDB88C.1040009@blue-labs.org>

ext David Ford wrote:
> 
> Try "ip route flush cache" or summarized, "ip r f c"
> 
> David
> 
> Manel Guerrero Zapata wrote:
> 
> >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.
> >
> [snipped]


Hi,


Answering to David:

Well, I have not tried that yet. But that is not a real solution.
You are not supposed to be flushing the cache manualy
(Although it might work as kind of workaround)
the kernel should detect that this is a stale cached entry
and delete it.


Answering to Martin:

Sure for most of the people that's not a big deal.
And yes, you are right: if the tcp connection has
been stablished before playing with routing tables
then everything works just fine.

But, IMHO I thing TCP should not make any assumptions about
routing tables (not even during the stablishment of connection).
So, I personaly see this as a kernel bug.

I understand that this is an "optimization" of the kernel
code, but I thing you should have the possibility of
disabling it.


Regards,

        Manel Guerrero

       reply	other threads:[~2001-10-30  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BDDB88C.1040009@blue-labs.org>
2001-10-30  8:58 ` Manel Guerrero Zapata [this message]
2001-10-30 13:43 ` 2.4.0 TCP caches ip route Manel Guerrero Zapata
2001-10-29 12:47 HIGMEM, SMP, 2.4.13 and Cerberus Rik van Riel
2001-10-29 13:03 ` 2.4.0 TCP caches ip route Manel Guerrero Zapata
2001-10-29 13:41   ` Martin Eriksson

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=3BDE6BAB.F7100545@nokia.com \
    --to=manel.guerrero-zapata@nokia.com \
    --cc=david@blue-labs.org \
    --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