Still issues with NTP server names.
UI gives an error when entering a server name.
Doing this: “/system/ntp/client/set enabled=yes servers=us.pool.ntp.org” will work, but the Address field will be blank and the resolved-address will be correct.
After that, “/export” does not include the server.
Nobody appreciates that anymore, the whiners have moved on to requesting Wireguard…
And we got a Linux version that supports Wireguard. So endless whining is avoided.
RouterOS eight would not be there in my lifetime.
Anyone else having problems with the CCR1036-8G-2S+ USB port under 7.0b8?
I upgraded my CCR from 6.46.1 to get my Huawei 3372h-320 working (tested on a hAP ac). But on my CCR, the stick isn’t recognized. In fact, nothing is; nothing shows up in USB resources, whatever I connect to it (USB memory stick, Android phone, 4G stick). And nothing I connect to the USB port recognizes that there is anything at the other end (The Android phone doesn’t go into USB tethering for instance, which works fine in 6.46.1, and gives me a working ‘LTE’ interface).
It looks like it just delivers power (it does do that: the phone charges), but nothing else. I have opened a ticket with support, we’ll see what drops out.
RouterOS v6 runs on a Linux version that supports OpenVPN with UDP, and we all know what happened there…
“the Linux version supporting it” is amongst the many different points deciding if something is added to RouterOS.
That is why I think it is a good idea to allow for user code to run in a sandbox. So people can add what they need
even when MikroTik does not consider it to be worth it.
(of course this does not really work for every feature one can think of, but for some of them it would)
BTW the IMG file is also available, just don’t use the ISO for installation.
Finally i installed ros V7 Beta5 under barebone hardware with the help of Vmware workstation.The boot partition is 35MB now which is bigger than previous(upgraded from V6).Thanks for your help.
Can you please add the “rpfilter” matcher to the firewall matching rule options?
See http://forum.mikrotik.com/t/rpfilter-matcher-available/108064/1 and http://forum.mikrotik.com/t/unicast-reverse-path-forwarding/51618/1
Just to check. I have my interfaces detected and running well on 7beta5, but after upgrading to 7beta8, all interfaces gone from the list,
also… somehow I have to wait about 2 minutes before I can use the CLI after login.
Any information to solve this issue?
-Wenas
Same here，The onboard nic works well in beta5 but can not detected in beta 8. I add a connectx-4 lx card and found the system working slowly with 80% cpu usage.Reset configuration or reboot didi not solve the problem. I reinstall beta8 and boot from another motherboard and this time everyting is ok.But after that i added a switch and system became slow again with very hight CPU usage
Do you have any info on how to reinstall to Beta8, netinstall doesn’t work for me. ISO only 7beta5 is available.
What is not working with Netinstall? Any error?
I posted screenshot above…
Use Vmware Workstation to boot from 7beta5 iso. Mount the physical disk into vmware and install 7beta5 . Plug the disk to your x86 router and boot from it. Use the npk file to upgrade to 7beta8.
Vmware will solve the “can not find CD-ROM” error when you use the iso for installation
You can make your own 7beta8 ISO file , Just use the ULTRA ISO to edit the 7beta5 iso file and replace the routeros.npk in it with the routeros-x86-7.0beta8.npk (rename to routeros.npk)
On RB951G-2HnD running V7.0beta8, unable to successfully load a metarouter image.
Entered command response is as follows:
[admin@FasSat V3.05.03.U016] > /metarouter import-image file-name=openwrt-mr-mips-rootfs.v1.22.01.20200413.tar.gz
import failed: file in archive goes out of root directory: ./FasSat/
[admin@FasSat V3.05.03.U016] >
Should metarouter capability be available in V7, or is this error something unique to our metarouter image?
Is it Mikrotik’s intention to have this available when V7 is released for production usage?
We use this feature on 1600+ 951G2HnD devices with ROS 6.45.8 and do strongly prefer it to remain available.
hi, tried someone ros7.0b8 on CRS354 ?
possible fix for interfaces forwarding problem ?
http://forum.mikrotik.com/t/crs354-48p-4s-2q-traffic-problem-on-ports-1-to-8/139024/1
ROS 7.0beta8 contains problems with CAPsMAN (or with DHCP)!
Local WiFi interface (on same router) connected via CAPsMAN (in CAPsMAN forwarding mode) cannot deliver DHCP lease, error ocured:
03:01:08 dhcp,warning dhcp1-lan offering lease 192.168.101.253 for MAC-ADDRESS without success
There is no problems with same config on ROS 6.45.x
And because RBD53G-5HacD2HnD cannot be downgraded to 6.X - I am in really big trouble 
Any suggestions are welcome: how to avoid “lease without success” issue in CAPsMAN forwarding mode?
Update:
In case of CAPsMAN forwarding mode, dynamic cap port in the bridge appears without “Forwarding”. And probably this is the reason why DHCP are failing.
I try to set STP protocol to none, unfortunately same problem still exists - “Forwarding” not enabled, DHCP do not working.
Since RouterOS v6.43 it is possible to create a Private VLAN setup on CRS3xx series switches, example can be found in the Switch chip port isolation manual page.
Did some testing with BGP this evening. BGP does not work when a TCP MD5 key is specified. Removing the TCP MD5 key requirement from the remote peer allows BGP to connect.
When the TCP MD5 key is specified, there are no error messages on either end regarding an invalid key as would be expected.
This test was done on a hEX S router running ROS 7.0beta8 connecting to a production RB1200 running ROS 6.47.
Example config:
/routing bgp template
set default as=4274700001
/routing bgp connection
add connect=yes listen=yes local.role=ibgp remote.address=10.23.1.37 template=default tcp-md5-key=abc123
Mikrotik, with the new kernel do you think to make MPTCP available?