Arp Moved from MAC to MAC ?

Status
Not open for further replies.

okaenrique

Dabbler
Joined
Jul 22, 2015
Messages
47
Hi!

i get this message

arp: 192.168.0.240 moved from 02:1a:6b:00:08:0a to d0:50:99:70:4c:1f on epair0b
arp: 192.168.0.240 moved from 02:d9:55:00:09:0a to d0:50:99:70:4c:1f on epair1b
arp: 192.168.0.240 moved from 02:1a:6b:00:08:0a to d0:50:99:70:4c:1f on epair0b
arp: 192.168.0.240 moved from 02:d9:55:00:09:0a to d0:50:99:70:4c:1f on epair1b

i don't know what this logg means ?


My Freenas
192.168.0.240 is my freenas

igb0:
ether d0:50:99:70:4c:1f


igb1:

ether d0:50:99:70:4c:1f


lagg0:
ether d0:50:99:70:4c:1f
inet 192.168.0.240

bridge0:
ether 02:df:50:af:62:00

epair1a:
ether 02:d9:55:00:09:0a

epair0a:
ether 02:1a:6b:00:08:0a

transmission jail
epair1b interface mac 02:b6:d9:00:0a:0b

owncloud jail
epair0b interface mac 02:b3:9e:00:0a:0b

Both have static ip address ,


br
OKA
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,175
It's characteristic of Apple devices taking over listening duties on the network. They might "transfer" their IP address to a second device so that the first can sleep. If the first device is contacted, the second will wake it up.
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
It drives me mad too :D You can stop the console messages entering the following in the CLI:

Code:
sysctl -w net.link.ether.inet.log_arp_movements=0
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
It drives me mad too :D You can stop the console messages entering the following in the CLI:

Code:
sysctl -w net.link.ether.inet.log_arp_movements=0
Thank you for this!
 

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
I also have this issue. I was listening to Security Now #573 (https://twit.tv/shows/security-now/episodes/573?autostart=false) and Steve Gibson was commenting on "Gratuitous ARP packets" on his two FreeBSD boxes due to the IPMI interface on the MoBo. He talks about it at 1:38:18 in the video feed. I was hoping someone that knows more about this than I might comment. I know my MoBo has an IPMI interface so when I have a chance I'll probably try to switch to my secondary NIC and see if this goes way.
 

DaveY

Contributor
Joined
Dec 1, 2014
Messages
141
It's characteristic of Apple devices taking over listening duties on the network. They might "transfer" their IP address to a second device so that the first can sleep. If the first device is contacted, the second will wake it up.

I'm missing something. What does it have to do with Apple? It's FreeNAS generating these messages
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,175
I'm missing something. What does it have to do with Apple? It's FreeNAS generating these messages
FreeNAS is telling you that an IP address, from another device, changed physical address. Such behavior is characteristic of Apple devices.
 

TAC

Contributor
Joined
Feb 16, 2014
Messages
152
FreeNAS is telling you that an IP address, from another device, changed physical address. Such behavior is characteristic of Apple devices.
So the IP addresses listed should be associated with an Apple device or a computer running iTunes?

My wife's computer has iTunes that she uses to sync podcasts to her iPod.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,175
So the IP addresses listed should be associated with an Apple device or a computer running iTunes?

My wife's computer has iTunes that she uses to sync podcasts to her iPod.
May be.
 
Joined
Aug 25, 2014
Messages
89
Apple devices on Open Directory have a tendency to share information just as a PC on Active Directory shares info. The info is just letting other devices know they exist on the network weather it is Active Directory or Open Directory. I recently had the same errors after I added a macOS Server (10.12.4) with Open Directory but not DHCP turned on. For me it was my Ethernet an WiFi addresses. I had a task where I needed to communicate with devices on WiFi and my server was on Ethernet so when I switched network ports I had the infamous freenasmini01.host.name kernel log messages:
> arp: 10.200.75.198 moved from 40:6c:8f:24:a8:ec to 80:49:71:12:92:cf on igb0
> arp: 10.200.75.198 moved from 80:49:71:12:92:cf to 40:6c:8f:24:a8:ec on igb0
> arp: 10.200.75.198 moved from 40:6c:8f:24:a8:ec to 80:49:71:12:92:cf on igb0
My clues were the static IP mentioned and the MAC address of my Ethernet NIC and my WiFi MAC address.
After reading everyone else's comments on this I believe it is just normal and is causing no harm.
 
Status
Not open for further replies.
Top