Help with testing the AP+Client Bug

[decodecoding]

Hi to all,

Does this bug that is being discussed here concern the pure Client mode? I mean with no AP defined and pluggin clients to the LAN port.
I'm using a Fonera 2100 with gargoyle 1.0.10

I have a Fonera set up as a client of another WiFi AP and from time to time, connection seems to stall. Sometimes it just comes back but other times I have to reboot in order to get it working again.

Thanks in advance.

[DoesItMatter]

1.0.14 - uptime of 14+ hours - seems to be good solid connection.

No issues connecting to Fonera 2201+ and good memory usage.

Nice build!

[ispyisail]

Uptime:1 days, 2 hours, 26 minutes

[DoesItMatter]

Same here!

1 day 2 hours 35 minutes and counting!

AP+Client looks like its working great.

I also have mixed encryption, I have the wireless DHCP client
using WEP 128bit encryption, and then I have the wireless AP mode
using WPA2-PSK encryption - no problems using mixed encryption.

------------

Edit: Ok, it died somewhere after 27 hours - I went to sleep, got up
and checked the connection, and no wireless connect possible.
I tried to go wired via LAN port, could not get to 192.168.1.1

Had to power-cycle my Fonera 2201+ in order for Gargoyle to
work again, but when it rebooted AP+Client mode was back up.

So here, it's at LEAST working for 27+ hours. Will try another run!

[decodecoding]

Althoug I'm interested in the pure Client mode, I'll be testing this AP+Client feature for the following days and see hoy stable it is.
I've set it up this morning so I'll report how it behaves. By the way, this AP+CLient feature is fantastic and so easy to set up.

Congrats to the developer/s.

[DoesItMatter]

AP+Client mode - 1.0.14 - uptime 1 day 21 hours 45 minutes

and counting

memory 11.8 out of 13.4 mb used

mix of WEP and WPA2-PSK used for the AP+Client mode

had streaming audio - shoutcast + some torrents running constantly

I THINK prior reboots or freezes must have been device either
running out of memory or it overloaded.

------

Edit: uptime 2 days 13 hours 45 minutes and still going.

-------

Another edit - 2 Days 16 hours - AP+Client mode dies out.
The wireless access to the Fonera is completely unavailable.
It gets a good solid signal, but no IP address assigned.

I can connect to the router via LAN port fine, no issues.
Just cannot connect anymore via wireless mode.

AP+Client mode is working MUCH better than before, but it does
look like its dying out after a couple of days on the Fonera 2201+

Anyone else have longer running than 2 days 16 hours on
some other Atheros devices?

[Eric]

That's worrying. I have a test device set up now, and we'll see how long it stays up (i.e., we'll see if it dies after 2-3 days).

[DoesItMatter]

The way I do the testing for the AP+Client mode is that I have
the connection constantly active.

I have streaming audio from shoutcast.com running 24/7 on the
AP+Client wireless mode and besides that I had a couple of
Linux torrents running as well.

Nothing that would overload it, just some constant data going
24/7 on the router, so that it would never remain just idle.

[Eric]

Right now, my system has been up for 4 days in AP+client mode, and it seems fine.

Maybe test again? Any chance, the problem could be with the AP you're using? If the AP the device is connected to goes down, all wireless on the AP+Client mode router will die.

[DoesItMatter]

For anyone trying out the AP+Client mode.

What are your security settings you are using to test?

For the AP+Client:

Client part connects to a wireless network with WEP-128 bit
I need WEP-128 bit for my Nintendo Wii and Nintendo DS

The AP part - if I try to also set it as WEP-128 bit,
when I try to connect from the client computer, it keeps saying
an invalid key has been detected, try again.

I can only use WPA or WPA2 security on the AP part, which doesn't
bother me, I can use any of the settings.

Anyone able to successfully use WEP 128 bit and WEP 128 bit?
I'm not sure if this is a bug or if this is just the way it has to be?