#RASPBERRY PI SAMBA SUBNET MAC#

Also if you'll read it carefully, you'll definitely encounter some strange term, a proxy arp. But you can see it enables IP routing explicitely instead: _forward=1. If you read a script in the Option 1, you wouldn't find any Linux bridge related commands there. Note that I don't have access to raw files or logs for the DHCP server, it's not an open system.

#RASPBERRY PI SAMBA SUBNET MAC#

Is there a way to tweak the changes I've made so that the device connecting via the bridge has its own item in the DHCP list rather than the bridge's? Is this a MAC address translation issue? The item in the DHCP list has the Pi's wifi MAC address. 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. The problem is mainly cosmetic in the DHCP's displayed list. In real life, I can access either device via their respective IP addresses or hostnames without any issues. 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. However, in the DHCP list, the client device is sharing the same spot on the list as the Raspberry Pi that's acting as the bridge. 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. I used Option 1 from the guide here: which is based on an earlier question that was answered here:

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.

Raspberry pi samba subnet