SUMMARY: Packet from unknown router

From: Rick von Richter (rickv@mwh.com)
Date: Wed Aug 27 1997 - 18:04:16 CDT


ORIGINAL QUESTION
-----------------
We have a bunch of Cisco 2511 routers for internal routing to remote corp
sites.
We have just added secondary IP addresses to them and now I am getting these
messages on my workstation (Sparc 5);

Aug 25 08:46:38 scorpio in.routed[93]: packet from unknown router,
176.55.100.238

I have a Sparc 5 running 2.5.1. I have read the man page for in.routed. I have
added routes to these router interfaces and I have even tried adding an entry in
my /etc/gateways file. The new interfaces are on the 176.55.100.0 net and I
can't get my routing table netmask to go out to 3 octets (24 bits) on this
network. I tried adding routes to these routers in my routing table using this
command;
# route add net 176.55.100.0 191.41.100.148 1
My routing table entry looks like this;
Routing Table:
  Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
176.55.0.0 191.41.100.148 UG 0 0

I did make an entry in the /etc/inet/netmasks file which looks like this;
176.55.0.0 255.255.255.0
And it still won't work.

How can I make this router KNOWN instead of being an UNKNOWN router?
How can I get my routing table to go out to three octets?

SOLUTION
--------
Thanks to all the respondents. I had asked two questions. The first was how to
stop the 'unknown router' packets and the second was how to get a route to a
subnetted class B network.

The answer to the first question deals with in.routed's inability to understand
anything but RIP (thanks to Brian O'Mahoney). The routers in question are
running EIGRP so naturally in.routed doesn't know what to do with those packets.
 The solution is to shut off in.routed by adding an /etc/defaultrouter file
which contains the IP address of your defaultrouter. If you need to add more
routes then create a startup file (mine is /etc/rc2.d/S72iproutes) which then
adds routes at boot time. Thanks to Robert Glover for this one. I had actually
had this set up for some time on my main servers (shut off in.routed and have
static routes) but my workstation was still runing in.routed which is what
confused me.

The second question has yet to be answered. How do I create a static route to a
subnetted class B net. Example: remote network is 176.55.100.0 (subnetmask
255.255.255.0), gateway is 191.41.100.148 (subnet mask 255.255.0.0). The
machine I am doing this route on has an ip address of 191.41.100.158 subnet mask
(255.255.0.0). The entry in the /etc/inet/netmasks file looks like this;
176.55.0.0 255.255.255.0
and this is my route command;
# route add net 176.55.100.0 191.41.100.148 1
And when I do a 'netstat -nr' I get this;
Routing Table:
  Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
127.0.0.1 127.0.0.1 UH 0 1 lo0
176.55.0.0 191.41.100.148 UG 0 0
191.41.0.0 191.41.100.158 U 3 10 le0
224.0.0.0 191.41.100.158 U 3 0 le0
default 191.41.100.254 UG 0 8

I cannot get the 176.55 entry to go to 176.55.100.0
I believe I read somewhere that this is a shortcoming in Solaris. I sure hope
they fix it in 2.6.

Cheers,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Rick von Richter | Phone: 619-552-6222
  Systems/Network Admin | Fax: 619-552-6221
  Maintenance Warehouse | Email: rickv@mwh.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Science is true. Don't be misled by facts.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

P.S. A lot of people responded and I thank them but I lost the names.(Sorry) 8-(
Brian's and Robert's posts were the last two I received.



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:01 CDT