since there were no other big issues, we wanted to fix the health very badly 
zero bugs left
Normis, can you please look at these:
Ticket#2014122966000079
Ticket#2014120866000733
Ticket#2015020266000252
It was working fine, upgrading from 6.25 → 6.26 → 6.27.
After “/system package update check-for-updates without-paging” I’, getting following output (on several RBs, 951, 2011, 751)
current-version: 6.27
status: resolving upgrade.mikrotik.com
current-version: 6.27
latest-version: 6.27
status: System is already up to date
current-version: 6.27
latest-version: 6.27
status: System is already up to date … and so on
After “/system package update check-for-updates”, first I get
current-version: 6.27
status: resolving upgrade.mikrotik.com
– [Q quit|D dump|C-z pause]
then, after about 1,5 seconds i get:
current-version: 6.27
latest-version: 6.27
– [Q quit|D dump|C-z pause]
Some of my RouterBoards are connected to the internet via PPPoE (direct connection to the ADSL modem), and some are behind internet router, but all of them are using working DNS servers (some of them are querying 8.8.8.8 and 8.8.4.4, some of them query local LAN cacheing DNS).
Regards
You wish.
– Nathan
I wish it would be true.
@normis:
What about setting variable in script via SMS - multiple year bug?
http://forum.mikrotik.com/t/how-initialized-a-variable-by-sms/53857/1
Multiple support tickets created for this bug.
The first two are more feature requests than bugs. The latest is new, so not answered yet, but before our specialist has looked at it, it may be specific hardware problem or something else, not a bug for sure.
Ticket#2014122966000079
This is a bug with the route table not being available over SNMP.
How is that a feature request?
Ticket#2014120866000733
This is a bug with VirtualAP showing inside SNMP Station Interface table (mtxrWlStatEntry)
How is that a feature request?
Ticket#2015020266000252
Random packet-loss and port-flapping.
Its an issue, whether hardware or software (yes, not strictly a bug).
Auto upgrade still offer latest version - 6.25. Why?
upgrade.jpg
Can anyone comment if dynamic IPSec policies are being properly removed after disconnect/timeout in these newer versions?
See:
http://forum.mikrotik.com/t/6-10-dynamic-ipsec-policies-not-deleted-after-disconnect/75058/1
Hi ,
Im having a issue , I need to set up 25 new X86 boxes with RouterOS , having issue knowing what motherboards to get…your WIKI is VERY out of date , please can you provide a compatibility list…surely you want your client to know if your product would work?
Also does RouterOS work on SATA 6gb/s?
Does it work with Atheros GbE LAN chip (10/100/1000 Mbit)?
Is the Gigabyte GA-H77-DS3H board supported?
Thanks
Mikrotik totally ignore this bug. I think after some time they will say - “It’s not the bug. It’s the feature”.
It will be more like… “your ppoe sessions loose packets when you turn off one of them in sign of mourning, it’s not a bug it’s a non-documented feature”
If you’re out of big bugs, feel free to fix the smaller ones, like [Ticket#2014120466000688] (brokerless 6to4 is unusable starting from 6.20). I understand that it isn’t a highest priority one, as the user base is probably small. On the other hand, it’s been broken for almost half a year now. And in a way, it’s a dream bug, it’s reliably broken (on 6.27 too) and does not require any special effort to reproduce.
MikroTik 951G-2HnD.
RouterOS v6.23
RouterOS v6.27
Awesome improvement MikroTik!
For me it works faster…
305mbit to 345mbit…
Are you sure your speedtest.net server gives full speed?
yes, I am sure. Downgrade back to RouterOS 6.23, full speed again with same speedtest.net server.
What about Ticket#2015020466000267 ?
Constant reboots, was told it was a Winbox issue?? Upgraded to latest winbox 3RC4 and to v6.27 ROS, router still crashes once or twice per day (if twice, it’s within a few minutes of each other)
Efetuei o upgrade para a versão 6.27 em uma RB 750 e o processamento foi as alturas, ficando entre 90 e 100%, chegando travar e reiniciar. O que fiz para sanar o problema foi: fazer o downgrade para a versão 6.25 e voltou tudo ao normal, o processamento fico entre 9 e 12%. Outro detalhe que reparei foi, algumas páginas abriam, outras não, conferi se era problema de DNS, troquei vários DNS e o problema persistiu.
Então por enquanto o que mantive a solução foi voltar a versão 6.25.
This bug still not fixed in 6.27:
http://forum.mikrotik.com/t/bug-ssh-client-does-not-works-from-background-script/84475/1