- Closed
Been scratching my head all afternoon on this one, but I think I finally narrowed it down. What I found is that when you have "Host access to custom networks" enabled in the Docker options, it's fudging the MAC address of the Unraid server as a whole.
I found this out because I was attempting to debug the "macvlan" Call Trace issue when we have custom IP's assigned to Docker Containers. To me, having custom IP's (Custom br0) is a requirement so I can implement firewall rules on a per docker container basis. As well, just taking the approach of creating another VLAN on my network is not a suitable workaround because that just adds additional complexity when trying to route to those containers from my primary network. Anyways.....
I thought what the hell, let me swap in a different network card to see if it makes a difference (Intel X550 vs X540 vs 82599ES etc..) since the assumption is some people have this issue and others don't, perhaps it's a hardware or driver issue?
So, I installed my different network card, and proceeded to do the usual, set static IP in unraid, then in pfsense make sure I tag the proper MAC address (the new one) to make sure I also assign the same static IP. This is where it started getting weird....
The actual MAC of my adapter begins with D0 and ends with 9C:
So when I went into pfsense, I was ready to tag D0..9C, but didn't see it. So I checked the ARP table, and low and behold I saw a MAC of 36...52:
If I disable "Host access to custom networks", then the real MAC comes back:
At least for me, this is an issue as this means that when enabling this option, any static IP assignment I have in my router would be ignored since the MAC is randomized each time with macvlan. As well, I am not sure of the additional macvlan ramifications of this when the MAC for an IP is changing.
Perhaps this is working as designed, but I wanted to bring this to light as it may be related to the calltrace for macvlan, and for sure surely breaks my static IP rule that I define in my router.
And yes, I know of course that I could set a static IP in unraid (which I do). But I also like to make sure that IP is static in my router as well, as I have had occasions where I needed to nuke the network.cfg file, and still want to come up on the same IP.
@limetech I am tagging as "other" for now since I can't make out if this is Urgent, Annoyance, Other or by design.