@ervau
Seems to work for you.
I've noticed a difference though. You have Repeater Bridge, I have Repeater only (different subnet).
Can you try to test the same situation with DIR-615 rev H in Repeater mode ? e.g. if your Remote AP (DIR-615 rev B - Ubicom cpu) is on subnet 192.168.1.1, then put your Repeater (DIR-615 rev H) on subnet 192.168.2.1
Well, I'm running it as Repeater too, (not bridge) and last night I did the other way around, changed the channel in the repeater (from 1 to 11) and waited to see if it would change back to the AP channel (1), and it did, the logs show it not being associated and associating, like ap_client should, and that was it, it didn't disassociate and re-associate repeatedly in a loop the way you described, KrypteX.
@Specimen
Do you have your script running, too ? If so, did you check whether it was ap_client or your script responsible for changing the channel ? _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Then I don't really know why it associates/disassociates for me... maybe my Remote AP (WNDR3800 on r27456) being Atheros kicks out the Repeater... I have to test some more with the new build 27506 flashed to both the Repeater and the Remote AP. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Then I don't really know why it associates/disassociates for me... maybe my Remote AP (WNDR3800 on r27456) being Atheros kicks out the Repeater... I have to test some more with the new build 27506 flashed to both the Repeater and the Remote AP.
If the problem is in ap_client, then it has to be in the 'assoc_loop' part of the code, because the 15 secs fit the "sleep 15" at the end of it.
Sorry guys; killed my repeater (remember Specimen: 100+ but no clue ); it's postioned on a cupboard, so I have to climb up to grap it down. It's always a mess.
Concerning the actual discussion I'm out of your depth, but I will have an eye on it to learn!
By the way: upgrade to 27506 via wifi works great.
Then I don't really know why it associates/disassociates for me... maybe my Remote AP (WNDR3800 on r27456) being Atheros kicks out the Repeater... I have to test some more with the new build 27506 flashed to both the Repeater and the Remote AP.
This is just hypothetical, but if I'm right it's related to the same multiple ap_client bug, at least, it makes sense that if and when you have multiple instances of the same program running and they have different settings they will be fighting each other, or even if they have the same settings it might occur that there is more than one AP with the same SSID and each ap_client is picking a different channel.
Yup, it's possible. I'll test again in a couple of days, I can't disrupt the network yet... _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Posted: Sun Oct 11, 2015 15:57 Post subject: NTFS support
Hi!
I'm new to dd-wrt, so I'm trying to pick things up. I've flashed the r27490 build for the ASUS RT-N13U B1. It's working great, solved some issues I was having with the standard firmware.
Now I'm trying to setup the USB storage, but from what i've read some specific steps are required to mount a NTFS hard drive. But there is no "Enable JFFS" option on the Administration page.
The router has 8MB flash and 64MB RAM, so I think I might be able to set it up.
Do I need an older firmware version? Or NTFS is just a deal breaker for this router?