On Mon, 2009-06-29 at 10:39 -0500, Jon Loeliger wrote: > I think I need to do this strictly from a client/station perspective. > The only AP in this picture would be the "upstream" AP to which my > client is associated. We shouldn't be changing any code running on > those APs at all. Right. Still though, an AP implementing it wouldn't seem to be compliant, so I would have guessed that APs don't implement this. > Which leads to me trying to figure out how the client is able to > know what the correct "MAC level NAT address" needs to be to > when it converts the 802.11 header to the 802.3 header. Doesn't > the upstream AP have to have already sent you 4-address frames > for this to work? Or will it respond with a 4-address frame if > it is sent a 4-address frame from the station? No idea. Nothing of this is specified in 802.11 or anywhere else, so it's all implementation dependent hacks. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
