On Sat, May 24, 2014 4:06 pm, Patrick Shirkey wrote:
> Hi,
>
> For reference sake in case anyone else comes across this thread I have
> upgraded to  the latest:
>
> BARRIER BREAKER (Bleeding Edge, r40820) May 22 2014
>
> I am seeing better behaviour now.
>
> first -> wlan0
> second -> wlan0-1
> third -> wlan0-2
>
> I also have to run the following commands a few times after boot.
>
> /etc/init.d/dnsmasq restart
> /etc/init.d/network restart
>
> Trying to connect more than one device at the same time causes things to
> fall over.
>
> However, I have now been able to connect 4 mobile devices with different
> operating systems to different AP's. They have been connected for over 12
> hours.
>
> I would like to understand what is going on at the lower level. It seems
> like there is an initialisation issue but I am not sure where to look to
> attempt to fully debug the issue.
>

We made a few tweaks to the firewall rules and we now see the following
behaviour with two devices:

wlan0 = first
wlan0-1 = second
wlan0-2 = third

device 1 -> second = no
device 1 -> third = no
device 2 -> second = no
device 2 -> third = no

device 2 -> first = yes
device 1 -> second = yes


- Basically, we cannot connect to the second/third AP until we have
established a connection to the first AP on at least one client device.

- We can also go from the first AP to the second/third AP on the same
client device if we do it quick enough. i.e. within 30 secs.

Then we can connect to the second/third AP on another client device.
However if we disconnect the first client device we cannot connect a third
client device to the second/third AP even though the second client device
is already connected to the second/third AP.

- We can replicate this behaviour every time. ex. switching the device
order, directly after a reboot and also if we run the following commands:

/etc/init.d/dnsmasq restart
/etc/init.d/network restart

- This seems like a logic issue in dhcp codebase where a connection to the
first AP (wlan0) is required for things to "just work" (tm).



--
Patrick Shirkey
Boost Hardware Ltd
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to