Skip to contentSkip to conversation

2.4.0 TCP caches ip route

DISCUSSION Manel Guerrero Zapata 1 participant 2 messages Oct 30, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 5 lines · ext David Ford

Try "ip route flush cache" or summarized, "ip r f c"

David

Quoted 8 lines
Quoted 5 lines · Manel Guerrero Zapata

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

#2 lore raw
In reply to a message not in the archive
Quoted 5 lines · ext David Ford

Try "ip route flush cache" or summarized, "ip r f c"

David

Quoted 8 lines
Quoted 5 lines · Manel Guerrero Zapata

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,

I've tried with:
echo 0 > /proc/sys/net/ipv4/route/flush
ip route flush cache is equivalent to:
cat /proc/sys/net/ipv4/route/min_delay > /proc/sys/net/ipv4/route/flush

It does not solve anything.
I don't know why.

So not even flushing manually the cache solves
the problem.

Any ideas about why?

Manel