Date: Thu, 25 Jun 1998 09:10:34 -0700 From: John <jbarbee@singular.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: Resolved: llinfo... source of many problems Message-ID: <3592767A.C8A996D3@singular.com> References: <Pine.BSF.3.96.980624211503.29163l-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White wrote: > On Tue, 23 Jun 1998, John wrote: > > > Originally, within /etc/rc, I placed the call to the dhcp client before > > all the other network stuff was set up. This time I removed de0 from > > rc.conf and placed the dhcp client after all the other network stuff was > > done. Now apache responds right away and I don't get the llinfo error > > anymore. This seems more like a bandage than a solution. > > IOt's correct .. if you read the dhclinet docs you're not supposed to > configure the ethernet interface beforehand. > should've read it, sorry > > Now, route complains that network is unreachable since de0 hasn't been > > configured yet. In fact, default router and other settings probably > > don't happen until the dhcp client sets them up. All indications show > > that route is failing to set the routes. > > Make sure you're running that route add after the dhclient run completes. > I thought dhclient runds the `route add default xx' automatically. > it does. which is probably why netstat shows the correct information. the network unreachable error happens when rc tried to route add default, which is before dhclient configures de0. that why i say that dhclient doesn't really blend too well with rc. > 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?3592767A.C8A996D3>