arp moved from ... ( not similar to other cases )

[Plato]

Hi,

I know there are a lot of mails about this problem but AFAIS what I have is a different problem then the others.

I'm using FreeNAS-11.1-U1

This is an excerpt from the log:

Code:

arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:68 to xx:xx:xx:xx:xx:0a on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:68 to xx:xx:xx:xx:xx:0a on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:68 to xx:xx:xx:xx:xx:0a on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:68 to xx:xx:xx:xx:xx:0a on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b
arp: 192.168.1.250 moved from xx:xx:xx:xx:xx:0a to xx:xx:xx:xx:xx:68 on epair0b

Mac ending with :68 is igb0, other mac ending with :0a is for epair0a..

The thing is there is no interface named epair0b when I run ifconfig.

There are igb0 which is FreeNas ethernet interface, igb1 which is N/C secondary ethernet interface, lo0 (loop), bridge0 (iohyve), epair0a and epair1a for the jails.. 192.168.1.250 is my FreeNas's own IP (not jail).

What could be the cause for this?

 

[Plato]

Just wanted to add additional information from "dmesg":

Code:

igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xc000-0xc01f mem 0xdc100000-0xdc17ffff,0xdc180000-0xdc183fff irq 22 at device 0.0 on pci6
igb0: Using MSIX interrupts with 5 vectors
igb0: Ethernet address: xx:xx:xx:xx:xx:68
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
igb0: Bound queue 2 to cpu 2
igb0: Bound queue 3 to cpu 3
igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xd000-0xd01f mem 0xdc200000-0xdc27ffff,0xdc280000-0xdc283fff irq 23 at device 0.0 on pci7
igb1: Using MSIX interrupts with 5 vectors
igb1: Ethernet address: xx:xx:xx:xx:xx:67
igb1: Bound queue 0 to cpu 4
igb1: Bound queue 1 to cpu 5
igb1: Bound queue 2 to cpu 6
igb1: Bound queue 3 to cpu 7
igb0: link state changed to UP
epair0a: Ethernet address: xx:xx:xx:xx:xx:0a
epair0b: Ethernet address: xx:xx:xx:xx:xx:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: promiscuous mode enabled

As you can see there is an "epair0b" here but it doesn't show up after boot in ifconfig.

There are also cases like this:

Code:

arp: 192.168.1.17 moved from xx:xx:xx:xx:xx:ad to xx:xx:xx:xx:xx:90 on igb0
arp: 192.168.1.1 moved from xx:xx:xx:xx:61:0a to xx:xx:xx:xx:xx:01 on igb0
arp: 192.168.1.1 moved from xx:xx:xx:xx:xx:01 to xx:xx:xx:xx:61:0a on igb0
arp: 192.168.1.18 moved from xx:xx:xx:xx:xx:14 to xx:xx:xx:xx:xx:fa on epair0b
arp: 192.168.1.18 moved from xx:xx:xx:xx:xx:14 to xx:xx:xx:xx:xx:fa on igb0

That :61:0a is different mac from epair0a.. But these may be related to other factors and devices outside freenas..

 

[Elliot Dierksen]

You didn't list your hardware configuration which would be helpful to know. That said, the message you describe is almost always an IP address conflict. It could also be some device on your network (like a firewall) doing a proxy ARP. What other devices do you have on your network, particularly things other than hosts (like switches, routers, firewalls, etc.)?

 

[MAC_Addy]

This looks like another device in the network has the same IP.

 

[Plato]

My hardware consists of Asus P10S-X, 32 GB RAM, Xeon E3-1260v5

Well, I have 1 router and 2 switches.... and a lot of devices (mobile, tablet, computer, console etc.. ) which poll their IPs from the router via DHCP. There are about 10 devices with static IPs which are above 192.168.1.200 ( not included in the DHCP range )..

I have one jail active with 192.168.1.231 IP, and FreeNAS again its' own IP as 192.168.1.250..

The weird thing is the messages are mostly about epair0b which doesn't show up on "ifconfig"

AFAIK there are no conflicting IPs in my network..

 

[Elliot Dierksen]

AFAIK there are no conflicting IPs in my network..

The messages you list are almost always the result of IP conflicts in my experience.

 

[Plato]

I understand but
1- I don't have any device which has the 192.168.1.250 or 192.168.1.231 ( jail ) that I'm sure of.
2- The real problem I think is about the interface.. As I explained above, there is actually no epair0b interface visible in ifconfig.. At startup it shows up in dmesg, but when I execute ifconfig there is only epair0a and epair1a interfaces..

 

[Elliot Dierksen]

I don't have any device which has the 192.168.1.250 or 192.168.1.231 ( jail ) that I'm sure of.

Something is responding on that IP address, so there is definitely something that thinks they have those IP's. You redacted the MAC addresses, so I can't make any guesses from that. If you want to have an idea what the mystery device(s) might be, you can look up the manufacturer based on the MAC.
https://www.wireshark.org/tools/oui-lookup.html
That may give you some idea where to go. You can also try to disable running any jail/iocage VM's and see if that changes things.

The real problem I think is about the interface.. As I explained above, there is actually no epair0b interface visible in ifconfig.. At startup it shows up in dmesg, but when I execute ifconfig there is only epair0a and epair1a interfaces..

The epair has to do with bridging an interface for a jail/iocage VM to a physical. That is why I would suggest stopping that to see if it helps. I only use FreeNAS for storage, so I don't have anything to suggest on the virtualization side.

 

[Plato]

I already explained mac addresses at the second mail.

The mac address ending with :68 is ASUS mainboard's ethernet adapter.. As I explained in my message earlier. At the boot-up FreeNas assigns this to igb0 interface ( which is first ethernet adapter )..

The other ending with :0a belongs to epair0a, which is virtual and assigned to jail...

But it shows epair0b which as far as I know not assigned to anything, or anywhere.. It shows up at bootup but then I cannot see it in ifconfig.. I think this is the real problem.

I run my server softwares on my jail so it's a bit hard to stop that right now... I could stop it at weekend to test it, though it would be hard to detect it because I'll most probably have to wait a while to see if it occurs again or not.

 

[vectronic]

Hi Plato,

Looks like I have exactly the same issue:

The mac address ending with :68 is ASUS mainboard's ethernet adapter.. As I explained in my message earlier. At the boot-up FreeNas assigns this to igb0 interface ( which is first ethernet adapter )..

The other ending with :0a belongs to epair0a, which is virtual and assigned to jail...

But it shows epair0b which as far as I know not assigned to anything, or anywhere.. It shows up at bootup but then I cannot see it in ifconfig..

Did you find out anything further on this?

 

[Plato]

No, not really.. But I'm using 11.2 right now, and as far as I can tell it stopped. I think something is fixed between 11.1 and 11.2..