On 02/19/2017 12:51 PM, Piotr Dymacz wrote: > Hello, > > 2017-02-19 11:41 GMT+01:00 Daniel Golle <dan...@makrotopia.org>: > > [...] > >>> Maybe a similar one that does what the "force enable wifi" script did >>> would do the trick? >> >> Well, it's not as simple as that. We need to generate a config for >> hostapd which matches the wifi hardware in terms of capabilities and >> band and launch it and bring up the interface (configure IP address and >> stuff) once hostapd comes up... possible, but quite a lot of work... > > If we assume that the problem is only inside wrong configuration > applied to the device, reverting it back to the defaults (I assume > here that default config for devices without Ethernet interface means > also that the Wi-Fi is enabled by default) should be enough to bring > back device to life. >
After Mathias's commit (as noted by other mails above) the devices we are talking about have wifi disabled by default but you can enable it with the wps button. https://github.com/lede-project/source/commit/bcfbeae79f799cf1087d692e4869589eb20d2080 Imho makes no sense as in most cases you will have to configure them anyway to be of any use (you can't just place them in a network with default config as they lack a ethernet port), so this "wifi off by default" and "remapping wps button to rfkill" imho is only an annoyance and removal of a potentially useful button that could be used for other things (enabling/disabling something else with scripts after user setup). -Alberto _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
