wifibox cannot connect using WiFi: 'wlan0' not found

Doodle3D / doodle3d-client

The Doodle3D web interface that people can access on computers or tablets to draw doodles and control the Doodle3D WiFi box.

www.doodle3d.com

GNU General Public License v2.0

3 stars 8 forks source link

wifibox cannot connect using WiFi: 'wlan0' not found #277

Open casperlamboo opened 9 years ago

casperlamboo commented 9 years ago

Suddenly the WiFi connection does not work anymore. Both creating an AccessPoint and joining as a client fail. Connection with ethernet cable works fine.

details:

firmware version: 10.5
When creating an accesspoint the wifibox fails to retrieve the MAC address so it tries to create a network with the name Doodle3D-000000
looking in the /tmp/wifibox.log shows wireless device 'wlan0' not found, trying fallback 'radio0' multiple times
the folder /sys/class/net contains: br-lan eth0 lo. This shows that wlan0 is missing
the contents of /etc/config looks normal

casperlamboo commented 9 years ago

the folder /sys/devices/platform/ar933x_wmac exists but the subfolder net is missing.

casperlamboo commented 9 years ago

reflashing the wifibox (using sysupgrade -v -n /tmp/doodle3d-wifibox-0.10.5-tl-mr3020-sysupgrade.bin) solved the issue. the cause of the problem is still unknown.

arneboon commented 9 years ago

was it renamed?

check

sudo gedit /etc/udev/rules.d/70-persistent-net.rules

check the NAME tag and rename back to wlan0 if it is changed?

arneboon commented 9 years ago

cat /etc/udev/rules.d/70-persistent-net.rules

arneboon commented 9 years ago

at least that works on debian

casperlamboo commented 9 years ago

/etc/udev/ does not exist on OpenWrt.

casperlamboo commented 9 years ago

The syslog in wifibox.tgz shows the following on the broken device:

Thu Jan  1 00:00:17 1970 daemon.info sysinit: 'radio0' is disabled
Thu Jan  1 00:00:17 1970 daemon.info sysinit: 'radio0' is disabled
Thu Jan  1 00:00:17 1970 daemon.info sysinit: 'radio0' is disabled

olijf commented 8 years ago

On recent firmwares it looks like the network name Doodle3D-000000 comes up more often if you issue a reboot from the command line. Maybe this has something in common with this issue?