[2240] in linux-net channel archive
Re: kernel redirect message
daemon@ATHENA.MIT.EDU (Alan Cox)
Mon Mar 25 13:27:51 1996
From: iialan@iifeak.swan.ac.uk (Alan Cox)
To: ccc@eintec.es (Carlos "M." Chamorro)
Date: Mon, 25 Mar 1996 08:48:18 +0000 (GMT)
Cc: linux-net@vger.rutgers.edu
In-Reply-To: <MAPI.Id.0016.00636320202020204335414330303030@MAPI.to.RFC822> from "Carlos "M." Chamorro" at Mar 24, 96 10:55:19 pm
> my kernel ring buffer is full of messages like (orion is the server's name,
> and 194.224.37.1 is the router's address :)
>
> orion#/root dmesg -c
> redirect from 194.224.37.1
> redirect from 194.224.37.1
> redirect from 194.224.37.1
> .....
> I know those are ICMP redirect messages received from the router, but I
> cann't find any redirected route (i.e. D or M marked) on a netstat -r
> output.
Linux probably didnt believe the redirect because there is sufficient
configuration difference between the two.
> how can I see which route is intended to be redirected by the ICMP
> message so I con make up the route and forget about it?
Use tcpdump.
> why doesn't the route get redirected all alone so I would never have to
> worry again?
The kernel didnt believe it was right.
> do I have to recompile the kernel ( by the way, uname -r returns 1.2.1, I
> know a little bit old, but it works fine) using any bizzarre hidden option or
> should I power off the router so it shuts up forever loosing my internet
> connection and go to the beach for surfing the sea?
You can recompile the kernel to ignore ICMP redirect (current 1.3.x
kernels do this automatically if built as a router because ICMP redirect
is a router->host operation).
Alan
