We have a FreeBSD 3.1R machine as our main router uplinking to a
Cisco 3620 (back to back, no switch).
All works well, and had for months. After a reboot of cisco and
freebsd, all still works well, but we cannot ping cisco inside to
fbsd outside (the back to back interfaces with x-over cable), plus
when we traceroute up to internet, all we get is * * * when
traversing that link, followed by normal traceoute behavior.
This link carries several a gigabyte of traffic a day in both
directions without pb's, but we have this problem with that link.
dmesg shows tons of:
arpresolve: can't allocate llinfo for 255.255.255.252rt
arplookup 255.255.255.252 failed: host is not on local network
arpresolve: can't allocate llinfo for 255.255.255.252rt
arplookup 255.255.255.252 failed: host is not on local network
arpresolve: can't allocate llinfo for 255.255.255.252rt
and /var/log/messages shows:
Jan 16 18:03:49 gw1 /kernel: arplookup 255.255.255.252 failed: host
is not on local network
Jan 16 18:03:49 gw1 /kernel: arpresolve: can't allocate llinfo for
255.255.255.252rt
Jan 16 18:03:51 gw1 /kernel: arplookup 255.255.255.252 failed: host
is not on local network
Jan 16 18:03:51 gw1 /kernel: arpresolve: can't allocate llinfo for
255.255.255.252rt
Jan 16 18:03:52 gw1 /kernel: arplookup 255.255.255.252 failed: host
is not on local network
Jan 16 18:03:52 gw1 /kernel: arpresolve: can't allocate llinfo for
255.255.255.252rt
255.255.255.252 is of course not an ip address but a netmask on the
two of the 3 xl0 cards in that machine.
ifconfig -a shows nothing strange
stumped
Len
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
