FreeNAS uses 2 IP addresses on 1 interface?

[Fantomas]

Hi,
few days back I upgraded FreeNAS 9.2.1.4 to 9.2.1.5 and then one PC on my network started reporting IP address conflict with another system. After quick investigation I found that the conflicting system was FreeNAS with only port 22 open (I simply shut the server down and the conflict was gone).

What's strange to me: This exact FreeNAS before upgrade to the latest version was running for months without any problems always sitting on IP 192.168.1.178. After upgrade it's IP was still the same, but also it had taken/stolen IP .180 from another computer (DHCP lease).

Even after setting IP .180 on the PC to manual setup, the problem still occured. I even set NIC MAC and IP of that PC on DHCP server, but the problem still exists.

Why is FreeNAS using two IPs (the server has two NICs, but only one has been set and has a cable plugged in). MAC of that ghost IP is 02:90:05:00:09:0b, which doesn't exist by the way :D
Why is it using .180 which was possibly not given by the DHCP server, because it's been leased to another computer?
Or what am I missing here? ;)

Thank you.

 

[dlavigne]

Post the output of ifconfig from the FreeNAS system.

 

[joeschmuck]

Are you using any plugins? Plugins typically take an IP address, sometimes it's incremental from the main machine address. You can change those in the plugin configuration. To test it out, start turning of your plugins.

 

[Fantomas]

@joeschmuck: Installed "clashplan 3.5.3", but is turned off.

@dlavigne:
ifconfig:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:25:90:aa:94:08
inet 192.168.1.178 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:25:90:aa:94:09
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier
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 0x6
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:5b:39:cd:3c: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: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 8 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:b1:09:00:08:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

 

[joeschmuck]

In the GUI upper ICON menu select Jails. Listed will be any jail you have installed and the IP address. Does this help?

And if you do not see any issues, reboot your router that issues the DHCP IP addresses, it may be releasing on to the 192.168.1.180.

Also, if you are going to use static IP's you should map them on paper or in some file.

 

[indy]

My router does not like 2 IPs on one interface very much as well.
Is there maybe a way to dedicate a physical lan-connection to a jail?

 

[joeschmuck]

Not sure what you mean that your router doesn't like 2 IPs on a single ethernet connection, well I understand but I find it hard to believe. I find that very hard to believe to be honest unless you have some very crappy third party firmware running on the router. But I don't know how to dedicate a jail to a second NIC, I'm sure this topic has come up in the past so a search of the forums should provide the answer.

 

[indy]

It screws with port forwarding (and other per-ip/interface) settings.
For example: I set a rule for port forwarding to 192.168.1.12 (the jail's ip), just checked it again and sure enough the rule changed to 192.168.179.20 for whatever reason.

 

[joeschmuck]

You are not using third party firmware on your router are you? If not then I'd say you need a new router because that should never happen. Of course I'm assuming you know how to setup advanced router settings and not messing something else up as well. Also we are stealing someone elses thread so we should stop.

 

[Fantomas]

@joeschmuck: Thank you for pointing me to the right place - crashplan had that .180 IP address in jails... As I'm quite new to FreeNAS I even didn't know about such a behaviour (crashplan was disabled!).
Removed crashplan, deleted its jail and I'm back running, exactly what I needed! ;)

Thank you once again!

 

[joeschmuck]

You can change the IP address of the jails in the jail configuration should you want to use them.