LS 2 Roaming Time

[carrasco]

I have two wireless access points (A and B) conencted to a LAN with enough distance between them allowing to do roaming with two different mobile stations -STA- (a LS2 and a Generic miniPCI). A central PC conencted to the LAN runs pings (64 bytes every 1 sec) continually to each STA. So when both STAs roam from A to B or viceversa, always the miniPCI shows no more than 3 pings dropped (in time: 3 secs), but the LS2 drops around 12 (12 secs).

So now the questions:

1. Is there a parameter that could be configured in the LS2 to be more aggressive for roaming, reducing the roaming time?
(I tried reducing the scan list channels to 1, 6, 11 but no difference)

2. I have also noticed that with any rate algorithm (Concervative (best results), Optimistic and EWMA) the LS2 hold the link until there is no signal (or the RSSI is really low) to switch to another access point.
Is there a parameter to determine that if the RSSI is below -XX dBm start scanning for other access point available in the neighborhood?


Config:
users.status=enabled
radio.1.thresh62g=28
radio.1.thresh62b=28
radio.1.thresh62a=28
wireless.1.l2_isolation=enabled
netconf.2.allmulti=disabled
radio.1.dfs.status=
wireless.1.addmtikie=enabled
wireless.1.sper=disabled
tshaper.status=disabled
wireless.1.signal_led4=64
wireless.1.signal_led3=74
wireless.1.signal_led2=84
wireless.1.signal_led1=94
wireless.1.compression=disabled
wireless.1.frameburst=disabled
wireless.1.fastframes=disabled
radio.1.frag=off
radio.1.rts=off
wireless.1.wmmlevel=-1
wireless.1.wmm=disabled
bridge.1.stp.status=disabled
igmpproxy.status=disabled
ebtables.51.status=disabled
ebtables.50.status=disabled
iptables.3.status=disabled
wireless.1.scan_list.status=enabled
radio.1.chanshift=0
radio.1.mcastrate=1M
snmp.location=mmx
snmp.contact=mmx
snmp.community=mmx
snmp.status=enabled
ls_logo.url=
ls_logo.status=disabled
users.1.status=enabled
users.1.name=mms
users.1.password=CctaS8i.MfQdQ
httpd.status=enabled
httpd.port.http=80
radio.status=enabled
radio.countrycode=840
radio.ratemodule=ath_rate_onoe
radio.1.status=enabled
radio.1.devname=ath0
radio.1.mode=managed
radio.1.rate.max=54M
radio.1.rate.auto=enabled
radio.1.ieee_mode=g
radio.1.txpower=10
radio.1.acktimeout=21
radio.1.ack.auto=enabled
radio.1.rx_antenna_diversity=disabled
radio.1.tx_antenna_diversity=disabled
radio.1.rx_antenna=1
radio.1.tx_antenna=1
wireless.status=enabled
wireless.1.status=enabled
wireless.1.devname=ath0
wireless.1.security=wep64
wireless.1.ssid=SSID
wireless.1.hide_ssid=disabled
wireless.1.rssi_led1=1
wireless.1.rssi_led2=15
wireless.1.rssi_led3=22
wireless.1.rssi_led4=30
bridge.status=enabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.2.devname=ath0
netconf.status=enabled
netconf.1.status=enabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.up=enabled
netconf.1.promisc=enabled
netconf.2.status=enabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.up=enabled
netconf.3.status=enabled
netconf.3.devname=br0
netconf.3.ip=172.30.13.44
netconf.3.netmask=255.255.0.0
netconf.3.up=enabled
dhcpd.status=disabled
dhcpd.1.status=disabled
dhcpc.status=disabled
dhcpc.1.status=disabled
dhcpc.1.devname=br0
route.status=enabled
route.1.status=enabled
route.1.devname=br0
route.1.gateway=172.30.0.1
route.1.ip=0.0.0.0
route.1.netmask=0
ebtables.status=enabled
ebtables.1.status=enabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=enabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.3.status=enabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
wireless.1.wds=disabled
wireless.1.macclone=disabled
radio.1.countrycode=840
radio.1.clksel=0
wireless.1.authmode=1
wireless.1.ap=
wpasupplicant.status=disabled
wpasupplicant.device.1.status=disabled
aaa.status=disabled
aaa.1.status=disabled
wireless.1.security.default_key=1
wireless.1.security.1.key=1f2e3d4c5b
ppp.1.password=
ppp.status=disabled
ppp.1.status=disabled
iptables.status=disabled
resolv.nameserver.1.status=enabled
resolv.nameserver.1.ip=0.0.0.0
resolv.nameserver.2.status=disabled
resolv.nameserver.2.ip=
resolv.status=enabled
netmode=bridge
wireless.1.scan_list.channels=1, 6, 11
sshd.status=enabled
sshd.port=22

[UBNT-Mike.Ford]

Hello Carrasco,

Please be aware that our software does not have roaming capabilities, and for the most part, client roaming is based on the software running on the client side.

Thanks,

Mike

[carrasco]

Please be aware that our software does not have roaming capabilities, and for the most part, client roaming is based on the software running on the client side.

Mike

Mike, for clarification, when you say 'our software does not have roaming capabilities' it refers to the LS2 in Station Mode? If so, why this simple feature has not been implemented yet?

Thanks.

[UBNT-Mike.Taylor]

carrasco,

Our driver has roaming capabilities of course. We don't allow you to adjust the roaming thresholds in the user interface though. We've tried to keep things simple in the UI.

For the kind of application our CPE equipment is normally put to - (point to multipoint, point to point, and fixed locations usually) aggressive roaming is not usually desirable.

If you want to tune the roaming settings for your application, you can use the persistent scripts (procedure described elsewhere in this forum) to set the madwifi roaming parameters. Use "iwpriv ath0" command to see the roaming settings and current values. hostroaming enables/disables.

Cheers,

Mike

[carrasco]

Our driver has roaming capabilities of course. We don't allow you to adjust the roaming thresholds in the user interface though. We've tried to keep things simple in the UI.

Could you include it at the top of the wish list please?

If you want to tune the roaming settings for your application, you can use the persistent scripts (procedure described elsewhere in this forum) to set the madwifi roaming parameters. Use "iwpriv ath0" command to see the roaming settings and current values. hostroaming enables/disables.

I tried with 'iwpriv ath0' and the only parameters available that include 'roaming' are 'get_roaming' (set at 1 by default). Then I tried setting it at '0' and '2' without good results. Higher values are not valid.

iwpriv ath0 get_roaming
Setting alternatives
iwpriv ath0 set_roaming 0
iwpriv ath0 set_roaming 1
iwpriv ath0 set_roaming 2

What I am missing....

Thanks for responding.

[UBNT-keba]

There is RSSI setting that specifies what is RSSI level to roam:

iwpriv
rssi11b
get_rssi11b
rssi11g
get_rssi11g

BTW: as it was said, UBTN LS/NS/PS devices are optimised for fixed wireless.

[carrasco]

BTW: as it was said, UBTN LS/NS/PS devices are optimised for fixed wireless.

When you say that these devices are optimized for... does it means that just the roaming feature is not enabled on these ones?
In fact when I execute 'iwpriv ath0 roam' it responses 'This device doesn't support roaming'. Is there a work around (or trick) that could enable this on the LS?

Thanks

[carrasco]

Hi UBNT Guys,

Please add to AirOS roaming capabilities for all UBNT embedded systems and wireless isp solutions.

Best Regards,
Carrasco

[bluestu]

Seconded. There are alot of people using these devises in a mobile setup (me included).

Thanks

s

[fbaffoni]

There is RSSI setting that specifies what is RSSI level to roam:

iwpriv
rssi11b
get_rssi11b
rssi11g
get_rssi11g

BTW: as it was said, UBTN LS/NS/PS devices are optimised for fixed wireless.

UBNT-keba, if the IEEE standard used is 802.11n (NS5M), will the rssi11b/g/a command work anyway?

I was looking for a rssi11n command to change the threshold value, but doesn't exist.