9.3 gets IP of jail

[mrreload]

After I updated to 9.3, FreeNAS is getting the IP of one of the jails.
I was changing some settings to see if ipv4 truly worked in jails now.
Even after reverting back to original settings, the jail IP is getting used by Freenas itself!!!
Very confused here, help?
ifconfig output below. FYI the jail still works, but I had to change the webgui port of FreeNAS or else I would get directed to FreeNAS when I was trying to get to the webserver in the jail.

From FreeNAS:
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=80099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
ether 00:1e:4f:f3:db:46
inet 192.168.1.143 netmask 0xffffff00 broadcast 192.168.1.255 <<<FreeNAS IP
inet 192.168.1.23 netmask 0xffffff00 broadcast 192.168.1.255 <<<belongs to Jail
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active

And then the Jail:
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=80099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
ether 00:1e:4f:f3:db:46
inet 192.168.1.23 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active

I have a feeling I need to rebuild all my Jails after the update, but just not ready to do that quite yet.

 

[dlavigne]

This command on the FreeNAS system should fix it: ifconfig bge0 192.168.1.23 delete .

 

[mrreload]

That command did work, however I added a new jail via plugin (cruciblewds) and it did the same thing. Is this a possible bug?

 

[dlavigne]

That is weird... If you report a bug at bugs.freenas.org, post the issue number here.

 

[ahcim_74]

Hi, I've got exactly the same problem, did you find a solution?