home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.dcom.sys.cisco
- Subject: Re: Packet from Unknown Router
- Date: 18 Aug 1992 23:28:50 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 22
- Message-ID: <16s13iINN1om@early-bird.think.com>
- References: <9208172005.AA11873@spsgate.sps.mot.com>
- NNTP-Posting-Host: telecaster.think.com
-
- In article <9208172005.AA11873@spsgate.sps.mot.com> guri@apogee.sps.mot.com writes:
- >Aug 17 14:43:41 zztop syslog: packet from unknown router, 222.21.248.254
- >Aug 17 14:50:11 zztop last message repeated 349 times
-
- This is due to the use of secondary addresses. By default, Unix routed
- expects that it will only see routing table broadcasts from a router on its
- own subnet. But the cisco sends out a broadcast from each secondary
- address, so machines on each subnet are seeing the broadcasts from the
- other subnet on that cable.
-
- You can get rid of the warning by making the router a "known" router, by
- putting an entry for it in /etc/gateways, e.g.
-
- host 222.21.248.254 gateway 222.21.248.254 metric 3 active
-
- This routing entry will never actually be used, since you can only route
- via a host on your own subnet. But its existence keeps routed quiet.
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-