Date: Sun, 15 Mar 2009 11:50:11 +0100 From: Martin <nakal@web.de> To: <current@freebsd.org> Subject: arpresolve: can't allocate llinfo for 192.168.0.1 Message-ID: <20090315115011.4f627373@zelda.local>
next in thread | raw e-mail | index | archive | help
Hi,
sometimes (not every time) I have problems with networking right after
booting my desktop.
The NIC (re) is usable, because my IPv6 services are accessible, but
IPv4 is unroutable.
In syslog there are these two lines (multiple repeats):
IPv4 address: "192.168.0.1" is not on the network
arpresolve: can't allocate llinfo for 192.168.0.1
I can fix the situation by these commands:
# ifconfig re0 192.168.0.12
# route add default 129.168.0.1
This has happened two times on my PC so far. I'm not totally sure, but
I've seen this problem the first time with a kernel from March 9th.
NIC is:
re0@pci0:4:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec
rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
class = network
subclass = ethernet
ifconfig (while working):
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
ether xx:xx:xx:xx:xx:xx inet6 fexx::xxxx:xxxx:xxxx:xxxx%re0 prefixlen 64
scopeid 0x1 inet6 2002:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64
autoconf inet6 fdxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64
autoconf inet 192.168.0.12 netmask 0xffffff00 broadcast 192.168.0.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
Kernel is:
FreeBSD zelda.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Mar 12
18:39:52 CET 2009 root@zelda.local:/usr/obj/usr/src/sys/ZELDA amd64
--
Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090315115011.4f627373>