I was wondering if anyone knew of an update or had any further
Or in general related to madwifi and roaming or other roaming
apps/daemons on top of drivers.
I have read http://madwifi.org/wiki/ChipsetFeatures/Roaming
and several of the documents there, but I am interested in a simpler
solution(compared with the AP syncing) such as part of the one outlined
in the ticket above. Essentially an rssi threshold fallover, with
increased valid scan frequency.?
* XXX turn this off until the ap release is cut */ if (0 &&
vap->iv_ic->ic_roaming == IEEE80211_ROAMING_AUTO &&
vap->iv_state >= IEEE80211_S_RUN)
/* XXX vap is implicit */ sta_roam_check(ss, vap);
which leads to that roam_check(), which seems to do something useful :).
I tried latest release, recompiling without that forced 0, and indeed
*some roams do seem to occur based on rssi. Is this ok for stas? How
strictly are the iwpriv rssi thresholds observed? Are there parameters
in the scan-aging that could be used to (get more complete scans
Thanks for anything,
From: JOEL LINDSAY <joellindsay@sh...> - 2007-05-29 23:26:57
I have a weird problem. This only happens when madwifi card setup as an AP.
When I try to set the atheros channel using iwconfig ath0 channel 60 from within a script running from inittab, it does not work properly and defaults to mode 11g and channel 1. All other parameters (ssid, rate etc) are all set correctly.
If I run the exact same script after inittab completes, everything is fine. To further complicate things, this only happens to me when my box is setup as a router or to nat, but doesn't happen when its a bridge.
Does anyone have some thoughts or wisdom that may help me figure out why. Presently I am running the script in crontab when necessary, but this is a dirty solution at best.
Get latest updates about Open Source Projects, Conferences and News.