Comment on [deleted]
just_another_person@lemmy.world 2 months ago
Because the MAC address isn’t a part of the tcp/ip exchange. You’re specifically addressing TCP/IP only.
If you’re trying to block something by MAC address, you’re doing it wrong.
Comment on [deleted]
just_another_person@lemmy.world 2 months ago
Because the MAC address isn’t a part of the tcp/ip exchange. You’re specifically addressing TCP/IP only.
If you’re trying to block something by MAC address, you’re doing it wrong.
modus@lemmy.world 2 months ago
I see. Thanks.
What other way is there if the the IP is dynamic. I thought to create a whitelist for devices I had to add the client’s MAC to the custom group. It seems to work fine so far. I was just concerned that it wouldn’t continue to work if the iPhone changed its MAC.
friend_of_satan@lemmy.world 2 months ago
That person is missing the point that a randomized MAC will often get a different DHCP lease, and the MAC address is used in that, so the IP address will change.
On a trusted Wi-Fi network, disable MAC randomization on your clients, and if possible reserve an IP address for their non-random MAC address. Some devices have a deterministic random per WiFi network, which could also work. In iOS this is WiFi network -> private WiFi address “fixed”. “Rotating” would cause your hole problems.
modus@lemmy.world 2 months ago
OK thanks. This makes sense. I guess if I’m going to go through the trouble of whitelisting the MAC, I can go and disable randomization on the device and assign it a static IP.