oubeedoub

Hi @DeekB, I seemingly have/had the exact same issue. I recently got rid of my ISP's modem/router/switch/access point box and upgraded to a pfsense box. I'm very much a novice and not the help you're looking for, but I've seemed to fix it? Temporarily perhaps? Hopefully my experience can help someone diagnose the actual problem. Hopefully, it is the same problem!? For context my networking was setup as follows: Unraid eth0 and eth1 on bond network (eth1 had nothing physically plugged into it, I just never bothered turning off bonding); bridge network was turned on, which most of my docker containers participated on; proxy network for containers I wish to access outside my network (presumably no relevance to the problem); custom host network for pihole, which had it's own IP independent of the server (on the same network), I thought this might be the issue since I have 1 device, with two IP's associated with it? My networking skill isn't good enough to know if this would be and issue. I had my pfsense DHCP Server hand out this IP (pihole) as the DNS server, then pihole forwarded back to pfsense (to the DNS Resolver) which then forwarded to Google DNS servers; bridge network utilizes Google DNS Servers, as I had "Unraid can talk to host networks" turned off, as I understand this might cause issues, nor do I really need my server to run through pihole; physical network is: interwebs -> pfsense box -> network switch (smart one, but utilized as a dumb switch for the time being) -> server plugged into a switch, along with my ip cameras, access point, and a smattering of clients; and, only one LAN network in play, no VLAN's. I was having the same symptoms as yourself; In addition to what you've noted, I noted the following with my setup: When I ping my router from the server, I would have 90%-ish packet loss, so it was kind of connecting? Similarly, traceroute -I 8.8.8.8 would sometimes hit the router and out the door, other times returned nothing; My pfsense log was throwing "pfsense kernel: arp: <Server IP> moved from <MAC Address 1> to <MAC Address 2> on igb1", this would constantly switch back and forth between the two MAC's. pfSense has documentation about this here. The MAC Address 1 I recognized as that reported by ifconfig for eth0 and br0 (makes good sense, I think). MAC Address 2, no idea what this was, much confuse. Actions I took to correct or accidentally correct the issue: I had a custom docker network setup, I noticed this while faffing about trying to solve the problem. I was like "what's this garbage" and deleted it. My pihole proceeded to get booted from it's host network and onto the bridge network. "Ah, that's why I had that..." Well... okay, this should still work anyways. I changed the DHCP Server so it handed out my servers ip. Then cleared the DHCP Lease table. All of my client's seemed happy with the new arrangement. However, I was still getting the log message about the flopping back and forth of this MAC Address. Who is this imposter MAC? My server has no internet still. I turned off the bond network on Unraid. Next, I assigned a static ARP Table entry for my server. So, static IP and Static MAC (bizarre concept to me). So this imposter MAC could no longer hijack what I interpreted as the correct MAC Address. Flushed my DHCP leases again, and my ARP table (aside from the static assignment). Rebooted my server. Voila! Everything is working now. I had rebooted before doing items 1, 2 and 3. So, I'm certain I didn't just need a reboot. I'm guessing item 3 was the game changer. Today in my pfsense logs I noticed that the imposter MAC got thrown onto another IP after attempting to alter a permanent ARP entry multiple times (haha, take that imposter MAC). I cannot track down if it is some other device on my network that was previously assigned my servers IP and refused to let go, or something coming from within Unraid itself. Log below (imposter MAC is in red): May 10 22:46:54kernelarp: 192.168.2.112 moved from 34:2e:b6:f9:8f:94 to 74:d6:37:1a:eb:3b on igb1 May 10 22:46:50kernelarp: 192.168.2.109 moved from 64:16:66:90:31:17 to 60:a4:b7:b7:60:c2 on igb1 May 10 22:46:46kernelarp: 192.168.2.107 moved from 80:f3:ef:c0:e1:9b to 40:3f:8c:c6:02:f4 on igb1 May 10 22:46:42kernelarp: 192.168.2.106 moved from 74:d6:37:1a:eb:3b to 68:d7:9a:0b:5d:eb on igb1 May 10 22:46:07kernelarp: 68:d7:9a:0b:5d:eb attempts to modify permanent entry for <Server IP> on igb1 May 10 22:46:00kernelarp: 68:d7:9a:0b:5d:eb attempts to modify permanent entry for <Server IP> on igb1 ... Hopefully, this helps in some way or another. Someone let me know if they don't think I fixed a single thing and it's still broken. I feel as if a static ARP is a band-aid? Let me know if you need more information or context or if we're even having the same problem, I'm far too smooth brain to know.