home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!news.claremont.edu!ucivax!noiro.acs.uci.edu!gordius!gordius!johnk
- From: johnk@gordian.com (John Kalucki)
- Subject: Re: RIP from secondary addresses
- Message-ID: <1992Aug13.005954.1384@gordian.com>
- Sender: news@gordian.com
- Organization: Gordian; Costa Mesa, CA
- References: <bsn37v.fyb@wang.com>
- Date: Thu, 13 Aug 1992 00:59:54 GMT
- Lines: 23
-
- In article <bsn37v.fyb@wang.com>, fitz@wang.com (Tom Fitzgerald) writes:
- >[...]
- >The problem is that RIP broadcasts only come from the primary interface, so
- >some systems with the secondary subnet number are blind to the routing
- >information.
- >[...]
-
- It's not only that, but the Cisco will send RIP responses containing
- valid routes to these secondary requests to RIP request broadcasts
- on the primary address. The machines on the primary net know routes
- to the secondary nets for a little while, and then their RIP entries
- time out.
-
- If you are going to put routes to the secondary interfaces in RIP
- responses to RIP requests from port 540, they should be in the
- normal RIP updates too.
-
- It's a great pump fake to think you have everything configured right
- and then WHAM!
-
-
- -John Kalucki
- johnk@gordian.com
-