Check this out...
Do you see that? This exact same ping WORKED under FreeBSD 12.3 just fine, zero config. changes, but now is failing. There are no other FIBs, just the usual default one. And the primary ethernet interface talks on a tagged VLAN. Its alias IP addresses now cannot talk to any loopback IP or any of the loopback alias IPs.
This is a PUZZLER!
Suggestions where to look? There is a firewall, ipfw, that permits all traffic.
IDEAS? Have you seen this before?
I discovered this after a jail (using an alias IP on the 10.0.0.x network) suddenly could no longer talk to a process in a different jail (a web server running on one of the localhost 127.0.0.x alias IPs) after an upgrade using freebsd-update from 12.3 to 13.0.
HELP!
Thanks for any pointers!
Aaron Gifford
Code:
[root@host /conf]# ifconfig
em0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=481249b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LRO,WOL_MAGIC,VLAN_HWFILTER,NOMAP>
ether 00:30:48:d5:c4:f1
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xffffff00
inet 127.0.0.2 netmask 0xffffffff
inet 127.0.0.3 netmask 0xffffffff
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
em0vlan10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4000403<RXCSUM,TXCSUM,LRO,NOMAP>
ether 00:30:48:d5:c4:f1
inet 10.0.0.100 netmask 0xffffff00 broadcast 10.0.0.255
inet 10.0.0.101 netmask 0xffffffff broadcast 10.0.0.101
inet 10.0.0.102 netmask 0xffffffff broadcast 10.0.0.102
groups: vlan
vlan: 10 vlanproto: 802.1q vlanpcp: 0 parent interface: em0
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
[root@host /conf]# ping -S 127.0.0.1 10.0.0.100
PING 10.0.0.100 (10.0.0.100) from 127.0.0.1: 56 data bytes
64 bytes from 10.0.0.100: icmp_seq=0 ttl=64 time=0.065 ms
64 bytes from 10.0.0.100: icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from 10.0.0.100: icmp_seq=2 ttl=64 time=0.059 ms
^C
--- 10.0.0.100 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.044/0.056/0.065/0.009 ms
[root@host /conf]# ping -S 127.0.0.1 10.0.0.101
PING 10.0.0.101 (10.0.0.101) from 127.0.0.1: 56 data bytes
ping: sendto: Can't assign requested address
ping: sendto: Can't assign requested address
ping: sendto: Can't assign requested address
^C
--- 10.0.0.101 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
[root@host /conf]# ipfw list
00090 allow ip from any to any
65535 deny ip from any to any
This is a PUZZLER!
Suggestions where to look? There is a firewall, ipfw, that permits all traffic.
IDEAS? Have you seen this before?
I discovered this after a jail (using an alias IP on the 10.0.0.x network) suddenly could no longer talk to a process in a different jail (a web server running on one of the localhost 127.0.0.x alias IPs) after an upgrade using freebsd-update from 12.3 to 13.0.
HELP!
Thanks for any pointers!
Aaron Gifford