IMPORTANT! Network is unreachable
KES
kes-kes at yandex.ru
Sat Aug 9 10:24:25 UTC 2008
# uname -a
FreeBSD gorodok.kes.net.ua 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #0: Sun Aug 3 13:18:21 EEST 2008 kes at gorodok.kes.net.ua:/usr/obj/usr/src/sys/KES_KERN_v7 i386
# netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.11.16.1 UGS 0 3758 rl0
10.0.0.0/16 10.11.16.2 UG 0 150 rl0
10.11.15.0/24 link#2 UC 0 0 rl1
10.11.16.0/24 link#1 UC 0 0 rl0
10.11.16.1 00:e0:4c:59:50:7e UHLW 2 421 rl0 953
10.11.16.2 00:03:79:01:9b:d0 UHLW 2 0 rl0 786
127.0.0.1 127.0.0.1 UH 0 122 lo0
Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#4 UHL lo0
ff01:4::/32 fe80::1%lo0 UC lo0
ff02::%lo0/32 fe80::1%lo0 UC lo0
# ifconfig rl0
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:0e:2e:db:4f:d4
inet 10.11.16.14 netmask 0xffffff00 broadcast 10.11.16.255
inet 10.11.16.9 netmask 0xffffff00 broadcast 10.11.16.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
# ifconfig rl0 add 10.10.16.3/28
# ifconfig rl0
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 00:0e:2e:db:4f:d4
inet 10.11.16.14 netmask 0xffffff00 broadcast 10.11.16.255
inet 10.11.16.9 netmask 0xffffff00 broadcast 10.11.16.255
inet 10.10.16.3 netmask 0xfffffff0 broadcast 10.10.16.15
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
# netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.11.16.1 UGS 0 2751 rl0
10.0.0.0/16 10.11.16.2 UG 0 142 rl0
10.10.16.0/28 link#1 UC 0 0 rl0
10.10.16.3 00:0e:2e:db:4f:d4 UHLW 1 6 lo0
10.11.15.0/24 link#2 UC 0 0 rl1
10.11.16.0/24 link#1 UC 0 0 rl0
10.11.16.1 00:e0:4c:59:50:7e UHLW 2 119 rl0 1176
10.11.16.2 00:03:79:01:9b:d0 UHLW 2 0 rl0 1093
127.0.0.1 127.0.0.1 UH 0 122 lo0
Internet6:
Destination Gateway Flags Netif
Expire
::1 ::1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#4 UHL lo0
ff01:4::/32 fe80::1%lo0 UC lo0
ff02::%lo0/32 fe80::1%lo0 UC lo0
After 5 min:
# netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.11.16.1 UGS 0 2859 rl0
10.0.0.0/16 10.11.16.2 UG 0 142 rl0
10.10.16.0/28 link#1 UC 0 0 rl0
10.10.16.3 00:0e:2e:db:4f:d4 UHLW 1 6 lo0
10.11.15.0/24 link#2 UC 0 0 rl1
10.11.16.0/24 10.11.16.14 UGC 1 0 rl0
10.11.16.1 10.11.16.14 UGHW 1 298 rl0
127.0.0.1 127.0.0.1 UH 0 122 lo0
Internet6:
Destination Gateway Flags Netif
Expire
::1 ::1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#4 UHL lo0
ff01:4::/32 fe80::1%lo0 UC lo0
ff02::%lo0/32 fe80::1%lo0 UC lo0
Notice second link#1 disappeared
# cat /var/log/messages
Aug 9 12:54:58 gorodok kernel: arplookup 10.11.16.14 failed: host is not on local network
Aug 9 12:54:58 gorodok kernel: arpresolve: can't allocate route for 10.11.16.14
Aug 9 12:54:59 gorodok kernel: arplookup 10.11.16.14 failed: host is not on local network
Aug 9 12:54:59 gorodok kernel: arpresolve: can't allocate route for 10.11.16.14
Aug 9 12:55:00 gorodok kernel: arplookup 10.11.16.14 failed: host is not on local network
Aug 9 12:55:00 gorodok kernel: arpresolve: can't allocate route for 10.11.16.14
Aug 9 12:59:59 gorodok kernel: arplookup 10.11.16.1 failed: host is not on local network
Aug 9 12:59:59 gorodok kernel: arpresolve: can't allocate route for 10.11.16.1
Aug 9 12:59:59 gorodok kernel: arplookup 10.11.16.1 failed: host is not on local network
Aug 9 12:59:59 gorodok kernel: arpresolve: can't allocate route for 10.11.16.1
And this repeats each 5min
#netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.11.16.1 UGS 0 2902 rl0
10.0.0.0/16 10.11.16.2 UG 0 145 rl0
10.10.16.0/28 link#1 UC 0 0 rl0
10.10.16.3 00:0e:2e:db:4f:d4 UHLW 1 6 lo0
10.11.15.0/24 link#2 UC 0 0 rl1
10.11.16.0/24 link#1 UC 0 0 rl0
10.11.16.1 00:e0:4c:59:50:7e UHLW 1 2 rl0 1199
127.0.0.1 127.0.0.1 UH 0 122 lo0
Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#4 UHL lo0
ff01:4::/32 fe80::1%lo0 UC lo0
ff02::%lo0/32 fe80::1%lo0 UC lo0
Another 5 min left and this line appears again
10.11.16.0/24 link#1 UC 0 0 rl0
It seems this bug appears when multiple nets appear on same interface on 7.0-RELEASE-p3
on 7.0-STABLE this bug appears when you start routed daemon.
In FreeBSD 6.3 this bug does not appear
More information about the freebsd-stable
mailing list