On Raspbian, you don't need to install the 8192cu driver manually, as it comes with the distribution
To avoid disconnection issues, you need however to disable power management. This needs to be done in two places. First, this is what I have in /etc/modprobe.d/8192cu.conf:
options 8192cu rtw_power_mgnt=0 rtw_enusbss=0
This alone did not prevent the issue. I also had to add this entry to /etc/network/interfaces:
auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf wireless-power off iface default inet dhcp
A friend recently brought us a Linksys WRT54GL which had been laying around for a while and whose password was not available anymore.
None of the "easy" password recovery methods seemed to work (like holding the reset button, power-cycling etc.) - possibly because the corresponding options had been previously disabled.
However, it didn't work until all these conditions were met:
- the laptop with the firmware image and the tftp client had to be connected to the WRT through an external switch
- the switch had to be unplugged from the LAN
- I had to lauch a "ping -f 192.168.1.1" in a different terminal before powering on the WRT in order for the tftp transfer to start
- before and after the flashing I followed the 30/30/30 procedure (not sure if that one is mandatory but it is recommended)
To make sure the hardware was working I installed the latest firmware from the Linksys website (WRT54GL_v4.30.11_012_ETSI_EN_code.bin), but now I'll likely reflash it with OpenWRT - this time from the web interface :o)
It seems that after having been up for a couple of days, the WAG200G starts having issues routing UDP packets properly. This particularly affects VoIP traffic (here IAX2 on port 4569). The symptoms are that "regular surfing" works flawlessly, but the registration with the asterisk server fails. tcpdump shows no traffic on the server side. Restarting the WAG200G immediately solves the problem.
Here is how I restarted the router from the command line: