Freebsd 12.3-RELEASE-p2
py38-iocage-1.2_9
The host server for a number of jails was restarted last night. This morning I discover that one of the jails did not start. The reason for this is:
The address in question is 192.168.216.108/16. It is not in use elsewhere on the network:
It appears that this may be the only ip address that causes this failure.
No other jail has 192.168.216.108 assigned, nor is it listed in
I have likewise tested .110 and .107. These work. But .108 causes the address clash. What could be causing this?
py38-iocage-1.2_9
The host server for a number of jails was restarted last night. This morning I discover that one of the jails did not start. The reason for this is:
Code:
#
# iocage get ip4_addr pas-redmine-2
em1|192.168.216.108/16
iocage start pas-redmine-2
* Starting pas-redmine-2
+ Start FAILED
jail: ioc-pas-redmine-2: IPv4 addresses clashThe address in question is 192.168.216.108/16. It is not in use elsewhere on the network:
Code:
# ping 192.168.216.108
PING 192.168.216.108 (192.168.216.108): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is downIt appears that this may be the only ip address that causes this failure.
Code:
# iocage get ip4_addr pas-redmine-2
em1|192.168.216.109/16
# iocage start pas-redmine-2
* Starting pas-redmine-2
+ Started OK
+ Using devfs_ruleset: 1015 (iocage generated default)
+ Using IP options: ip4.addr=em1|192.168.216.109/16 ip4.saddrsel=1 ip4=new ip6.saddrsel=1 ip6=new
+ Starting services OK
+ Executing poststart OKNo other jail has 192.168.216.108 assigned, nor is it listed in
ifconfig, nor does a ping on the network reveal its use anywhere else.I have likewise tested .110 and .107. These work. But .108 causes the address clash. What could be causing this?