Hallo sun-manager,
that's great. In less than one day I got a whole bunch of good
answers to my problem:
We get this message and don't know how to get rid of it. It doesn't seem
to do any harm on our system ( Solaris 2.3 ) but the logfile grows...
in.routed: packet from unknown router 123.45.98.98
Can someone help?
The responses came from:
stern@sunrise.East.Sun.COM
yves@cc.mcgill.ca
harishm@pcsdnfs1.eq.gs.com
Tim.Tokarsky@dssserv.fw.gs.com
symanski@gold.nosc.mil
derrickh@ecl.psu.edu
jls2013@tntech.edu
Thanks to all of you !!!
The responses:
it means you are getting RIP packets from a machien that isn't
on your IP network. are you running two IP networks on the
same wire?
-- I would assume that this machine that has an IP adress of w.x.y.z (thus is in the y subnet) is not physically connected to the Y subnet but it is connected to another subnet, probably 98 based on this message:in.routed: packet from unknown router 123.45.98.98
It means that the router interface for the 98 subnet is routing packets to your machine but since the IP adress of the machine does not match the subnet it was supposed to be on, the router is considered unknown to the machine because a route given to routed makes routed expect packets from the router interface for subnet y.
The solution is to physically connect the machine to the right subnet. Note that this will cause problem to other machines on both subnets: y and 98. --
delete the route entry, try to grab it from netstat -r | grep 123.45.98.98 and use route command to delete the static route.
-- A host ,whom you do not know as a router, is sending you RIP. You can find out who that is and stop the rip or you can reboot the first machine. ( If you can't reboot you may have to start and stop in.routed.
--
I had this problem about a year ago. Try turning off the routed on your systems if your systems are not routers(?).
kill 'in.routed' \and/ create a file "/etc/defaultrouter" that contains the address of your default router. You can read "/etc/rc.local" to see the effect of having that file there. It sets the default and also forces routed to not start.
--
We had the same problem, you can get rid of this by killing in.routed or the more appropriate way to diminish the problem is to setup the network properly. what is happening is that it is using a routed that is a default to you machine but not known to your network. we give the command after booting to be ifconfig le0 128.118.55.19 netmask 255.255.255.0 broadcast 128.118.55.255 route add default 128.118.55.1 1 the two command lines above helped on our machine which is 128.118.55.19 change the commands to suit you machine and it may work. hope this helps. --
>>> I can ping that number, and find it in my domain name server. and do a >>> reverse address lookup to the address. what else does the system mean >>> by unknown router. >> >>An unknown router is one that isn't on the same subnet as the local machine >>and isn't in /etc/gateways. You can get that message if you are running >>multiple subnets on a single cable and sending RIP broadcasts to the >>255.255.255.255 address (instead of <net>.<subnet>.255); we noticed it when >>we configured a "secondary address" on our cisco router. >> >>You can suppress the complaints by adding an entry for the router to >>/etc/gateways and restarting in.routed. >>-- >> >>this exactly the situation and the fix works. >> -- >>I found the description of /etc/gateways in the man page for 'routed' after >>I had mailed both of you. -- >>net 129.243 gateway 129.243.52.233 metric 0 active >>net 160.205 gateway 129.243.52.233 metric 0 active >>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:03 CDT