Jail connectivity and routing

[Hollajandro]

As of my upgrade to 9.2.1 I am getting an error on boot regarding my jail networking startups and I cannot ping my gateway or access anything on the other side of my gateway from inside my jails. I can however ping anything on my local subnet. Networking works correctly outside of the jails. This is what I see at the console at boot time after the execution of the jail -c command:

Setting IP4 address: 192.168.30.211/24
add net default: gateway 192.168.30.254
jexec 3 arp -s 192.168.30.211 94:44:52:14:a1:b7
fi
#
# No defaultrouter configued for IPv4, so if bridge IP address was
# configured, we set the default router to that IP.
#
elif [ -n ] ; then
local ether=94:44:52:14:a1:b7
get_ip_and_netmask
if [ != YES ] ; then
jexec 3 route add -inet default 192.168.30.211
else
jexec 3 route add default gateway 192.168.30.211
fi
if [ -n 94:44:52:14:a1:b7 ] ; then
get_ip_and_netmask :: Unknown server error
route: writing to routing socket: File exists
add net default gateway 192.168.30.254: route already in table

Then it continues to load the rest of the jails. Has anyone seen this happen? I have tried flushing my routes to no avail.

EDIT:

If I add aliases for the interface I can then ping the router and get outside of my network.


Jail:

root@mythbackend:/ # netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
127.0.0.1 link#1 UH 0 5421 lo0
192.168.30.0/24 link#2 U 0 155 epair0
192.168.30.213 link#2 UHS 0 0 lo0

Internet6:
Destination Gateway Flags Netif Expire
::1 link#1 UH lo0
fe80::%lo0/64 link#1 U lo0
fe80::1%lo0 link#1 UHS lo0
ff01::%lo0/32 ::1 U lo0
ff02::%lo0/32 ::1 U lo0
root@mythbackend:/ #

root@mythbackend:/ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:a5:c3:00:0f:0b
inet 192.168.30.213 netmask 0xffffff00 broadcast 255.255.255.255
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
root@mythbackend:/ #

Host:

[root@storage] /etc# netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.30.254 UGS 0 243 re0
127.0.0.1 link#12 UH 0 22997 lo0
192.168.30.0/24 link#1 U 0 24644 re0
192.168.30.136 link#1 UHS 0 35 lo0
Internet6:
Destination Gateway Flags Netif Expire
::/96 ::1 UGRS lo0
::1 link#12 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::/10 ::1 UGRS lo0
fe80::%lo0/64 link#12 U lo0
fe80::1%lo0 link#12 UHS lo0
ff01::%lo0/32 ::1 U lo0
ff02::/16 ::1 UGRS lo0
ff02::%lo0/32 ::1 U lo0
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 94:de:80:7a:b4:00
inet 192.168.30.136 netmask 0xffffff00 broadcast 192.168.30.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
pflog0: flags=0<> metric 0 mtu 33152
nd6 options=9<PERFORMNUD,IFDISABLED>
pfsync0: flags=0<> metric 0 mtu 1500
nd6 options=9<PERFORMNUD,IFDISABLED>
syncpeer: 0.0.0.0 maxupd: 128
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xc
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:c0:1f:34:28:00
nd6 options=1<PERFORMNUD>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 17 priority 128 path cost 2000
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 16 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 15 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 14 priority 128 path cost 2000
member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:10:f5:00:0e:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:d8:3a:00:0f:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:0c:d4:00:10:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:a8:4a:00:11:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

 

[dlavigne]

Did this ever get sorted?

 

[Hollajandro]

No. Even if I set new static ips in the freenas interface that are different and use the old ones (the jails initial real ips) as aliases, the aliases do not work to ping my router or anything outside my network. Seems like something is holding those specific ips in the freenas configs and it's messing it all up.

 

[dlavigne]

Can you check if there is a similar report at bugs.freenas.org? If not, create one and post the issue number here.