RouterOS v6.27 released

On my OmniTIK UPA-5HnD I still get wrong health info on 6.27:

/system health> print
voltage: 21.8V
temperature: -23C

Now unless there’s an efficient freezer inside this is wrong. Outside temp is -5…

Most probably you have too old version to have this feature working :slight_smile: I found v6.7 in my network from that it worked fine. So you most probably need to upgrade … so that you can upgrade :slight_smile:

RouterOS v6 uses Linux Kernel 3.3.5. , if that motherboard have drivers for that Linux Kernel - probably you are fine, but only way to find for sure is to actually try. I myself waiting to ROuterOS v7 only to get all the good driver stuff that will come with new Linux Kernel

I’m pretty sure that 6to4 works, i use it a lot, maybe it is configuration error? or you have very very specific problems.if there would be mayor problem with 6to4 since 6.20 we would have s..t storm here in forum for sure. I suggest to open separate topic about this issue so we can give you a hand.

We already responded that this is not a bug that is easily fixable. This is one of fundamental flaws of the whole system, reason comes from kernel. If you have thousands of interfaces that are being listed, removing entries is very CPU intensive. We cannot fix it in RouterOS v6

I have a suggestion, though not sure it can be implemented. What if you add an option to just disable (and mark somehow) such interfaces instead of permanently deleting them from the list. And then reuse these interfaces for new PPPoE sessions later. Will this solve the original problem?

does RouterOS work on SATA 6gb/s?

Hi Normis,

system clock error in RouterOS v6.25 by x86!
It is synchronized with NTP-Servers unproblematic
But it works delayed in time (look on seconds).
we can’t upgrade our live system to v6.27 to test it.

we have tested v6.25 in RouterOS v6.25 by mipsbe, it works

for your reply thank you in advance
Regards,
paka

please explain more, what is wrong with seconds ?
can you post some image, or other details about this ?

here i have attached gif image, that shows difference system takt time between mipsbe and x86

Maybe Winbox is slow to give updates beause your router is 100% CPU loaded? What is the cause of CPU load ?

Just love how some questions just gets ignored…

100 % CPU load is since we have upgraded from v6.6 to v6.22.
The cause for that is bug :slight_smile:
see here http://forum.mikrotik.com/t/6-22-routeros-wireless-high-cpu-usage/83086/1

in v6.22 we had not problem with system time

Yes it works with 6gb/s ports
in motherboard GA-Z77MX-D3H with kingston V300 ssd

You say v6.22 but image shows v6.25, but this topic is actually about v6.27 …

we find that with the new ros versions after a day or two the ccq drops and the data across the links starts getting less till the router is rebooted then it is back to normal for the next two days
mostly we see this on the newer rbs
anybody else have this problem

What about Nstreme? When will it be fixed? (not polled for too long disconnections)

Is there any reasons not to fix this issue? As you can see in the picture, TCP traffic through the Ethernet interface shows over 80 percent more than the VLAN interface. UDP shows the correct speed on both interfaces and the issue appears only in the X86 version of RouterOS.

It depends on what kind of 6to4 you use. If it’s connection to tunnel broker (6to4 interface has remote-address set), then it works. But if it’s the automatic kind (no remote-address for 6to4 interface, address derived from IPv4 in 2002::/16 range and default route with gateway ::192.88.99.1%<6to4_interface_name>), then it does not. This is complete config. Since then, they fixed the first problem (“hop limit exceeded” for 2002::/16) in 6.24. But the second one (“no route to host” for everything else) persists. Last reply (“we will look into it”) from support is from 16th December, so I’m getting a little worried if the issue got lost in queue or something.

Normis, but the same packet loss occurs when one pppoe reach keepalive-timeout or only if removed from shell/gui by administrator?
In order to understand if in this case is better to restart pppoe-client on the CPE.

The limit of 1000 pppoe it’s valid on CCR1036 ?

Thank you