"stable" channel
Not only that but you cannot select bridge from the list because it's not there. Terminal command works so that's what I am going to use until WoL gets improved in WinBox.Make a correct WOL or remove it. Without hosts list it is useless.
Possibly because they could not reproduce. Did you open a support ticket?Why you don't fix OSPF ?
We have this strange OSPF problems too. Especially on large routers with many EPL circuits, with many Ethernet links and many GRE-links.Possibly because they could not reproduce. Did you open a support ticket?Why you don't fix OSPF ?
I just opened a ticket asking for tech support regarding wireless sudden re-associations of some of my devices, and I just saw this release. I am currently on long-term branch, but if you explain this wireless changes I may consider switching to stable. Working from home is a pain in the *** doing video calls and getting disconnected of the AP, even for juts 5 seconds.*) wireless - improved system stability on hAP ac^2;
Did it get worse than 6.46.5? Do you have problems with 6.46.5? All fixes are not for all, so it may be that there are changes that makes it better for others.Upgraded from 6.46.5 to 6.46.6 n so far I didnt see any better. Maybe need to wait for 6.46.7 for stability.
Some of my routers are HAP AC2. Not getting worse but not any better.Did it get worse than 6.46.5? Do you have problems with 6.46.5? All fixes are not for all, so it may be that there are changes that makes it better for others.Upgraded from 6.46.5 to 6.46.6 n so far I didnt see any better. Maybe need to wait for 6.46.7 for stability.
uptime: 1h33m5s
version: 6.46.6 (testing)
build-time: Apr/27/2020 10:32:16
...
we are using ospf, and mt ospf was always a little bit 'sensitive', special when u have a lot of interface changes because you have 'dynamic' interfaces inside the ospf - than it just stops working sometimes.We have this strange OSPF problems too. Especially on large routers with many EPL circuits, with many Ethernet links and many GRE-links.Possibly because they could not reproduce. Did you open a support ticket?Why you don't fix OSPF ?
This problem rise up at random, but I do not know how to reproduce it... It is appear after large scale carrier takes downtime and many links goes down\up at once. I think so, but I may be wrong...
Several members here note this problem from 6.44.6 till now...
We have no 6.44.5, but only 6.44.6 and older. All these verisons have up/down/init/extart problem. This problem solved only with full instance restart. Manual interface up/down does nothing.we are using ospf, and mt ospf was always a little bit 'sensitive', special when u have a lot of interface changes because you have 'dynamic' interfaces inside the ospf - than it just stops working sometimes.We have this strange OSPF problems too. Especially on large routers with many EPL circuits, with many Ethernet links and many GRE-links.Possibly because they could not reproduce. Did you open a support ticket?Why you don't fix OSPF ?
This problem rise up at random, but I do not know how to reproduce it... It is appear after large scale carrier takes downtime and many links goes down\up at once. I think so, but I may be wrong...
Several members here note this problem from 6.44.6 till now...
currently i'm chasing an ospf bug, where just the presence of an ospf-out filter breaks ecmp / cost calculation, but i don't know if this happened already in previous versions..
you mentioned that 'your problems' started with 6.44.6 - you mean the 'long term build' i guess, because that's the only one, where there were documented ospf-code changes.
please confirm, that you don't have ospf stability problems with 6.44.5 long term, or which was the last well-known-working version?
08:16:04 interface,info ether1 link down
08:16:04 dhcp,info dhcp-client on ether1 lost IP address 10.99.9.1 - lease stopped locally
08:16:15 interface,info ether1 link up (speed 100M, full duplex)
08:16:16 dhcp,info dhcp-client on ether1 got IP address 10.99.9.1
.
08:20:45 interface,info ether1 link down
08:20:45 dhcp,info dhcp-client on ether1 lost IP address 10.99.9.1 - lease stopped locally
08:20:56 interface,info ether1 link up (speed 100M, full duplex)
08:20:57 dhcp,info dhcp-client on ether1 got IP address 10.99.9.1
.
08:32:49 interface,info ether1 link down
08:32:49 dhcp,info dhcp-client on ether1 lost IP address 10.99.9.1 - lease stopped locally
08:32:59 interface,info ether1 link up (speed 100M, full duplex)
08:33:00 dhcp,info dhcp-client on ether1 got IP address 10.99.9.1
https://wiki.mikrotik.com/wiki/Manual:API#Initial_logini can use my api without any changes in v 6.43.16 or older.where can be the issue
I tested the long term version and the previous one and everything works without a problem. Only 6.46.6 makes problems.hAP ac^2 occasional loss of IP address after upgrade.
Z.
That problem is only in 6.47.rc60 all lower versions are OKDoes L2TP_IPSec now work?
I had to downgrade from 6.47.rc60 to 6.44.6 in order to find a version that would behave normally.
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?
The check for updates in winbox shows latest version 6.46.6 but in the lower left corner it says:What happens when you use the built-in "system->packages->check for updates" on CCR2004?
unfortuanelty very true, I tried via the product page myself too!arm64 build is missing, and CCR2004 product page incorrectly links to arm build
RouterOS ARM64 does not existThe check for updates in winbox shows latest version 6.46.6 but in the lower left corner it says:What happens when you use the built-in "system->packages->check for updates" on CCR2004?
ERROR: missing routeros-arm64-6.46.6.npk
I can nowhere find a newer arm64 OS than on the CCR2004 delivered 6.46.3!
Please HELP mikrotik!
No, I think he needs to wait until MikroTik have resolved this issue... apparently the build- and downloadsite environment does not support arm64 yet.RouterOS ARM64 does not existThe check for updates in winbox shows latest version 6.46.6 but in the lower left corner it says:What happens when you use the built-in "system->packages->check for updates" on CCR2004?
ERROR: missing routeros-arm64-6.46.6.npk
I can nowhere find a newer arm64 OS than on the CCR2004 delivered 6.46.3!
Please HELP mikrotik!
You need to download ARM version
I use 6.45.6 Stable for my hAP AC2 for months and works well.Hello,
I am new user of a hap ac^2, could you please tell me what version of OS I should use: 6.46.6 stable or 6.45.8 long term ?
Thank you,
IF
Because they really know if this release not really stable lolThis version shows up as "testing" in IP neighbor instead of stable. Both in winbox and CLI.
Screenshot from 2020-05-09 22-29-24.png
After disabling LCD and re-enabling it, it started to work again. Apparently a coincidental glitch.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?
If i downgrade the router to 6.45.9, i don't notice the problems anymore.*) system - improved system stability when forwarding traffic from switch chip to CPU (introduced in v6.43);
*) system - improved system stability when receiving/sending TCP traffic on multicore devices;
There is a whole thread about RB4011iGS reboots. I solved it by disabling time management (SNTP + Cloud time). Check out this topic: viewtopic.php?f=2&t=158939&e=1.Downgraded to 6.46.5 after seeing RB4011iGS+RM reboots without any entry in the log file or any external cause. Never seen on this device before.
For the v6.46.6 the date was "Tue Apr 28, 2020 1:03 pm", why re-released?Were v6.46.6 and 6.47beta53 re-released today? Why?
Just tested this on a CCR1009 and it works fine. You may want to open up a new forum thread, providing configuration of the bridge and interfaces.There is a bridge configured on CCR1036-12G-4S MikroTik Router. There are 9 ethernet interfaces in that bridge and one root port (that leads to Internet).
The bridge is in 255.255.255.0 network. It is possible to sent WOL Magic packet from router using tool wol mac=... command and the computer wakes up.
Using WOL software it is possible to wake the computer if both computers are on the same switch (connected to same ethernet port on MikroTik router).
But it is not possible to wake the computer if one computer is connected to one port and another computer is connected to another ethernet port.
Both ports are in the same network and in the same bridge. RSTP is enabled. ARP is enabled. Edge port is chacked and Edge Port Discovery is checked.
What could be the problem? And what would be the solution?
Thank you
I am one of those people, under specific circumstances - the helper is useful when individual phones are connected at the LAN side and the exchange is unable to deal with CPE-side NAT on its own. If the exchange is at the LAN side, whether the helper helps or causes trouble depends on the behaviour of that particular exchange.Some people recommend to turn this the SIP helper off.
The answer is right in the picture: the router is behind a NAT.Please Give Advice how to i make solve this issue
when i make connect ip cloud ... local ok .. but remotley showing time out
Could you kindly explain the wireless client association problme? I am running a problem where the wifi user frequently disassociated for 2 to 5 second. Is it problem with this 6.46.6? my device is rb1100.Some of my routers are HAP AC2. Not getting worse but not any better.Did it get worse than 6.46.5? Do you have problems with 6.46.5? All fixes are not for all, so it may be that there are changes that makes it better for others.Upgraded from 6.46.5 to 6.46.6 n so far I didnt see any better. Maybe need to wait for 6.46.7 for stability.
I can tell if 6.43.16 still faster n more stable than 6.44.6 to 6.46.6.
Problem? Yes.
1. Sometimes wireless G cant connect, while wireless N can always connect n working just fine. Mode bgn. 6.43.16 dont have this issue.
2. Some installation at office building with alot of noise, 6.43.16 perform better for 2.4ghz.
3. PPTP from android phone, will go disconnect in few mins. With 6.43.16, the same phone can connected for hours without any problem.
Most installation still with 6.43.16 n will stay at 6.43.16 until MT can make another real stable version.