Hi All, Have a 30 odd CAPsMAN deployment with the WAPac unit - It seems that Android v6 clients (to which we have 1) seem to have issues connecting. Spent a few hours on it today and if I set an ACL for the test phone I'm working with to Signal Range not set and AP/Client TX Limit to 0 it connects but bounces. It seems to prefer only want to connect to one access point which I cannot work out why - Tried removing re-adding from the phone etc. All the normal stuff but not happy. CAPsMAN device is a CCR running 6.39.2 and all the AP's are same version. Any suggestions? Cheers, Dave
Hi Dave, Logs? Wireless debug logs are usually quite helpful in these cases! Also, have you tried ruling out capsman as a contributor? (by manually configuring one AP and connect to it?) Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Wednesday, 14 June 2017 11:17 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] Mikrotik CAPsMAN Android
Hi All,
Have a 30 odd CAPsMAN deployment with the WAPac unit - It seems that Android v6 clients (to which we have 1) seem to have issues connecting. Spent a few hours on it today and if I set an ACL for the test phone I'm working with to Signal Range not set and AP/Client TX Limit to 0 it connects but bounces. It seems to prefer only want to connect to one access point which I cannot work out why - Tried removing re-adding from the phone etc. All the normal stuff but not happy.
CAPsMAN device is a CCR running 6.39.2 and all the AP's are same version.
Any suggestions?
Cheers,
Dave _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, With a single AP it seems to have same issue even when standing metres from it - User adamant it works on all other WiFi networks (Maccas, home, etc) Without the ACL I get 4 way handshake timeout, with the ACL in accepting regardless of signal strength and AP/Client TX it's a received deauth message - When connected at even good RX signal strength it reports 1Mbp/s ingress/egress I guess just want to see if other people have had issues on Android 6 - It's got my buggered. Worth noting too had one of my colleagues in here with hie Android 6 phone and had same drama. Android 7 fine. The same colleague's phone works fine at our office with the same sort of CAPsMAN setup, all be it with considerably less APs. Cheers, Dave ________________________________ From: Public <public-bounces@talk.mikrotik.com.au> on behalf of Mike Everest <mike@duxtel.com> Sent: Wednesday, 14 June 2017 11:23:37 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] Mikrotik CAPsMAN Android Hi Dave, Logs? Wireless debug logs are usually quite helpful in these cases! Also, have you tried ruling out capsman as a contributor? (by manually configuring one AP and connect to it?) Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Wednesday, 14 June 2017 11:17 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] Mikrotik CAPsMAN Android
Hi All,
Have a 30 odd CAPsMAN deployment with the WAPac unit - It seems that Android v6 clients (to which we have 1) seem to have issues connecting. Spent a few hours on it today and if I set an ACL for the test phone I'm working with to Signal Range not set and AP/Client TX Limit to 0 it connects but bounces. It seems to prefer only want to connect to one access point which I cannot work out why - Tried removing re-adding from the phone etc. All the normal stuff but not happy.
CAPsMAN device is a CCR running 6.39.2 and all the AP's are same version.
Any suggestions?
Cheers,
Dave _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Dave, So you are relatively confident that it is repeatable with that particular version android? I'm reading your comments to say that AP reports client deauth request when the problem happens(?) in which case there is apparently something going on that the client doesn't like. Is there captive portal involved by any chance? Or some kind of DHCP issue? Something that definitely causes that kind of trouble from time to time is when a mobile device tries to test internet connectivity and when (the device thinks) interet connectivity is not there, will automatically (and often quietly) fall back to mobile network.. Could be something like that going on? Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Wednesday, 14 June 2017 11:43 AM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] Mikrotik CAPsMAN Android
Hi Mike,
With a single AP it seems to have same issue even when standing metres from it - User adamant it works on all other WiFi networks (Maccas, home, etc) Without the ACL I get 4 way handshake timeout, with the ACL in accepting regardless of signal strength and AP/Client TX it's a received deauth message - When connected at even good RX signal strength it reports 1Mbp/s ingress/egress
I guess just want to see if other people have had issues on Android 6 - It's got my buggered.
Worth noting too had one of my colleagues in here with hie Android 6 phone and had same drama. Android 7 fine. The same colleague's phone works fine at our office with the same sort of CAPsMAN setup, all be it with considerably less APs.
Cheers,
Dave
________________________________ From: Public <public-bounces@talk.mikrotik.com.au> on behalf of Mike Everest <mike@duxtel.com> Sent: Wednesday, 14 June 2017 11:23:37 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] Mikrotik CAPsMAN Android
Hi Dave,
Logs? Wireless debug logs are usually quite helpful in these cases!
Also, have you tried ruling out capsman as a contributor? (by manually configuring one AP and connect to it?)
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Wednesday, 14 June 2017 11:17 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] Mikrotik CAPsMAN Android
Hi All,
Have a 30 odd CAPsMAN deployment with the WAPac unit - It seems that Android v6 clients (to which we have 1) seem to have issues connecting. Spent a few hours on it today and if I set an ACL for the test phone I'm working with to Signal Range not set and AP/Client TX Limit to 0 it connects but bounces. It seems to prefer only want to connect to one access point which I cannot work out why - Tried removing re-adding from the phone etc. All the normal stuff but not happy.
CAPsMAN device is a CCR running 6.39.2 and all the AP's are same version.
Any suggestions?
Cheers,
Dave _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi Mike, Yes, it's repeatable with that version. No captive and DHCP seems fine from what I can see. Keen to see if other people are seeing this or it's some sort of weird anomaly. Not making a whole bunch of sense to me. The fact that we can be standing a metre from a wAP-AC, have great signal yet a relative speed of 1Mbp/s is odd. You're probably right in that the phone tests for internet, can't get there for whatever reason then just disconnects. Cheers, Dave
On 14 Jun 2017, at 12:21 pm, Mike Everest <mike@duxtel.com> wrote:
Hi Dave,
So you are relatively confident that it is repeatable with that particular version android? I'm reading your comments to say that AP reports client deauth request when the problem happens(?) in which case there is apparently something going on that the client doesn't like. Is there captive portal involved by any chance? Or some kind of DHCP issue? Something that definitely causes that kind of trouble from time to time is when a mobile device tries to test internet connectivity and when (the device thinks) interet connectivity is not there, will automatically (and often quietly) fall back to mobile network..
Could be something like that going on?
Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Wednesday, 14 June 2017 11:43 AM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] Mikrotik CAPsMAN Android
Hi Mike,
With a single AP it seems to have same issue even when standing metres from it - User adamant it works on all other WiFi networks (Maccas, home, etc) Without the ACL I get 4 way handshake timeout, with the ACL in accepting regardless of signal strength and AP/Client TX it's a received deauth message - When connected at even good RX signal strength it reports 1Mbp/s ingress/egress
I guess just want to see if other people have had issues on Android 6 - It's got my buggered.
Worth noting too had one of my colleagues in here with hie Android 6 phone and had same drama. Android 7 fine. The same colleague's phone works fine at our office with the same sort of CAPsMAN setup, all be it with considerably less APs.
Cheers,
Dave
________________________________ From: Public <public-bounces@talk.mikrotik.com.au> on behalf of Mike Everest <mike@duxtel.com> Sent: Wednesday, 14 June 2017 11:23:37 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] Mikrotik CAPsMAN Android
Hi Dave,
Logs? Wireless debug logs are usually quite helpful in these cases!
Also, have you tried ruling out capsman as a contributor? (by manually configuring one AP and connect to it?)
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Wednesday, 14 June 2017 11:17 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] Mikrotik CAPsMAN Android
Hi All,
Have a 30 odd CAPsMAN deployment with the WAPac unit - It seems that Android v6 clients (to which we have 1) seem to have issues connecting. Spent a few hours on it today and if I set an ACL for the test phone I'm working with to Signal Range not set and AP/Client TX Limit to 0 it connects but bounces. It seems to prefer only want to connect to one access point which I cannot work out why - Tried removing re-adding from the phone etc. All the normal stuff but not happy.
CAPsMAN device is a CCR running 6.39.2 and all the AP's are same version.
Any suggestions?
Cheers,
Dave _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
participants (2)
-
Dave Browning -
Mike Everest