#20475: No WLAN available if router cant connect to WWAN
-------------------------------------------------+-------------------------
 Reporter:  frietpan                             |      Owner:  developers
     Type:  defect                               |     Status:  new
 Priority:  high                                 |  Milestone:
Component:  base system                          |    Version:  Trunk
 Keywords:  WLAN, wifi, SSID, Travel, Lockout,   |
  Connect                                        |
-------------------------------------------------+-------------------------
 When i configure OpenWRT With a WWAN SSID that connects to another router
 to connect to the web and a WLAN SSID (or multiple WLAN SSID's)  All works
 fine.

 But, when the WWAN SSID is not available WWAN does not connect AND as a
 result WLAN does not seem to come alive.
 In case of the ever more populair travel router this is a massive
 headache.

 In case you travel with a travel router you need to connect to different
 SSID's when you are at different locations. So this is going to lock
 people out. More so because the idea of wireless travel routers is
 traveling without wires...
 The only way to access the router is by using a CAT cable or over UART.
 But that's not in everyones backpack.

 I have tested this on:
 - NEXX WT3020 (Mediatek 7620) with CCrc2 and CCrc3
 - GL.iNet 6416 and D-link DIR-505 (both Atheros 3133) With BB and CCrc3

 When WLAN is not connected the Atheros devices behave a little different
 then the Mediatek
 When adding WLAN's to the device they seem to be activated for a little
 wile however the wrong SSID becomes active. (not the one I last
 configured)

 dmesg and log: I will add ASAP

 So what I at least expect:
 Since WLAN's are configured I expext that WLAN's will become available
 even when the router isn't able to connect to a WWAN. So that a traveler
 can still access his travel router. And is not forced to travel with CAT
 cable. (and people with tablet or Android they don't even have a RJ45
 connector so it's even worse..)

 Another thing that gets messed up is NoDogSplash. I haven't been able to
 fully configure NoDogSplash so I can't say much more about this. It's
 still on my todo list.
 When configured on WAN NoDogSplash worked, when I switched to WWAN
 NoDogSplash nolonger worked. Also not when I went back to WAN. There seems
 to be a connection to this. But that's all I can say at this point.

 Please read this forum topic:
 https://forum.openwrt.org/viewtopic.php?pid=291182#p291182
 There are a few old bug that seem to be related. But those bugs fail to
 describe the bigger issue. In my poinion this bug manifest itself in
 differnt ways depending on different configuration goals. So if this can
 be revisited I think it could fix several bugs, annouances and config
 weirdnesses at the same time.

 I have set the priority to high because of the nature of the travel
 router. In this case OpenWRT is not very user friendly.

 I really hope that this can be fixed.

 This is not a duplicate bug, although a few bugs seem closely connected
 https://forum.openwrt.org/viewtopic.php?pid=290840#p290840

 Thank you!

--
Ticket URL: <https://dev.openwrt.org/ticket/20475>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to