From owner-freebsd-questions Tue Jun 23 16:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06281 for freebsd-questions-outgoing; Tue, 23 Jun 1998 16:49:18 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from server6.singular.com (server6.singular.com [204.140.208.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06275 for ; Tue, 23 Jun 1998 16:49:13 -0700 (PDT) (envelope-from jbarbee@singular.com) Received: from singular.com ([204.140.208.136]) by server6.singular.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42397U400L100S0) with ESMTP id AAA340 for ; Tue, 23 Jun 1998 16:50:44 -0700 Message-ID: <35903F7D.28D3BC06@singular.com> Date: Tue, 23 Jun 1998 16:51:25 -0700 From: John Organization: Singular Solutions X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: Resolved: llinfo... source of many problems References: <358E8024.97C4D93B@singular.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well. 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. Before, route would complain that file already exists since de0, defaultrouter, netmask and broadcast was already configured by the dhcp client. 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. What's bizarre is that the netstat and ifconfig output from before and now are both the same. This probably is an indication that there is partially incompatible between the isc dhcp client and route. Does someone have a different take on this? Can anybody point me to where I can actually see what route is doing? TIA John wrote: > Hi, > Over the past couple of weeks I've tried ignoring this message > /kernel: arpresolve: can't allocate llinfo for 127.0.0.1 > but it pops up during Star Office and whenever I attempt to telnet > to port 80 of my ip address, 204.140.208.136 > > This is the output of my ifconfig -a and netstat -rn > > de0: flags=8843 mtu 1500 > inet 204.140.208.136 netmask 0xffffff00 broadcast > 204.140.208.255 > ether 00:80:48:e8:96:f3 > media: autoselect (10base2/BNC) status: active > lp0: flags=8810 mtu 1500 > tun0: flags=8010 mtu 1500 > sl0: flags=c010 mtu 552 > ppp0: flags=8010 mtu 1500 > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif > Expire > default 204.140.208.66 UGSc 4 61 de0 > 127.0.0.1 127.0.0.1 UH 1 124 lo0 > 204.140.208 link#1 UC 0 0 > 204.140.208.3 0:80:5f:48:68:28 UHLW 0 1268 de0 > 1070 > 204.140.208.6 0:60:b0:3c:cb:3d UHLW 0 0 de0 > 1154 > 204.140.208.7 0:60:b0:3c:cb:3d UHLW 0 2582 > de0 855 > 204.140.208.22 8:0:9:b4:6d:40 UHLW 0 427 de0 > 1109 > 204.140.208.66 0:0:a2:a:d4:7d UHLW 5 1766 > de0 834 > 204.140.208.136 127.0.0.1 UGHS 0 73 de0 > 204.140.208.138 0:c0:f0:14:6b:61 UHLW 0 73 de0 > 1109 > 204.140.208.232 0:60:b0:6b:a2:2c UHLW 0 12 > de0 687 > > I don't see anything wrong. I'm also not running routed. > > I should mention that I'm using the current version of ISC's dhcp > client. It's the one that sets my broadcast address, ip address and > hostnumber etc. That may be why there is an Sc flag for the first > routing entry, i don't know. > > rc does attempt set routes for me since rc.local knows the > defaultrouter, however, upon startup, rc gives this message > writing to routing socket: file exists > add net default: gateway 204.140.208.66: file exists > > Other than the llinfo message, this is the only indication that I have > that something is wrong. > > Does anyone have any ideas? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message