Date: Mon, 13 Apr 1998 15:53:15 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: "Cambria, Mike" <MCambria@lucent.com> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG> Subject: RE: Router Discovery using routed(8) Message-ID: <Pine.BSF.3.96.980413155107.5663X-100000@gdi.uoregon.edu> In-Reply-To: <813D2854D1B0D1118236006097177581036ACE@smtp.Lucentmmit.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Apr 1998, Cambria, Mike wrote: > > >224.* is the multicast network. It may not be set up correctly on your > >router(s) but you still have static references in /etc/rc.conf. Unless > >you're using multicast you can ignore these. > > But I can't ignore these. The router solicitations sent by routed never > hit the wire. Thus a router is never discovered. The route table has > just 2 entries, 127.0.0.0 and the one for the local LAN. Odd. The routed broadcasts should end up on the locally attached network, if multicast fails (and I don't recall RIP using multicast). If your router is set up properly then it should reply there. > When I use gated for router discovery client (with multicast) I do *not* > see the problem I described with routed. Routed is pretty stupid as far as routing daemons go. Gated is miles ahead in intelligence. I'd suggest checking the routed manpage and/or relevant documentation (the UNIX sysadmin red book comes to mind). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980413155107.5663X-100000>