> > It's my fault that I forget to mention:
> > ccssu:~# uname -a
> > Linux mordor 2.2.5 #41 Fri Apr 2 19:45:30 MSD 1999 i586 unknown
> Ok, I've thought about it a little bit more... Are you trying to talk
> to a _specific_ host? What happens if you try to talk to a host that
> is matched by this route but with whom you didn't talk before? Does it
> use the new route?
I did not taalk to this host before (or if talk was done, it was a long ago)
Let me explain purposes of this somewhat weird routing:
I have 2 dialin hosts and I have dialin clients with static IP.
So I set up routing for these static IPs from one host to another
and from that another to first (I get loop this way).
When PPP client with this IP connected, route to ppp device established
and overrides default one. This was 2.0 behaviour, but under 2.2
this scheme no longer works. It does not work from start, when there was no
traffic between one of hosts and that address.
(just to add. I replaced only one 2.0 box with 2.2 kernel,
so I just see what works with 2.0 did not work with 2.2)
It was brought to my attention that route added differently in 2.0
and 2.2 (in 2.0 pppd do it, in 2.2 kernel do it),
but I think it is silly to differentiate kernel added and user added routes.
> The pb that a I see is that:
> - You talk to host A before your ppp connection goes up so the kernel
> caches this route
No. That was not the case
> - You bring up the ppp connection and add a different route
> - You still want to talk to host A _but_ the kernel has a a route that
> is cached and more important still valid so it has no reason to look
> into its routing tables for another route (look at ipforward.c and
> route.c in ipv4)
As I said it was not the case (may be it looked like this from my demonstration,
but believe me, even if no previous conversations with host A was made
route still not work.)
> Now, try adding a:
> echo 1 > /proc/sys/net/ipv4/route/flush
> in your ip-up script... Does it cure the problem??
I cannot say for now, but I'll try as soon as I can.
Anyway it is a pity, that I cannot use somewhat previously worked with 2.0
without changes
Bye,
Oleg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/