I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS. Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs. When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration... When the WAPACS aren't working well on Wifi I can still connect in from the network side with Winbox and have no issues there. I've tried all sorts of things and am running out of options. Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au>
Hi Jason, I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them. It might be worth giving that a try.. Regards, Andrew On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from the network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Hi I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log. No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any. Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms. I'll try 6.40.1 tomorrow and turn off local forwarding and client to client. On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
-- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
I can add to this that we've generally seen CAPsMAN to be quite stable under bugfix except for two cases I'm aware of that so far are quite inexplicable. One of them is Jason's issue, and the other is a relatively large install of about 300 wAPs in an apartment building system. This other issue is possibly similar to what Jason is reporting - in this case at apparently random intervals, the CAPs Manager starts dropping CAP interfaces en-masse until they are all gone, and then immediately starts adding them again Since there are so many CAPs in this case, the whole process takes several minutes to complete with the end result being pretty much the same as what Jason's school scenario produces: clients lose connectivity for a few minutes, but stay connected to the wAP for the entire period. We are still working through the diagnostic options, but so far a solution has been a quite elusive :( I'll report back to this list if/when the solution arrives :-} Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Thursday, 10 August 2017 8:40 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] CAPSMAN WAPAC WIFI Failure
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.co m.au
-- <https://www.upandrunningtech.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
It's frustrating as I have a very similar system at another school that doesn't carry on like that. As for the apartment, I had a CAPSMAN system go up and down at a hotel in a similar way at regular intervals with all the CAPSMAN clients logging out and then coming back and booting the irate guests off. I replaced the legacy (a nice word for crummy) DLink and TPLink switches with Mikrotik and the problem went away. The TPLink was in the cellar on the same mains line as a whole bunch of fridges and perhaps it was either failing somehow or mains spikes from fridge motor stops and starts were upsetting it. I set the Mikrotik up with all the eth ports joined to a bridge (no master/slave) so I could try debug the problem or at least hope that the bridge system would clean up any bad frames but doing that alone seemed to resolve the issue. What is the make of the core switches? Are they running (R)STP? Jason On 10 August 2017 at 09:43, Mike Everest <mike@duxtel.com> wrote:
I can add to this that we've generally seen CAPsMAN to be quite stable under bugfix except for two cases I'm aware of that so far are quite inexplicable.
One of them is Jason's issue, and the other is a relatively large install of about 300 wAPs in an apartment building system. This other issue is possibly similar to what Jason is reporting - in this case at apparently random intervals, the CAPs Manager starts dropping CAP interfaces en-masse until they are all gone, and then immediately starts adding them again Since there are so many CAPs in this case, the whole process takes several minutes to complete with the end result being pretty much the same as what Jason's school scenario produces: clients lose connectivity for a few minutes, but stay connected to the wAP for the entire period.
We are still working through the diagnostic options, but so far a solution has been a quite elusive :(
I'll report back to this list if/when the solution arrives :-}
Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Thursday, 10 August 2017 8:40 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] CAPSMAN WAPAC WIFI Failure
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.co m.au
-- <https://www.upandrunningtech.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
Which bugfix version do you suggest? The current one or an older one? On 10 August 2017 at 09:43, Mike Everest <mike@duxtel.com> wrote:
I can add to this that we've generally seen CAPsMAN to be quite stable under bugfix except for two cases I'm aware of that so far are quite inexplicable.
One of them is Jason's issue, and the other is a relatively large install of about 300 wAPs in an apartment building system. This other issue is possibly similar to what Jason is reporting - in this case at apparently random intervals, the CAPs Manager starts dropping CAP interfaces en-masse until they are all gone, and then immediately starts adding them again Since there are so many CAPs in this case, the whole process takes several minutes to complete with the end result being pretty much the same as what Jason's school scenario produces: clients lose connectivity for a few minutes, but stay connected to the wAP for the entire period.
We are still working through the diagnostic options, but so far a solution has been a quite elusive :(
I'll report back to this list if/when the solution arrives :-}
Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Thursday, 10 August 2017 8:40 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] CAPSMAN WAPAC WIFI Failure
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.co m.au
-- <https://www.upandrunningtech.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
Official position is "the latest bugfix version" My personal opinion is 6.37.4 but don't tell anyone I said that (oops - too late! ;-) Cheers!
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Jason Hecker (Up & Running Tech) Sent: Thursday, 10 August 2017 10:02 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] CAPSMAN WAPAC WIFI Failure
Which bugfix version do you suggest? The current one or an older one?
On 10 August 2017 at 09:43, Mike Everest <mike@duxtel.com> wrote:
I can add to this that we've generally seen CAPsMAN to be quite stable under bugfix except for two cases I'm aware of that so far are quite inexplicable.
One of them is Jason's issue, and the other is a relatively large install of about 300 wAPs in an apartment building system. This other issue is possibly similar to what Jason is reporting - in this case at apparently random intervals, the CAPs Manager starts dropping CAP interfaces en-masse until they are all gone, and then immediately starts adding them again Since there are so many CAPs in this case, the whole process takes several minutes to complete with the end result being pretty much the same as what Jason's school scenario produces: clients lose connectivity for a few minutes, but stay connected to the wAP for the entire period.
We are still working through the diagnostic options, but so far a solution has been a quite elusive :(
I'll report back to this list if/when the solution arrives :-}
Cheers, Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Dave Browning Sent: Thursday, 10 August 2017 8:40 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] CAPSMAN WAPAC WIFI Failure
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikroti k.co m.au
-- <https://www.upandrunningtech.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.co m.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
-- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Dave and Andrew, What issues have you had with WAPACs? Jason On 10 August 2017 at 08:39, Dave Browning <dave@sentrian.com.au> wrote:
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) < jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk. mikrotik.com.au
-- <https://www.upandrunningtech.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
We have an install with around 230 wAP AC's on a single CAPSMAN, all SSID's use tuneled datapath. The issues we have had are: - ARP replies disappearing when using a tunneled datapath (Clients get a DHCP lease but are unreachable) This one still happens on 6.40.x - Irregular performance. Two laptops connected to the same AP on the same SSID, one will only be able to do 4mbit, the other will do a few hundred. Both have Intel 802.11ac wireless cards. - Prior to 6.40rc2 we had issues with mainly Apple iPhones and Samsung Galaxy J5's where they would be connected but would be unreachable. Dropping them off from Capsman, or restarting wireless fixed them. This seems to be fixed.. I am hoping Mikrotik can fix the ARP issue, and I am looking forward to the promised band-steering features :) On Thu, Aug 10, 2017 at 2:03 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote:
Dave and Andrew,
What issues have you had with WAPACs?
Jason
On 10 August 2017 at 08:39, Dave Browning <dave@sentrian.com.au> wrote:
I've had random issues with wAPAC's that rolling back to bug fix resolved. Can't name all the issues and not all issues resolved. But life is a bit happier on bugfix.
On 9 Aug 2017, at 9:19 pm, Jason Hecker (Up & Running Tech) < jason@upandrunningtech.com.au> wrote:
Hi
I am getting similar issues with 6.40 and 6.39.2. I wish Mikrotik would mention such major changes in the change log.
No (R)STP on any bridges, long guard interval, 1 hour group key timeout don't seem to help any.
Another school with Apple devices and a similar setup isn't having the same issue but their devices tend to stay in the rooms.
I'll try 6.40.1 tomorrow and turn off local forwarding and client to client.
On 9 August 2017 at 19:58, Andrew Thrift <andrew@networklabs.co.nz> wrote:
Hi Jason,
I have not seen that specific issue, but Mikrotik replaced the driver for the wAP AC and hAP AC in RouterOS 6.40. It fixed a few issues we were having on them.
It might be worth giving that a try..
Regards,
Andrew
I have a school site with CAPSMAN on an RB2011 controlling 7 WAPACS.
Local forwarding and client to client comms are used and the 5GHz band is pre-eminent as most of the devices are iPads and Macbook Airs.
When the class of students with their iPads move from one WAPAC to another Wifi connectivity seems to collapse on the adjacent WAPACS - no devices can communicate. Registration table shows they join but data doesn't flow very well if at all so DHCP fails etc. After 15-30 mins or a power cycle it all seems to settle down and things work again until the next migration...
When the WAPACS aren't working well on Wifi I can still connect in from
On Wed, Aug 9, 2017 at 8:14 PM, Jason Hecker (Up & Running Tech) <jason@upandrunningtech.com.au> wrote: the
network side with Winbox and have no issues there.
I've tried all sorts of things and am running out of options.
Has anyone else seen this sort of thing? -- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk. mikrotik.com.au
-- <https://www.upandrunningtech.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
-- <https://www.upandrunningtech.com.au> _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
participants (4)
-
Andrew Thrift -
Dave Browning -
Jason Hecker (Up & Running Tech) -
Mike Everest