Community discussions

MikroTik App
 
bleblas
just joined
Topic Author
Posts: 15
Joined: Fri Mar 30, 2012 10:36 pm
Location: Poland, Żary

capsmanv1 and capsmanv2 problem with roaming

Fri Nov 21, 2014 9:44 am

i have new job to do, i need making wifi roaming network in company.
to mobile workers with wifi devices, still have access to Wifi network and reconnect
automatically to closer AP

so i wanna use cAP 2n and SXTG-2HnD devices in capsman mode.

so i make some test on my office and i find some problem with roaming windows 7 laptop's,
iphone 4 is work very nice, when i go to the hole, (when i have cap2) it is
automatically connect to cap2, i lost max 2 ping's.
but windows 7 laptop with atheros card,don't wanna lost connect with cap1 even signal is -90, just at lost cap1, then connect to cap2, but i get more then 10 ping's lost. tablet with android have this same problem with reconnect to closer cap's

i try find some help on wiki and google, but ther is litter examples and doc's about capsman configuration
pls see on my configuration, and help find solution on this problem

capsman device -> RB750UP (MX_OFFICE)
cap1 -> RBmAP2n (AP_biuro)
cap2 -> RB433AH with card RouterBOARD R52nM (AP_GARAZ)

admin@MX_OFFICE] /caps-man provisioning> print
Flags: X - disabled
0 radio-mac=00:00:00:00:00:00 hw-supported-modes=g
action=create-dynamic-enabled master-configuration=cfg1
slave-configurations="" name-prefix="cfg1"

1 radio-mac=00:00:00:00:00:00 hw-supported-modes=g action=create-enabled
master-configuration=cfg1 slave-configurations=cfg1 name-prefix=""

[admin@MX_OFFICE] /caps-man channel> print
0 name="channel1" frequency=2412 width=20 band=2ghz-onlyg

[admin@MX_OFFICE] /caps-man configuration> print
0 name="cfg1" mode=ap ssid="Office" guard-interval=any country=poland
security=security1 datapath=datapath1 channel=channel1

admin@MX_OFFICE] /caps-man datapath> print
0 name="datapath1" bridge=bridge1 local-forwarding=no

[admin@MX_OFFICE] /caps-man interface> print
Flags: M - master, D - dynamic, B - bound,
X - disabled, I - inactive, R - running
# NAME RADIO-MAC MASTER-INTERFACE
0 M B cap6_garaz 4C:5E:0C:11:3B:XX none
1 M BR cap7_biuro 4C:5E:0C:7C:19:XX none

[admin@MX_OFFICE] /caps-man remote-cap> print
# ADDRESS NAME STATE RADIOS
0 4C:5E:0C:7C:19:XX/56256 CAP... Run 1
1 00:0C:42:32:DD:XX/35768 CAP... Run 1

admin@MX_OFFICE] /caps-man radio> print
Flags: L - local, P - provisioned
# RADIO-MAC INTERFACE REMOTE-CAP-NAME REMOTE-CAP-IDENTITY
0 P 4C:5E:0C:7C:19:XX cap7_biuro CAP-4C5E0C7CXXX AP_biuro
1 P 4C:5E:0C:11:3B:XX cap6_garaz CAP-000C4232XXX AP_GARAZ

...
config on cap1
no bridge, no router
[admin@AP_GARAZ] /interface wireless cap> print
enabled: yes
interfaces: wlan1
certificate: request
lock-to-caps-man: yes
discovery-interfaces: ether1
caps-man-addresses:
caps-man-names:
caps-man-certificate-common-names:
bridge: none
requested-certificate: CAP-000C4232XXXX
locked-caps-man-common-name: CAPsMAN-000C42EDXXXX

..
config on cap2
no bridge, no router
[admin@AP_biuro] /interface wireless cap> print
enabled: yes
interfaces: wlan1
certificate: request
lock-to-caps-man: yes
discovery-interfaces: ether2
caps-man-addresses:
caps-man-names:
caps-man-certificate-common-names:
bridge: none
requested-certificate: CAP-4C5E0C7CXXXX
locked-caps-man-common-name: CAPsMAN-000C42EDXXXX

i try with access-list and drop with bed signal ,but don't help
[admin@MX_OFFICE] /caps-man access-list> print detail
0 interface=all signal-range=-78..120
1 interface=all signal-range=-120..-79 action=reject

thx for help, and sorry for my english ;)

bleblas
 
jarda
Forum Guru
Forum Guru
Posts: 7756
Joined: Mon Oct 22, 2012 4:46 pm

Re: capsmanv1 and capsmanv2 problem with roaming

Fri Nov 21, 2014 7:32 pm

Set more aggressive roaming mode to your laptop card driver. If it doesn't help enough try to set a bit lower transmit power to the ap. The last option would be kicking off the client from ap when it lowers under some signal level threshold. You have to laborate in your actual environment to fine tune such things.
 
bleblas
just joined
Topic Author
Posts: 15
Joined: Fri Mar 30, 2012 10:36 pm
Location: Poland, Żary

Re: capsmanv1 and capsmanv2 problem with roaming

Fri Nov 21, 2014 10:23 pm

Re

it is true, i change card on rb433 with smaller dbi and now work more fine,
but steall access list on capsman don't kick when signal going to -89 down ,even then i use -120..-70 on access list.

access list check signal only when new client connect,
i try to write small script on capsman that list on capman registation table and then kick some client with rx-signal worse then X (-80).

i try what heppen then

thanks for the interest in the topic
bleblas
 
User avatar
NathanA
Forum Veteran
Forum Veteran
Posts: 829
Joined: Tue Aug 03, 2004 9:01 am

Re: capsmanv1 and capsmanv2 problem with roaming

Sun Nov 23, 2014 12:20 am

You don't say what version of RouterOS you are running. For CAPsMAN v1, there was a bug in the access-list with signal level thresholds from 6.11 to 6.15. You need to run 6.16 or newer on the CAPsMAN server for this to work.

You mention CAPsMAN v2. I have never tried CAPsMAN v2 and it might have a similar problem. Try using CAPsMAN v1 (wireless-fp) on a recent RouterOS and see if that causes your access-list rules to start working.

-- Nathan
 
bleblas
just joined
Topic Author
Posts: 15
Joined: Fri Mar 30, 2012 10:36 pm
Location: Poland, Żary

Re: capsmanv1 and capsmanv2 problem with roaming

Mon Nov 24, 2014 9:35 am

hi

i have 6.23rc1 capsman v1 on all cap network devices
 
bleblas
just joined
Topic Author
Posts: 15
Joined: Fri Mar 30, 2012 10:36 pm
Location: Poland, Żary

Re: capsmanv1 and capsmanv2 problem with roaming

Mon Nov 24, 2014 10:42 am

Re

i write some sample script to kick user with signal worst then $MAXsignal.
now roaming work very nice, when capsman kick PC i lost only 2-5 ping's and reconnect to closer Cap's AP.
Caps devices work in one SSID, but another channel.

i will tested this script and write it helps or worsens.
in system scheduler i put interval on 20s, 10s make CPU 100% of use,

# i use max worses singal to "-78"
:local MAXsignal "-78";
:local capsClientId;
:local capsClient;
:local capsClientSignal;

:foreach i in=[/caps-man registration-table find] do={

:set capsClientId [/caps-man registration-table get $i];
:set capsClient [/caps-man registration-table get $i mac-address];
:set capsClientSignal [/caps-man registration-table get $i rx-signal];

:if ("$MAXsignal" > $capsClientSignal) do={
/caps-man registration-table remove $i;
:log info "Caps script kick user $capsClient signal $capsClientSignal";
}
}
thx for reading
bleblas
 
ebreyit
Member Candidate
Member Candidate
Posts: 119
Joined: Tue Apr 30, 2013 11:44 am
Location: Shropshire, United Kingdom

Re: capsmanv1 and capsmanv2 problem with roaming

Fri Jan 09, 2015 11:18 pm

Hi All,
No script required, Access list will achieve what you are looking for.

Checkout this post
http://forum.mikrotik.com/viewtopic.php ... 50#p459889

Important thing to remember is that you MUST have an accept rule to enter the client into the ACL so that you can control automatic disconnection using the second reject rule.

http://wiki.mikrotik.com/wiki/Manual:In ... ccess_List

Who is online

Users browsing this forum: No registered users and 50 guests