I thought had been true since at least version 3.30.
We get around it by using a bridge with a loopback address on it so we
can always get to a connected device.
This also resolves issues with the way MT returns SNMP requests and
RADIUS responses.
On 11/24/2014 4:30 PM, Matt Larsen - Lists wrote:
We have been doing some firmware upgrades on Mikrotiks from 5.26 to
6.22, and alarms start going off on a few of our locations. If we
have an AP that has no associations on it, you cannot ping the ip
address of the wireless card after upgrading to 6.22.
Is there a workaround for this? I have a few places where the alarms
are driving me crazy.
Matt Larsen
Vistabeam.com
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4223/8621 - Release Date: 11/24/14
--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration
Mikrotik Advanced Certified
www.nwwnet.net
(765) 855-1060 (765) 439-4253 Toll-free (855) 231-6239
_______________________________________________
Mikrotik mailing list
[email protected]
http://mail.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
