|
This one fell through the cracks on the questions list… probably cause
its not a simple question… or at least I would like to think so ;-) It is regarding an error occurring in the route table on various
machines under various configurations.
The one similarity is dhclient. Read below… I was fairly detailed with the description of the problem… thanks! Aaron Sonntag -----Original
Message----- I HAVE THIS PROBLEM TOO… I am not sure what causes it… but if you do a netstat
–rn I am sure you will see that the route to your nic interface address is
pointing to 127.0.0.1 instead of a mac address (as show below under
[BEFORE]). Do a ‘route delete
[interface address]’… for instance in the example below… I type ‘route delete
216.140.184.45’. Then ping the
interface and run netstat –rn again and you will see (as shown below under
[AFTER]) that the mac addy will appear and the machine will be happy. Temporarily L [BEFORE] Internet: Destination Gateway
Flags
Refs
Use Netif
Expire default
216.140.184.33
UGSc
11 2528899 rl0 10.0.1/24 link#3
UC
0 0 mx1 127.0.0.1
127.0.0.1 UH
2
80
lo0 216.140.184.32/27 link#1
UC
0 0 rl0 216.140.184.45 127.0.0.1 UGHS
0 232 rl0 [AFTER] Internet: Destination Gateway
Flags
Refs
Use Netif
Expire default
216.140.184.33
UGSc
11 2528999 rl0 10.0.1/24 link#3
UC 0
0
mx1 127.0.0.1
127.0.0.1 UH
1
80
lo0 216.140.184.32/27 link#1
UC
0 0 rl0 216.140.184.45 0:4f:4e:1:1a:88 UHLW 0
2
lo0 A
friend/coworker of mine helped me with this temporary fix (THANKS DAVID!). But he seemed to think it was a larger
issue with the dhclient script. I
have had this problem on three different 3.3 machines on three COMPLETELY
different networks and the one similarity between them was dhclient. Two of them were nat boxes on RR and
one is a workstation. To reinforce
this theory… on the nat boxes that have the problem… its only the interfaces
that are getting dhcp via dhclient that have the problem. My point is… the above is a temporary solution. The following message will completely flood my dmesg
buffer until the machine stops responding… arplookup 127.0.0.1 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 127.0.0.1rt anybody have any permanent solutions?? Thanks Aaron Sonntag -----Original
Message----- I
just installed freebsd 3.3 stable and i keep getting this message: /kernet:
arplookup 127.0.0.1 failed: can't allocate llinfo /kernet
arpresolve can't allocate llinfo for 127.0.0.1 any
idea what is causing this and how i can fix it? Thanks zshack |
