Raspberry Pi WiFi to ethernet bridge

Re:Raspberry Pi WiFi to ethernet bridge by mjg59 on Friday June 11, 2021 @02:52AM (#27470123)

On wired ethernet, a packet contains the MAC address of the destination host. Switches across the network keep track of which port a given MAC address is associated with and forward it appropriately. Wifi doesn't have the same concept - the only destination MAC address in a standard 802.11 packet is that of the destination Wifi station. So, if you have a device on Wifi with several wired devices behind it, and you want to send a packet to one of those wired devices, you can't stick the wired device's MAC address in there - it needs to be the address of the one with Wifi. So how does that Wifi node know which wired device to forward the packet to?

(This is avoided with WDS, but that requires the AP to cooperate)

[ Parent | on HN ]

Re:Raspberry Pi WiFi to ethernet bridge by serendipitous on Friday June 11, 2021 @04:52AM (#27470839)

The 802.11 header has 4 MAC addresses: Source Address (SA), Destination Address (DA), Transmitter Address (TA), Receiver Address (RA). The TA and RA are those of the Wifi station and SA and DA are the Ethernet addresses. This allows bridging Ethernet and Wifi interfaces and it is how many (most?) Linux-based Wifi routers work.

[ Parent | on HN ]

Re:Raspberry Pi WiFi to ethernet bridge by mjg59 on Friday June 11, 2021 @01:17PM (#27476007)

Yes, if you're using WDS, otherwise you only have three addresses used. Since you need the transmitting device to populate the DA, you can't just turn on bridging on a client and have everything work - you need both ends of the link to be involved.

[ Parent | on HN ]

Re:Raspberry Pi WiFi to ethernet bridge by serendipitous on Saturday June 12, 2021 @04:32AM (#27482749)

Yes, for a wifi client (like in the article) you're right. manuel_w was talking about bridging on the AP and for that you do just enable bridging and it works fine.

[ Parent | on HN ]