Help with testing the AP+Client Bug

[DoesItMatter]

Reloaded madwifi 14000 and its been about 8 hours - still running.

Will leave this build running overnight and give it a full 24 hour test.

Anyone else besides myself and IspyIsail can load up 14200 or 14400 and run some testing?

14400 started to look flaky @ 8hr mark, but I'll have to try again to be sure.

[ispyisail]

I have also reloaded 14000 and my fault is repeatable

If I reboot my router AP+Client is rock solid.

From memory version 13xxx did not need a reboot to function correctly?

Eric would you consider this a pass?

[Eric]

For now, let's consider it a provisional pass. However, since you are having a fault on boot, I'm not 100% sure we can ignore this, so I'm not going to remove the ones before 14000 from the list above just yet -- we may need to come back to them.

Not to bias you, but when I was testing these builds I saw something similar to what you describe with 14400 -- that one died on me when I first installed it but when I tried again (rebooted) it was ok. That made me think the problem was probably in a higher revision, especially since I didn't see it on builds right after it, but since you're seeing something similar I'm not so sure. Let's see what you find for the higher revisions. (As I said, 15465 was the first one to fail repeatably for me... but you said that didn't work, so I need to know what you see on these intermediate builds).

[alternative]

Version 14000 works almost fine for me on fonera2100,but totaly hangs when trying to scan for ssid to join.
updt:after reboot ,sometimes work good sometimes always disconnecting ,loosing wireless etc.

[DoesItMatter]

OK, I was having some flakiness on the 14400 build at 8+ hours, but 14000 was working fine.

I loaded up build 15408 and its been up and running 18+ hours now.

Running solid, doesn't seem to be any issues listed above like scanning for client to connect to, or needing to reboot in order to work.

Will leave this one loaded overnight and check it again in the AM.

[alternative]

But not for my fon2100,stil bug with rescan for another ssid in 15408,router stil work but wifi goes down,need ifup wifi each time through ssh conected via eth.

[DoesItMatter]

Hmm...

That seems it could be an even stranger issue.

I'm doing my testing on a Fonera 2201+, the one with the extra LAN port, and all my setup/config is done through the LAN port, and then I disable LAN port and connect via wireless to do the testing.

Alternative: When you're doing your testing and flashing

Are you doing this first?

fis init -f

to completely wipe the nvram?

Also, are you entering all config info from scratch?
I.E. do not load a config file, manually type in all the info?

I always wipe the nvram and manually type in all settings fresh.

[alternative]

I thinked here is no nvram in kamikaze.
Flashing without redboot,just through ssh with mtd.
Then doing all changes in web,but when wireless goes down there no posibillity to up it in web,so i do it via ssh.
but its not big problem,now my fonera is ~7 hrs uptime in AP+Client mode and works ~fine.

[DoesItMatter]

Have you ever tried flashing via Fon Flash?

You should try one of those flashes, because it wipes out all settings
and fresh installs the firmware.

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

Build 15408 - almost @ 36 hours uptime and still going.

[alternative]

Almost flashing atheros routers through serial conection with red boot,most used fw is legend with x-wrt webif,based on openwrt.i think fis init -f needed usualy when flashing from dd-wrt to another dd-wrt but not openwrt.
and fon flashers only for win i think or i'm wrong?
Update:After 8 hours make some changes ,like 4 MAC's to filter in,and quatas changing, router reboots and now always drop conections.now can conect via lan and wan ,but strange ,no internet on laptop.I dot't think it flashing issue because flashed about ~40 fons with different fw and never was same problems like 8 hrs work then not work and again.
OK.next try with next version with fis init -f .