On 2010-01-08 6:24 PM, Ferenc Wagner wrote: > Stefan Bethke <s...@lassitu.de> writes: > >> Am 08.01.2010 um 16:57 schrieb Ferenc Wagner: >> >>> However, I failed to use it in client mode: it associates with the >>> AP, but doesn't receive IP packets (I simply bridge it to the LAN, >>> and try DHCP from the laptop). >> >> See the numerous forum posts on why client bridging does not work. >> You'll need to run udhcp on the router itself, or configure a fixed >> ip. > > Many thanks for the quick pointer! I guess you're referring to > https://dev.openwrt.org/ticket/5749, right? I can accept that there are > technical reasons which make client bridging impossible, but don't fully > understand them from the ticket. And I'm curious, so I'd be grateful > for some further explanation or pointers. Why is the source MAC address > missing from "the" packet (travelling in which direction)? The source MAC is missing in packets from STA->AP The destination MAC is missing in packets from AP->STA These MACs are missing, because they are unnecessary when not using bridging, so they left them out in the standard. This also serves as MAC spoofing protection, as you cannot fake your MAC address without associating with a different ID.
- Felix _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
