but keep in mind that you share your admin account with anyone on the internetIf you need anything MORE stable - go to Zyxel with their zyfwp.
avahi / mdns-reflection; I have to do this on a raspberry pi now. It's a necessary feature, if you separate your iot stuff from production networks.Which features are missing in your opinion?
It may worked like this in previous versions, but with 3.27 it opens up nothing.Session > new, opens up a new session, and will not save upon exit if it's not done manually.
Amazon Echo devices do this all the time.. At least 1.Gen ones that I have.It has been a long time since I saw a client that by default preferred 2.4 over 5 GHz connection.
Always set an admin mac address for bridges, or it will cause trouble sooner or later. Just my experience..rb4011igs. after update, bridge mac address changes non stop
my log filled withversion 6.44.6 don't have this problemCode: Select all
"bridge" mac address changed to xx:xx:xx:xx:xx:xx
For me it's working fine. Tested with 2 interfaces, timeout 10 seconds.It appears that the "interface slideshow" (configured in the interfaces screen under the LCD menu) on devices like the CCR1009 has stopped working in this release...
Anyone else who can confirm that?
32Bit: https://download.mikrotik.com/winbox/3.21/winbox.exeAnyone know where to find 3.21?
No memory leak here with a HAP AC2HAP AC2
After loading the router, 75 MB of memory is free, and after 4 days uptime, 55 MB of memory is free, I’ve cleaned the memory logs. Where did the memory leak?
@slackR Did you already open a ticket at Mikrotik Support?I can also confirm snmpv3 does not work in 6.45rc50 with Observium or snmpwalk.
Check System / ClockAnother "bug" from version to version, form stable to stable release
"Future" time on GRE tunnels in (up\down) status field
May be someone know how it resolve?
I doubt this is a software issue. Seems only one port is affected.After updating CCR1009 to 6.43 there is a problem with port stability! Has anyone else encountered such a problem?
Something must have been changed with ipsec processing in rc64. No traffic is passing through the tunnels.osc86, we are aware of the issue. It will be fixed until 6.43 is released in current release channel.
does this mean ipsec tunnels can be established between 2 sites with dynamic ip addresses, so I can get rid of the additional L2TP Tunnel?*) ipsec - allow to specify remote peer address as DNS name (CLI only);