mix wrote:asayler: Immediately after your wireless drops out (or whatever you are experiencing), connect to the router with ssh with a wired client. What is the output of the "logread" command? Something in it will most likely correspond with the timing of the outage occurring.
I have very similar problems on a LinkSys/Cisco WRT160NL.
I am using it as a client bridge on 2.4 Ghz, 20 Mhz bandwith with WPA2+PSK. After a reboot it connects to the Access Point, but after a while it looses wireless connectivity.
When this happens I see no messages from 'logread' or from 'dmesg' indicating any errors.
When I use 'ssh' to login from a wired client, using 'wl wlan0 station dump', I can see the rx packets and tx packets incrementing, so something gets send and received on the wireless interface, but nothing gets routed.
After some time, the wireless connection might come back on it own.
When connectivity is lost, the gargoyle client bridge stays associated with the Access Point. If I close the connection from the Access Point, gargoyle will immediately reassociate and connectivity is restored.
This happens on version 1.4.0, 1.4.1 and 1.4.2.
It makes gargoyle very unstable and unusable at the moment.
Does anyone know how to get gargoyle running stable as a client bridge without repeater function?