Raspberry Pi as WiFi Bridge on Same Subnet

I currently have my Raspberry Pi 4B setup as a bridge to provide wifi access to a separate ethernet device that can't do wifi. I used Option 1 from the guide here: https://willhaley.com/blog/raspberry-pi-wifi-ethernet-bridge/ which is based on an earlier question that was answered here: https://raspberrypi.stackexchange.com/questions/88954/workaround-for-a-wifi-bridge-on-a-raspberry-pi-with-proxy-arp/88955#88955

It works! The client device connects to the network via the bridge just fine and gets its own appropriate IP address from my network's main DHCP server that's in the correct subnet. However, in the DHCP lease, the client device has the same MAC address as the Raspberry Pi that's acting as a bridge. So in my DHCP's GUI, the list of clients only displays the Pi's hostname (not the bridged client's), and its IP address vascillates between the Pi's and the client's every couple minutes.

In real life, I can access either device via their respective IP addresses or hostnames without any issues. The problem is mainly cosmetic in the DHCP's displayed list. However it also makes it difficult to figure out the client's IP address, especially if it changes because I'm plugging in something different. Is there a way to tweak the changes I've made so that the device connecting via the bridge has its own MAC address in the DHCP lease rather than the bridge's MAC address?

https://stackoverflow.com/questions/65963950/raspberry-pi-as-wifi-bridge-on-same-subnet January 30, 2021 at 10:05AM