[support] RAs leaking into adjacent wifi networks

[Arnaud Ebalard]

Hi,

"Georgopoulos, Panagiotis" <panos at comp.lancs.ac.uk> writes:

>                 In my nepl running testbed I have numerous madwifi APs and
> clients to try and simulate real life scenarios of MR roaming from one
> network to another doing bindings with their respective HAs. I recently have
> started seeing situations where a client (ie. a sta interface in a MR)
> although being connected to e.g. AP1, receive inadvertently RA from
> AP2.
>
> Unfortunately this makes the interface configure an additional address from
> the network prefix of AP2 and brake the bindings which from this point on
> cannot achieve. 
>
> The client interfaces are configured using iwconfig athx essid "ssid-name"
> (NOT any) so it is very weird that they hear RAs from adjacent networks (I
> can confirm in wireshark that they hear RAs from a network that they are not
> connected to). Let me also note here, that wireshark logs like 50 RAs from
> the network that they are connected to and then only one from an adjacent
> network that brake things. 
>
> Unfortunately this problem is happening very frequently lately and I was
> wondering whether there is anyone who experienced this in the past and
> whether there is a solution to it? Is there any obvious configuration issue
> or something that I might have overlooked causing this problem?

Basically, the card should not accept the frame relayed by AP2 because
it is not associated with it (even if channel are the same or close).

Are AP1 and AP2 on close channels (like 6 and 7) and have you by (lack
of) luck put the interface of the MR in promiscuous mode?

Just a guess though. You should definitely ask on madwifi ml. If you
happen to find the root of the issue, I'll be interested.

Cheers,

a+