Help on freenas.local kernel log messages

[cr2069]

I am new to FreeNAS, just setup my first NAS and it works great! However, I do have some issues to try to understand. Maybe it's an old topic, I did some search but couldn't find the answer I am looking for.

First, I keep getting these kernel log messages(through the email I set up), though not everyday. For example, here is a typical one:

> arp: 192.168.0.250 moved from 68:1c:a2:01:4a:62 to e8:94:f6:c3:69:32 on re0
> arp: 192.168.0.250 moved from e8:94:f6:c3:69:32 to 68:1c:a2:01:4a:62 on re0
> arp: 192.168.0.250 moved from 68:1c:a2:01:4a:62 to e8:94:f6:c3:69:32 on re0
> arp: 192.168.0.250 moved from e8:94:f6:c3:69:32 to 68:1c:a2:01:4a:62 on re0
> arp: 192.168.0.250 moved from 68:1c:a2:01:4a:62 to e8:94:f6:c3:69:32 on re0

Can anyone help me to understand what this means?

Second, since I setup my FreeNAS system and connected to the router, I found some IP conflicts(seems to be) which resulted some other devices could not connected to network unless I remove the static IPs assigned to those devices. I suspect it's related to FreeNAS and above kernel log message. Be more specific, I have a computer which I assign the local IP as 192.168.0.250 and worked fine before, after I put my FreeNAS system in the network, running for a few days, the 192.168.0.250 computer cannot connect to network anymore, then I got the above message next day. If I remove the static IP assigning, changes it to dynamic IP, then it works again and no more such problem. It happened to few other computers too, so I can't use static IP because of FreeNAS? My FreeNAS system has a static IP of 192.168.0.11 in my local network.

Thanks for any help or explanation!

 

[L]

It looks like you have 2 devices on the same IP address. Maybe try using a different IP address on the .250 host.

 

[cr2069]

It looks like you have 2 devices on the same IP address. Maybe try using a different IP address on the .250 host.

I suspect that too. However, I couldn't figure out why, and don't know whether it's caused by the FreeNAS system or not. Because I didn't have that problem before I put my FreeNAS system in the network, some devices are bound to specific IPs(local), and the FreeNAS is also bound to specific one. Now, others cannot be bound to those IPs, it seems that these IPs are used by others(I don't know how it happened this way). That's why I tried to understand the log messages above.

 

[L]

try....

open a shell and type #arp -a

and

#ifconfig -a

I would guess it is the freenas box that has the .250 config'ed somehow.

 

[cr2069]

try....

open a shell and type #arp -a

and

#ifconfig -a

I would guess it is the freenas box that has the .250 config'ed somehow.

Thanks, I will try it tonight.

FreeNAS system is bound to 192.168.0.11 in my local network, it shouldn't have anything to do with 192.168.0.250(in theory) ...anyway, not only 192.168.0.250 is affected, other static IPs like 192.168.0.150 etc. are also having same problem, and it sends out similar kernel log message like above.

 

[L]

What I would expect to see is the freenas box with an interface assigned the 192.168.0.250 IP. You would be able to see that with ifconfig -a.. It is just a suspicion though, and I would have no idea how it got like that, maybe it dhcp'ed and then got set static.

 

[anodos]

Typically on a network I will designate static and dynamic address ranges.

For instance the DHCP server will only assign 192.168.0.50 - 192.168.0.200

When I need to set a static address I set it outside that range. This prevents address conflicts.

This works great until a third-party tech from the printer company comes in and plops a printer on a static address in your dynamic range. In that case you don't have to worry because the tech has a wonderful combination of laziness and incompetence that causes him to set admin passwords to '1234' allowing you to fix the problem. Speaking hypothetically of course.

 

[rogerh]

To extend the helpful parable above, you need to look at the kit on your network that is providing DHCP services. Possibly a router with a web admin interface? Either change the range of addresses it is allowed to assign (which should be less than all 256 in the 192.168.0.* range) or if it is not easily changeable assign your fixed IP addresses outside that range. Have you got jails or anything in Freenas that could be using any address apart from the one you have assigned? If not it does not seem to be a problem with Freenas, just that the Freenas box is logging the problem!