Thread: [Madwifi-devel] Help with setchanlist
Status: Beta
Brought to you by:
otaku
From: Aditya B. <ay...@an...> - 2010-07-09 21:39:54
|
Hi, Can someone please provide an example of how to use setchanlist? In my work, Im enabling 5/10 MHz channels and by changing ath_mhz2ieee(), I have given each channel a different number. In my simple AP-STA network, what I am observing is the following 1. Every time the STA gets associated with the AP, it remains on the channel for a short duration of time (maybe 10-20s) and then loses association. As a result, it restarts scanning and because there are now so many channels to scan, it takes a long time for the STA to get reassociated again. Is this normal? Why is the STA rescanning when it has found and associated with an AP? What I want to do is the following 1. Initially the STA scans its whole channel list to find the AP. Once it finds the AP (from the configured ESSID and channel number), it stops scanning for other APs. Even if somehow it loses association (say for example a large number of consecutive missed beacons), it should only scan again in the configured channel number. Essentially, once the STA finds the AP, it should reduce its channel list to only 1 channel. Can someone provide hints on how to do this? Thanks regards, Aditya Bhave |
From: Kelly H. <ks...@bl...> - 2010-07-09 22:56:36
|
iwpriv $DEVICE hostroaming 2 On the station device This will pin the selection/association to the userland code, and disassociating will not change the channel. Be sure to set all aspects of the connection or you will not get an association. On Jul 9, 2010, at 3:39 PM, Aditya Bhave wrote: > Hi, > > Can someone please provide an example of how to use setchanlist? > > In my work, Im enabling 5/10 MHz channels and by changing > ath_mhz2ieee(), I have given each channel a different number. In my > simple AP-STA network, what I am observing is the following > > 1. Every time the STA gets associated with the AP, it remains on the > channel for a short duration of time (maybe 10-20s) and then loses > association. As a result, it restarts scanning and because there are now > so many channels to scan, it takes a long time for the STA to get > reassociated again. Is this normal? Why is the STA rescanning when it > has found and associated with an AP? > > What I want to do is the following > > 1. Initially the STA scans its whole channel list to find the AP. Once > it finds the AP (from the configured ESSID and channel number), it stops > scanning for other APs. Even if somehow it loses association (say for > example a large number of consecutive missed beacons), it should only > scan again in the configured channel number. Essentially, once the STA > finds the AP, it should reduce its channel list to only 1 channel. > > Can someone provide hints on how to do this? > > Thanks > regards, > Aditya Bhave > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel |
From: Aditya B. <ay...@an...> - 2010-07-10 18:40:43
|
Hi, This did not work. Given below is the script I use to configure the STA sudo modprobe ath_pci sudo wlanconfig ath0 destroy sudo wlanconfig ath0 create wlandev wifi0 wlanmode managed sudo iwpriv ath0 mode 11g sudo iwconfig ath0 essid e_ap channel 6 ap 00:02:6F:21:EC:B9 sudo iwpriv ath0 hostroaming 2 sleep 1 sudo ifconfig ath0 up sleep 2 sudo ifconfig ath0 10.1.1.2 netmask 255.255.255.0 sudo sysctl -w dev.wifi0.diversity=0 sudo sysctl -w dev.wifi0.txantenna=1 sudo sysctl -w dev.wifi0.rxantenna=1 sudo 80211debug +assoc +scan +state sudo athdebug +reset +beacon +rate iwconfig ath0 ifconfig ath0 The STA never finds the AP and never gets associated. I use the following script to configure the AP sudo modprobe ath_pci sudo wlanconfig ath0 destroy sudo wlanconfig ath0 create wlandev wifi0 wlanmode ap sudo iwpriv ath0 mode 11g sudo iwconfig ath0 essid e_ap channel 6 sleep 1 sudo ifconfig ath0 up sleep 2 sudo ifconfig ath0 10.1.1.1 netmask 255.255.255.0 sudo sysctl -w dev.wifi0.diversity=0 sudo sysctl -w dev.wifi0.txantenna=1 sudo sysctl -w dev.wifi0.rxantenna=1 sudo 80211debug +assoc +scan +state sudo athdebug +reset +beacon +rate +state iwconfig ath0 ifconfig ath0 Thanks for your help regards, Aditya Bhave On 07/09/2010 06:27 PM, Kelly Hogan wrote: > iwpriv $DEVICE hostroaming 2 > > On the station device > > This will pin the selection/association to the userland code, and disassociating will not change the channel. Be sure to set all aspects of the connection or you will not get an association. > On Jul 9, 2010, at 3:39 PM, Aditya Bhave wrote: > > >> Hi, >> >> Can someone please provide an example of how to use setchanlist? >> >> In my work, Im enabling 5/10 MHz channels and by changing >> ath_mhz2ieee(), I have given each channel a different number. In my >> simple AP-STA network, what I am observing is the following >> >> 1. Every time the STA gets associated with the AP, it remains on the >> channel for a short duration of time (maybe 10-20s) and then loses >> association. As a result, it restarts scanning and because there are now >> so many channels to scan, it takes a long time for the STA to get >> reassociated again. Is this normal? Why is the STA rescanning when it >> has found and associated with an AP? >> >> What I want to do is the following >> >> 1. Initially the STA scans its whole channel list to find the AP. Once >> it finds the AP (from the configured ESSID and channel number), it stops >> scanning for other APs. Even if somehow it loses association (say for >> example a large number of consecutive missed beacons), it should only >> scan again in the configured channel number. Essentially, once the STA >> finds the AP, it should reduce its channel list to only 1 channel. >> >> Can someone provide hints on how to do this? >> >> Thanks >> regards, >> Aditya Bhave >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Madwifi-devel mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel > > |
From: Kelly H. <ks...@bl...> - 2010-07-11 05:53:01
|
After setting the essid and ap, change the hostroaming mode to 1, let it scan and find, then change to hostroaming 2 at that point. I've seen it when teh card will not associate until I put it in a 1 or 0 hostroaming mode (maybe it initiates a scan at the driver level) and then associates. I've even done a channel change to a wrong change to make it lock back on the other correct change. Once I see the association, I set to 2 to prevent any falloff if it disassociates. Also, timing on the iwconfig commands has caused me grief in the past. I see your sleep, but stick some larger sleeps statements in there too. Sometimes it can take a few seconds to associate on even a 680mhz routerstation. On Jul 10, 2010, at 12:40 PM, Aditya Bhave wrote: > Hi, > > This did not work. Given below is the script I use to configure the STA > > sudo modprobe ath_pci > sudo wlanconfig ath0 destroy > sudo wlanconfig ath0 create wlandev wifi0 wlanmode managed > sudo iwpriv ath0 mode 11g > sudo iwconfig ath0 essid e_ap channel 6 ap 00:02:6F:21:EC:B9 > sudo iwpriv ath0 hostroaming 2 > sleep 1 > > sudo ifconfig ath0 up > sleep 2 > sudo ifconfig ath0 10.1.1.2 netmask 255.255.255.0 > > sudo sysctl -w dev.wifi0.diversity=0 > sudo sysctl -w dev.wifi0.txantenna=1 > sudo sysctl -w dev.wifi0.rxantenna=1 > > sudo 80211debug +assoc +scan +state > sudo athdebug +reset +beacon +rate > > iwconfig ath0 > ifconfig ath0 > > > The STA never finds the AP and never gets associated. I use the following script to configure the AP > > sudo modprobe ath_pci > sudo wlanconfig ath0 destroy > sudo wlanconfig ath0 create wlandev wifi0 wlanmode ap > sudo iwpriv ath0 mode 11g > sudo iwconfig ath0 essid e_ap channel 6 > sleep 1 > > sudo ifconfig ath0 up > sleep 2 > sudo ifconfig ath0 10.1.1.1 netmask 255.255.255.0 > > sudo sysctl -w dev.wifi0.diversity=0 > sudo sysctl -w dev.wifi0.txantenna=1 > sudo sysctl -w dev.wifi0.rxantenna=1 > > sudo 80211debug +assoc +scan +state > sudo athdebug +reset +beacon +rate +state > > iwconfig ath0 > ifconfig ath0 > > Thanks for your help > regards, > Aditya Bhave > > > > On 07/09/2010 06:27 PM, Kelly Hogan wrote: >> iwpriv $DEVICE hostroaming 2 >> >> On the station device >> >> This will pin the selection/association to the userland code, and disassociating will not change the channel. Be sure to set all aspects of the connection or you will not get an association. >> On Jul 9, 2010, at 3:39 PM, Aditya Bhave wrote: >> >> >>> Hi, >>> >>> Can someone please provide an example of how to use setchanlist? >>> >>> In my work, Im enabling 5/10 MHz channels and by changing >>> ath_mhz2ieee(), I have given each channel a different number. In my >>> simple AP-STA network, what I am observing is the following >>> >>> 1. Every time the STA gets associated with the AP, it remains on the >>> channel for a short duration of time (maybe 10-20s) and then loses >>> association. As a result, it restarts scanning and because there are now >>> so many channels to scan, it takes a long time for the STA to get >>> reassociated again. Is this normal? Why is the STA rescanning when it >>> has found and associated with an AP? >>> >>> What I want to do is the following >>> >>> 1. Initially the STA scans its whole channel list to find the AP. Once >>> it finds the AP (from the configured ESSID and channel number), it stops >>> scanning for other APs. Even if somehow it loses association (say for >>> example a large number of consecutive missed beacons), it should only >>> scan again in the configured channel number. Essentially, once the STA >>> finds the AP, it should reduce its channel list to only 1 channel. >>> >>> Can someone provide hints on how to do this? >>> >>> Thanks >>> regards, >>> Aditya Bhave >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Sprint >>> What will you do first with EVO, the first 4G phone? >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>> _______________________________________________ >>> Madwifi-devel mailing list >>> Mad...@li... >>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Madwifi-devel mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >> >> > |
From: Aditya B. <ay...@an...> - 2010-07-11 14:02:02
|
Hi, Thanks for your reply. Im running some automated experiments with MadWifi where my script changes the channel on AP and STA, runs iperf for a while, changes the channel again on both AP and STA, runs the test again etc. So Im not in front of my computer watching when the STA associates. Can you suggest where in the source code I can make this change? I want to change the mode to 2 as soon as the STA associates. Secondly is it necessary to specify the AP? Wont specifying the ESSID and channel number be enough? regards, Aditya Bhave On 07/11/2010 12:53 AM, Kelly Hogan wrote: > After setting the essid and ap, change the hostroaming mode to 1, let it scan and find, then change to hostroaming 2 at that point. I've seen it when teh card will not associate until I put it in a 1 or 0 hostroaming mode (maybe it initiates a scan at the driver level) and then associates. I've even done a channel change to a wrong change to make it lock back on the other correct change. Once I see the association, I set to 2 to prevent any falloff if it disassociates. > > Also, timing on the iwconfig commands has caused me grief in the past. I see your sleep, but stick some larger sleeps statements in there too. Sometimes it can take a few seconds to associate on even a 680mhz routerstation. > > On Jul 10, 2010, at 12:40 PM, Aditya Bhave wrote: > > >> Hi, >> >> This did not work. Given below is the script I use to configure the STA >> >> sudo modprobe ath_pci >> sudo wlanconfig ath0 destroy >> sudo wlanconfig ath0 create wlandev wifi0 wlanmode managed >> sudo iwpriv ath0 mode 11g >> sudo iwconfig ath0 essid e_ap channel 6 ap 00:02:6F:21:EC:B9 >> sudo iwpriv ath0 hostroaming 2 >> sleep 1 >> >> sudo ifconfig ath0 up >> sleep 2 >> sudo ifconfig ath0 10.1.1.2 netmask 255.255.255.0 >> >> sudo sysctl -w dev.wifi0.diversity=0 >> sudo sysctl -w dev.wifi0.txantenna=1 >> sudo sysctl -w dev.wifi0.rxantenna=1 >> >> sudo 80211debug +assoc +scan +state >> sudo athdebug +reset +beacon +rate >> >> iwconfig ath0 >> ifconfig ath0 >> >> >> The STA never finds the AP and never gets associated. I use the following script to configure the AP >> >> sudo modprobe ath_pci >> sudo wlanconfig ath0 destroy >> sudo wlanconfig ath0 create wlandev wifi0 wlanmode ap >> sudo iwpriv ath0 mode 11g >> sudo iwconfig ath0 essid e_ap channel 6 >> sleep 1 >> >> sudo ifconfig ath0 up >> sleep 2 >> sudo ifconfig ath0 10.1.1.1 netmask 255.255.255.0 >> >> sudo sysctl -w dev.wifi0.diversity=0 >> sudo sysctl -w dev.wifi0.txantenna=1 >> sudo sysctl -w dev.wifi0.rxantenna=1 >> >> sudo 80211debug +assoc +scan +state >> sudo athdebug +reset +beacon +rate +state >> >> iwconfig ath0 >> ifconfig ath0 >> >> Thanks for your help >> regards, >> Aditya Bhave >> >> >> >> On 07/09/2010 06:27 PM, Kelly Hogan wrote: >> >>> iwpriv $DEVICE hostroaming 2 >>> >>> On the station device >>> >>> This will pin the selection/association to the userland code, and disassociating will not change the channel. Be sure to set all aspects of the connection or you will not get an association. >>> On Jul 9, 2010, at 3:39 PM, Aditya Bhave wrote: >>> >>> >>> >>>> Hi, >>>> >>>> Can someone please provide an example of how to use setchanlist? >>>> >>>> In my work, Im enabling 5/10 MHz channels and by changing >>>> ath_mhz2ieee(), I have given each channel a different number. In my >>>> simple AP-STA network, what I am observing is the following >>>> >>>> 1. Every time the STA gets associated with the AP, it remains on the >>>> channel for a short duration of time (maybe 10-20s) and then loses >>>> association. As a result, it restarts scanning and because there are now >>>> so many channels to scan, it takes a long time for the STA to get >>>> reassociated again. Is this normal? Why is the STA rescanning when it >>>> has found and associated with an AP? >>>> >>>> What I want to do is the following >>>> >>>> 1. Initially the STA scans its whole channel list to find the AP. Once >>>> it finds the AP (from the configured ESSID and channel number), it stops >>>> scanning for other APs. Even if somehow it loses association (say for >>>> example a large number of consecutive missed beacons), it should only >>>> scan again in the configured channel number. Essentially, once the STA >>>> finds the AP, it should reduce its channel list to only 1 channel. >>>> >>>> Can someone provide hints on how to do this? >>>> >>>> Thanks >>>> regards, >>>> Aditya Bhave >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by Sprint >>>> What will you do first with EVO, the first 4G phone? >>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>>> _______________________________________________ >>>> Madwifi-devel mailing list >>>> Mad...@li... >>>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>>> >>>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Sprint >>> What will you do first with EVO, the first 4G phone? >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>> _______________________________________________ >>> Madwifi-devel mailing list >>> Mad...@li... >>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>> >>> >>> >> > > |
From: Kelly H. <ks...@bl...> - 2010-07-11 15:52:27
|
If using hostroaming 2, We've found that you need the following specifics: 1) ESSID and AP 2) channel to an incorrect channel, then to correct -or- an iwlist $DEVICE scan while in hostroamin =< 1 3) Reset to exact ESSID, AP, CHANNEL and hostroaming 2 upon association. For determining the associate is there, here is a stanza of bash that will do that. echo "Spinning To Let Association Happen...." | $logger i=1 iwconfig $interface essid $newssid ap $bridgemac # set spincount on machine speed if [ $MACHINE = "UBNTRS" ]; then spincount=150 else spincount=30 fi while [ "$(iwconfig $interface | grep 'Link Quality='| awk -F'[/=]' '{print $2}')" -eq 0 ]; do echo "Spinning for signal quality above 0...." $i | $logger i=$(($i + 1)) [ "$i" -gt $spincount ] && break done Not that a machine the RS is so fast that your spinlocks need to be adjusted to allow the correct amount of time to connect. Hoep this helps... On Jul 11, 2010, at 7:31 AM, Aditya Bhave wrote: > Hi, > > Thanks for your reply. Im running some automated experiments with > MadWifi where my script changes the channel on AP and STA, runs iperf > for a while, changes the channel again on both AP and STA, runs the test > again etc. So Im not in front of my computer watching when the STA > associates. Can you suggest where in the source code I can make this > change? I want to change the mode to 2 as soon as the STA associates. > > > Secondly is it necessary to specify the AP? Wont specifying the ESSID > and channel number be enough? > > > regards, > Aditya Bhave > > > > On 07/11/2010 12:53 AM, Kelly Hogan wrote: >> After setting the essid and ap, change the hostroaming mode to 1, let it scan and find, then change to hostroaming 2 at that point. I've seen it when teh card will not associate until I put it in a 1 or 0 hostroaming mode (maybe it initiates a scan at the driver level) and then associates. I've even done a channel change to a wrong change to make it lock back on the other correct change. Once I see the association, I set to 2 to prevent any falloff if it disassociates. >> >> Also, timing on the iwconfig commands has caused me grief in the past. I see your sleep, but stick some larger sleeps statements in there too. Sometimes it can take a few seconds to associate on even a 680mhz routerstation. >> >> On Jul 10, 2010, at 12:40 PM, Aditya Bhave wrote: >> >> >>> Hi, >>> >>> This did not work. Given below is the script I use to configure the STA >>> >>> sudo modprobe ath_pci >>> sudo wlanconfig ath0 destroy >>> sudo wlanconfig ath0 create wlandev wifi0 wlanmode managed >>> sudo iwpriv ath0 mode 11g >>> sudo iwconfig ath0 essid e_ap channel 6 ap 00:02:6F:21:EC:B9 >>> sudo iwpriv ath0 hostroaming 2 >>> sleep 1 >>> >>> sudo ifconfig ath0 up >>> sleep 2 >>> sudo ifconfig ath0 10.1.1.2 netmask 255.255.255.0 >>> >>> sudo sysctl -w dev.wifi0.diversity=0 >>> sudo sysctl -w dev.wifi0.txantenna=1 >>> sudo sysctl -w dev.wifi0.rxantenna=1 >>> >>> sudo 80211debug +assoc +scan +state >>> sudo athdebug +reset +beacon +rate >>> >>> iwconfig ath0 >>> ifconfig ath0 >>> >>> >>> The STA never finds the AP and never gets associated. I use the following script to configure the AP >>> >>> sudo modprobe ath_pci >>> sudo wlanconfig ath0 destroy >>> sudo wlanconfig ath0 create wlandev wifi0 wlanmode ap >>> sudo iwpriv ath0 mode 11g >>> sudo iwconfig ath0 essid e_ap channel 6 >>> sleep 1 >>> >>> sudo ifconfig ath0 up >>> sleep 2 >>> sudo ifconfig ath0 10.1.1.1 netmask 255.255.255.0 >>> >>> sudo sysctl -w dev.wifi0.diversity=0 >>> sudo sysctl -w dev.wifi0.txantenna=1 >>> sudo sysctl -w dev.wifi0.rxantenna=1 >>> >>> sudo 80211debug +assoc +scan +state >>> sudo athdebug +reset +beacon +rate +state >>> >>> iwconfig ath0 >>> ifconfig ath0 >>> >>> Thanks for your help >>> regards, >>> Aditya Bhave >>> >>> >>> >>> On 07/09/2010 06:27 PM, Kelly Hogan wrote: >>> >>>> iwpriv $DEVICE hostroaming 2 >>>> >>>> On the station device >>>> >>>> This will pin the selection/association to the userland code, and disassociating will not change the channel. Be sure to set all aspects of the connection or you will not get an association. >>>> On Jul 9, 2010, at 3:39 PM, Aditya Bhave wrote: >>>> >>>> >>>> >>>>> Hi, >>>>> >>>>> Can someone please provide an example of how to use setchanlist? >>>>> >>>>> In my work, Im enabling 5/10 MHz channels and by changing >>>>> ath_mhz2ieee(), I have given each channel a different number. In my >>>>> simple AP-STA network, what I am observing is the following >>>>> >>>>> 1. Every time the STA gets associated with the AP, it remains on the >>>>> channel for a short duration of time (maybe 10-20s) and then loses >>>>> association. As a result, it restarts scanning and because there are now >>>>> so many channels to scan, it takes a long time for the STA to get >>>>> reassociated again. Is this normal? Why is the STA rescanning when it >>>>> has found and associated with an AP? >>>>> >>>>> What I want to do is the following >>>>> >>>>> 1. Initially the STA scans its whole channel list to find the AP. Once >>>>> it finds the AP (from the configured ESSID and channel number), it stops >>>>> scanning for other APs. Even if somehow it loses association (say for >>>>> example a large number of consecutive missed beacons), it should only >>>>> scan again in the configured channel number. Essentially, once the STA >>>>> finds the AP, it should reduce its channel list to only 1 channel. >>>>> >>>>> Can someone provide hints on how to do this? >>>>> >>>>> Thanks >>>>> regards, >>>>> Aditya Bhave >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.net email is sponsored by Sprint >>>>> What will you do first with EVO, the first 4G phone? >>>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>>>> _______________________________________________ >>>>> Madwifi-devel mailing list >>>>> Mad...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>>>> >>>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by Sprint >>>> What will you do first with EVO, the first 4G phone? >>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>>> _______________________________________________ >>>> Madwifi-devel mailing list >>>> Mad...@li... >>>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>>> >>>> >>>> >>> >> >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel |
From: Aditya B. <ay...@an...> - 2010-07-13 04:07:34
|
Ive noticed that while the STA is scanning, the link quality can go above zero even if it hasnt completed association with an AP. The script should perhaps check for the status of "Access Point" to see if the association has taken place. Im not too good with awk. Can you suggest what changes need to be made to look for the Access Point field. Secondly, how do I use this script from within say a C program? Is it as simple as system(assocChecker.sh); system("sudo iwpriv ath0 hostroaming 2"); Thanks regards, Aditya Bhave On 07/11/2010 11:52 AM, Kelly Hogan wrote: > If using hostroaming 2, We've found that you need the following specifics: > > 1) ESSID and AP > 2) channel to an incorrect channel, then to correct > -or- > an iwlist $DEVICE scan while in hostroamin =< 1 > 3) Reset to exact ESSID, AP, CHANNEL and hostroaming 2 upon association. > > For determining the associate is there, here is a stanza of bash that will do that. > > echo "Spinning To Let Association Happen...." | $logger > i=1 > iwconfig $interface essid $newssid ap $bridgemac > # set spincount on machine speed > if [ $MACHINE = "UBNTRS" ]; then > spincount=150 > else > spincount=30 > fi > while [ "$(iwconfig $interface | grep 'Link Quality='| awk -F'[/=]' '{print $2}')" -eq 0 ]; do > echo "Spinning for signal quality above 0...." $i | $logger > i=$(($i + 1)) > [ "$i" -gt $spincount ]&& break > done > > Not that a machine the RS is so fast that your spinlocks need to be adjusted to allow the correct amount of time to connect. > > Hoep this helps... > > On Jul 11, 2010, at 7:31 AM, Aditya Bhave wrote: > > >> Hi, >> >> Thanks for your reply. Im running some automated experiments with >> MadWifi where my script changes the channel on AP and STA, runs iperf >> for a while, changes the channel again on both AP and STA, runs the test >> again etc. So Im not in front of my computer watching when the STA >> associates. Can you suggest where in the source code I can make this >> change? I want to change the mode to 2 as soon as the STA associates. >> >> >> Secondly is it necessary to specify the AP? Wont specifying the ESSID >> and channel number be enough? >> >> >> regards, >> Aditya Bhave >> >> >> >> On 07/11/2010 12:53 AM, Kelly Hogan wrote: >> >>> After setting the essid and ap, change the hostroaming mode to 1, let it scan and find, then change to hostroaming 2 at that point. I've seen it when teh card will not associate until I put it in a 1 or 0 hostroaming mode (maybe it initiates a scan at the driver level) and then associates. I've even done a channel change to a wrong change to make it lock back on the other correct change. Once I see the association, I set to 2 to prevent any falloff if it disassociates. >>> >>> Also, timing on the iwconfig commands has caused me grief in the past. I see your sleep, but stick some larger sleeps statements in there too. Sometimes it can take a few seconds to associate on even a 680mhz routerstation. >>> >>> On Jul 10, 2010, at 12:40 PM, Aditya Bhave wrote: >>> >>> >>> >>>> Hi, >>>> >>>> This did not work. Given below is the script I use to configure the STA >>>> >>>> sudo modprobe ath_pci >>>> sudo wlanconfig ath0 destroy >>>> sudo wlanconfig ath0 create wlandev wifi0 wlanmode managed >>>> sudo iwpriv ath0 mode 11g >>>> sudo iwconfig ath0 essid e_ap channel 6 ap 00:02:6F:21:EC:B9 >>>> sudo iwpriv ath0 hostroaming 2 >>>> sleep 1 >>>> >>>> sudo ifconfig ath0 up >>>> sleep 2 >>>> sudo ifconfig ath0 10.1.1.2 netmask 255.255.255.0 >>>> >>>> sudo sysctl -w dev.wifi0.diversity=0 >>>> sudo sysctl -w dev.wifi0.txantenna=1 >>>> sudo sysctl -w dev.wifi0.rxantenna=1 >>>> >>>> sudo 80211debug +assoc +scan +state >>>> sudo athdebug +reset +beacon +rate >>>> >>>> iwconfig ath0 >>>> ifconfig ath0 >>>> >>>> >>>> The STA never finds the AP and never gets associated. I use the following script to configure the AP >>>> >>>> sudo modprobe ath_pci >>>> sudo wlanconfig ath0 destroy >>>> sudo wlanconfig ath0 create wlandev wifi0 wlanmode ap >>>> sudo iwpriv ath0 mode 11g >>>> sudo iwconfig ath0 essid e_ap channel 6 >>>> sleep 1 >>>> >>>> sudo ifconfig ath0 up >>>> sleep 2 >>>> sudo ifconfig ath0 10.1.1.1 netmask 255.255.255.0 >>>> >>>> sudo sysctl -w dev.wifi0.diversity=0 >>>> sudo sysctl -w dev.wifi0.txantenna=1 >>>> sudo sysctl -w dev.wifi0.rxantenna=1 >>>> >>>> sudo 80211debug +assoc +scan +state >>>> sudo athdebug +reset +beacon +rate +state >>>> >>>> iwconfig ath0 >>>> ifconfig ath0 >>>> >>>> Thanks for your help >>>> regards, >>>> Aditya Bhave >>>> >>>> >>>> >>>> On 07/09/2010 06:27 PM, Kelly Hogan wrote: >>>> >>>> >>>>> iwpriv $DEVICE hostroaming 2 >>>>> >>>>> On the station device >>>>> >>>>> This will pin the selection/association to the userland code, and disassociating will not change the channel. Be sure to set all aspects of the connection or you will not get an association. >>>>> On Jul 9, 2010, at 3:39 PM, Aditya Bhave wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> Can someone please provide an example of how to use setchanlist? >>>>>> >>>>>> In my work, Im enabling 5/10 MHz channels and by changing >>>>>> ath_mhz2ieee(), I have given each channel a different number. In my >>>>>> simple AP-STA network, what I am observing is the following >>>>>> >>>>>> 1. Every time the STA gets associated with the AP, it remains on the >>>>>> channel for a short duration of time (maybe 10-20s) and then loses >>>>>> association. As a result, it restarts scanning and because there are now >>>>>> so many channels to scan, it takes a long time for the STA to get >>>>>> reassociated again. Is this normal? Why is the STA rescanning when it >>>>>> has found and associated with an AP? >>>>>> >>>>>> What I want to do is the following >>>>>> >>>>>> 1. Initially the STA scans its whole channel list to find the AP. Once >>>>>> it finds the AP (from the configured ESSID and channel number), it stops >>>>>> scanning for other APs. Even if somehow it loses association (say for >>>>>> example a large number of consecutive missed beacons), it should only >>>>>> scan again in the configured channel number. Essentially, once the STA >>>>>> finds the AP, it should reduce its channel list to only 1 channel. >>>>>> >>>>>> Can someone provide hints on how to do this? >>>>>> >>>>>> Thanks >>>>>> regards, >>>>>> Aditya Bhave >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> This SF.net email is sponsored by Sprint >>>>>> What will you do first with EVO, the first 4G phone? >>>>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>>>>> _______________________________________________ >>>>>> Madwifi-devel mailing list >>>>>> Mad...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>>>>> >>>>>> >>>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.net email is sponsored by Sprint >>>>> What will you do first with EVO, the first 4G phone? >>>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>>>> _______________________________________________ >>>>> Madwifi-devel mailing list >>>>> Mad...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Madwifi-devel mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-devel >> > > |