aubade: The wiki is up-to-date. Restructured wiki yesterday so all optional config is in the "Optimizations" section. Hopefully the main/core instructions are relatively brief and straight forward.
Repeater mode is in beta. It seems to basically work for everyone who reported results here. Connection stability, and usability of security, varies per user. Connections are stable for some (like louis)... others (like me and mikmouse) report intermittent client drops. We have workarounds that seem to mediate the latter. Any instabilities could be due to hw/protocol/network/rf issues in the test networks, not necessarily the repeater mode itself.
In any case, if you try it out, we would be grateful if you report your insights or results here for others.
hey wofo: to run obfsh, setup a free shell account on m-net.arbornet.org. Change the first line of obfsh to "#! /bin/bash" to run on their servers... I tried it and it works.
obfsh requires some shell/script knowledge to get going (so its not for everyone). Type "obfsh -h" for options. Also - it will likely make your resultant (obfuscated) scripts larger... so in a memory-limited environment, it might be best to obfuscate small scripts.
Another way to obfuscate your code would be to compile it. That would make it small and fast, too. If you have a development environment setup, that might be best.
Regarding splashd stopping... one approach to restart it would be via the startup command file, wrapped in a do/sleep loop, as documented in the wiki (the approach used to start and restart autoap). I've had success with that approach.
Thanks Marc.... I do have a few linux boxes here to compile the script with, but that would stop ther dev process for the moment, so until the script is nailed all the way down, I don't see much sense in compiling it yet, but very soon, when we get it perfected, then that would be the ideal thing to do, and I will...
The script is so small that obfuscating it to some degree should not make it too big for memory... I will play with that.. Thanks much for the pointer...
I will also check out the wiki on the do/sleep command... I already tried just running the splashd command in the startup command script, but it only works when I telnet in and run it from there... Strange...
anyway, I have two new employees starting today, so I have to drop this for a few hours and I will be back with what I find on this...
Thanks so much again for your time MJ... I will kick you down for this help... big time.. Do you need anything for your develpment process? I am sure I could part with a few routers if you need them...
Marc,
when the AP is attempting to connect as a client to a remote network in order to repeat it,
is there a log or trace of sorts showing what exactly is going on?
as for the time being, my only indication that it connected, is the cisco logo turning orange, and getting the IP lease..
i'd like to know what's going on in detail when or if the AP fails to connect.
wo-fo, the URL you're referring to shows output generated by the autoap_kick script, and only shows if the AP lost the client connection, and reconnects it
it doesn't actually show the process involved.
in other words, if my connection is failing due to a wrong key.. i'd love to see a relevant failure
the newest release logs to syslogd instead, so you can monitor that regardless of internet connectivity.
i believe that dd-wrt stores the syslog locally if syslogd is enabled and no remote IP address is specified. in that case, you'll want to link the html page to /var/log/messages
i've enabled syslog right after i flashed v24 beta
and i'm tailing the log constantly.. but i do NOT see anything related to the wireless connection establishment, authentication, etc..
in other words, if the connection fails between my AP as a client and a remote AP.. i have nothing in the logs to tell me why
that was true because you needed v24 to utilize repeater mode. but ive got a v24 release posted too. most of hte bugs should be out, and it fixes connection checking (association and dhcp) and adds optional internet checking.
it will run in client or client repeater mode only. (if its in ap mode it will exit and leave the connection alone)
You should just need set up the repeater, then add 'autoap' (no quotes), to the first line in your startup script.
when i have some free time ill get a version that adds wds integration to it. it'd would be cool to build a version that used the strongest connection available amonst the WDS members.
i just flashed your firmware on.. set the SSID to my building's main AP name "SSC Dubai". mode to Repeater.
Physical Interface Wireless Security to WEP, and set the WEP Key of "SSC Dubai"
enabled syslogd, started autoap and watched the logs:
Jan 1 00:06:50 wlan user.notice autoap: scanman - Network SSC DUBAI SNR 47 dB is protected. Modes are ESS WEP ShortSlot
Jan 1 00:06:50 wlan user.notice autoap: scanman - Network CON SNR 18 dB is protected. Modes are ESS WEP ShortPre ShortSlot
Jan 1 00:06:51 wlan user.notice autoap: scanman - Network OIC-ALQ SNR 0 dB is protected. Modes are ESS WEP ShortPre PBCC ShortSlot
Jan 1 00:06:51 wlan user.notice autoap: joinpref - Moving to network 1.
Jan 1 00:06:51 wlan user.notice autoap: joinpref - Trying to connect to .
Jan 1 00:06:57 wlan user.notice autoap: joinpref - Associated to , renewing dhcp lease.
Jan 1 00:06:57 wlan local0.info udhcpc[2564]: Performing a DHCP renew
Jan 1 00:06:57 wlan local0.debug udhcpc[2564]: Sending discover...
Jan 1 00:07:12 wlan user.notice autoap: checkjoin - Reqeusted AP is , currently connected to .
Jan 1 00:07:12 wlan user.notice autoap: checkjoin - Retrying to associate with in 4 seconds
Jan 1 00:07:16 wlan user.notice autoap: checkjoin - Successfully associated with 1, attempting to ping gateway 0.0.0.0.
Jan 1 00:07:20 wlan user.notice autoap: checkjoin - Successfully configured for gateway. Checking for internet.
Jan 1 00:07:20 wlan user.notice autoap: inet_check - Could not contact www.google.com! Will try once more.
Jan 1 00:07:24 wlan user.notice autoap: inet_check - Could not gain internet access. Scanning for new APs.
i like the fact that autoap shows this much debugging..
but would it be possible to set the default WEP key to use with autoap?
it kinda defeats the purpose since i'm not really scanning for any open network to repeat it... but instead i want to repeat one specific network
autoap, thus far, has only checked for open networks. the next update should include wep support. (Try a list of keys against any open wep network)
Does the connection watchdog do what you're looking for? I thought it reset connections for you when they stopped responding... that should be the only thing you need if you're only interested in one ap.
The connection watchdog still doesn't show much
as 'wl join' itself doesn't return any output, and i'm still to figure out how to get it into a debugging mode of sorts
i'm basically trying to connect to a remote AP with an SSID and a WEP Key set.. but nothing happens and my WRT-54GL is simply quiet about it.
no errors, no info on syslog
