*) ovpn - added support for null crypto;
*) files - allow to remove empty disk folders;
*) sntp - fix problems with dns name resolving failures that were triggering
system watchdog timeout;
*) eoip/eoipv6/gre/gre6/ipip/ipipv6/6to4 tunnels have new features:
tunnels go down when no route to destination;
tunnels go down for 1 minute when transmit loop detected, warning gets logged;
new keepalive-retries setting;
keepalives enabled by default for new tunnels (10sec interval, 10 retries);
*) improved connection-state matcher in firewall - can match multiple states in one rule, supports negation;
*) added connection-nat-state matcher - can match connections that are srcnatted,dstnatted or both;
*) 100% CPU load caused by DNS service fixed;
*) 100% CPU load caused by unclassified services fixed;
*) 6to4 tunnel fixed;
*) new RouterBOOT firmware for Metal 2SHPn to improve wireless stability;
Click “Check for updates” in QuickSet or Packages menu to get the new version. This time, it should also work for v5 routers, please report if your device found the new release and how the update went.
We will try to fix torrent shortly. Thank you very much for the report.
Please report to this forum topic everything about 6.22 RouterOS version.
If you have specific reports about older versions, please contact us by support@mikrotik.com with detailed problem report. We will try to help you and solve your problem as soon as possible.
Thank you very much for the cooperation.
I have problems in address-lists and dhcp from 6.19 and all higher versions later. I submitted a report of the problem (Ticket#2014110466000984) to the v6.21.1. I tested the new version 6.22 right now and surprise: nothing has changed.
I have heard people talk here in “BugOS” to refer to “RouterOS” and tend to agree with them, unfortunately.
Ehm, no. As a brave man, I decided to try fresh ROS 6.22 on my home router (I often misuse it for various testing, its physical reachability is big advantage ). Same simple config as last time with 6.21.1. First impression was good, both routes were reported as reachable:
0 A S dst-address=2000::/3 gateway=::192.88.99.1%6to4 gateway-status=::192.88.99.1%6to4 reachable
distance=1 scope=30 target-scope=10
2 ADC dst-address=2002:d5d3:xxxx:80::/64 gateway=internal gateway-status=internal reachable
distance=0 scope=10Unfortunately, nothing was reachable from LAN. Why? Because no matter what I tried to connect to, router was returning ICMPv6 destination unreachable (type 1, code 0). Also all attempts to ping external IPv6 address directly from router failed with “no route to host”. So it says it has routes, but internally it does not seem to really have them.
I recreated the same config (only required bare minimum) on clean ROS 6.22 x86 VM just to be sure that it’s not influenced by something else on my router (I have a lot of stuff there). Exactly the same result. So welcome back, ROS 6.19. Looking forward to 6.23.
And with every release it is another part, That is my definition of beta. Wasted 4h yesterday with a problem where a
ethernet port did not work when removing it out of a bridge.
What about the new feature disk
From Winbox I do not see any drives. Looking on the Files menu I see a folder called Disk1.
How can I create folders on a drive for e.g. WebProxy or logging?
#WebProxy:
/ip proxy set cache-path=disk1/web-proxy1
#Logging:
/system logging action set disk disk-file-name=disk1/log
#User-Manager:
/tool user-manager database set db-path=disk1/user-manager
The ticket is still open and solution has not been found. Sergejs asked for logs and he is still looking into this problem. The issue will be solved, when ticket is closed, and you will be notified about this problem.
). Same