SOLVED arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b

[Xelas]

I'm getting millions of these bogus arp messages. 192.168.1.1 belongs to my router, which I changed a few days ago. The MAC address is correct for the new router.

Code:

Jan 11 02:09:32 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:09:32 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:09:32 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:09:32 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:09:32 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:09:32 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:09:47 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:09:47 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:09:47 NAS kernel: arp: attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:09:47 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:09:47 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:09:47 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:09:52 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:09:52 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:09:52 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:09:52 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:09:52 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:09:52 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:10:46 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:10:46 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:10:46 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:10:46 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:10:46 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:10:46 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b
Jan 11 02:11:09 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:11:09 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair2b
Jan 11 02:11:09 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:11:09 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair1b
Jan 11 02:11:09 NAS kernel: arp: xx:xx:xx:f0:7a:2f attempts to modify permanent entry for 192.168.1.1 on epair0b

The problem is that I'm not seeing a permanent entry in the arp table for that ip:

Code:

[root@NAS] ~# arp -a
? (192.168.1.41) at xx:xx:xx:xx:07:0b on igb0 permanent [ethernet]
? (192.168.1.40) at xx:x:xx:xx:06:0b on igb0 permanent [ethernet]
? (192.168.1.42) at xx:xx:xx:xx:0a:0b on igb0 permanent [ethernet]
router.kurort (192.168.1.1) at xx:xx:xx:f0:7a:2f on igb0 expires in 1200 seconds [ethernet]
? (192.168.1.3) at xx:xx:xx:cd:d7:08 on igb0 expires in 1132 seconds [ethernet]
MamaNova.kurort (192.168.1.187) at xx:xx:xx:fe:40:65 on igb0 expires in 1090 seconds [ethernet]
T420.kurort (192.168.1.125) at xx:xx:xx:xx:9d:a1 on igb0 expires in 1095 seconds [ethernet]
? (192.168.1.191) at xx:xx:xx:5a:1c:f8 on igb0 expires in 1144 seconds [ethernet]
WindowsServer.kurort (192.168.1.31) at xx:xx:xx:e4:35:00 on igb0 expires in 1199 seconds [ethernet]
NAS.kurort (192.168.1.30) at xx:xx:xx:xx:fa:f5 on igb0 permanent [ethernet]
ESXi.kurort (192.168.1.20) at xx:xx:xx:xx:fa:f4 on igb0 expires in 320 seconds [ethernet]
? (192.168.2.1) at xx:xx:xx:xx:d8:f3 on vmx3f0 permanent [ethernet]
[root@NAS] ~#

Any ideas?

 

[Xelas]

The issue ended up being one of the jails. I subsequently discovered that a jail had lost network access for some reason (but the "main" freenas host was fine). I rebooted that jail, and the jail recovered network access, and the bogus arp messages stopped.