Date: Wed, 16 Jun 1999 19:03:41 -0400 (EDT) From: John Baldwin <jobaldwi@vt.edu> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-hackers@freebsd.org Subject: RE: DHCP, arp and de0 Message-ID: <199906162303.TAA17280@smtp1.erols.com> In-Reply-To: <XFMail.990616115748.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16-Jun-99 Daniel O'Connor wrote: > > On 16-Jun-99 John Baldwin wrote: >> Whoops.. just ifconfig de0. Have you tried using the interface? We use >> for a lab I help run, and 'arp -a' on the clients does not show an entry >> for >> the local de0 card they have installed, but they work fine regardless. Do >> have a route for 127.0.0.1 in your route table (netstat -rn), there should >> one that just points to itself so, AFAIK, it shouldn't be arp'ing for that >> address. > > Well I have a netstat -nr from when it was using DHCP and when it wasn't and > the only difference is the 'Refs' for 127.0.0.1 was 3 for DHCP and 2 for > static. Hmm. Here's what I have on one of our clients: # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default xxx.xx.184.1 UGSc 2 2 de0 127.0.0.1 127.0.0.1 UH 2 10 lo0 xxx.xx.184 link#1 UC 0 0 de0 xxx.xx.184.66 127.0.0.1 UGHS 0 0 lo0 xxx.xx.184.255 ff:ff:ff:ff:ff:ff UHLWb 1 896 de0 As you can see, only 2 refs for 127.0.0.1. Note that there is a route for de0's IP: xxx.xx.184.66 to 127.0.0.1. Do you have lo0 configured properly (is lo0 in network_interfaces in /etc/rc.conf and ifconfig_lo0 in either /etc/rc.conf or /etc/defaults/rc.conf)? > The interface works OK for somethings, but for example I can't run 'esd', and > whenever I try and ping the address assigned to the ethernet card I get > Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0.1 failed: could not allocate > llinfo > Jun 13 17:35:21 guppy /kernel: arpresolve: can't allocate llinfo for > 127.0.0.1rt > > every ping packet sent. Don't have esd to test with, but I can ping it's own IP fine. I'd be willing to bet, though, that esd not working is a symptom of the same problem since a client talking to a server on the same host usually uses the lo0 interface. It really sounds like your lo0 isn't configured. What version of FreeBSD are you running? --- John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906162303.TAA17280>