I had the same issue. After update from stable to v7.0b3 the CPU load on my RB951G-2HnD were hitting 100% without any reason. Downgrade back to stable version fixed the issue.

OK, I'll think about it. Thank you guys!

It seems my ISP is blocking port 80. I have changed port number and now all works fine! The problem is solved! Thanks to all!

Jotne, thanks, but I have already tried this and it's not working! Firewall shows no input packets when I'm trying to connect from WAN. Only LAN connection works fine. Any ideas why?

OK, here is my config in attachment. Please, help!

Config? Do you mean Supout.rif?

Hello! I need a remote acces to my router over Webfig. I have enabled DDNS in IP - Cloud. When I open http://XXXXXXXXXXXX.sn.mynetname.net/ in browser, it works fine, but only from my home network. From WAN it doesn't work! I have no firewall rules which may block remote access. I have also port 80 ...

Very disappointing news ;( I hoped there is a way to solve this problem in OpenVPN style. OpenVPN server pushes static routes to Mikrotik with no issues. But OVPN is too slow for me. SoftEther VPN is much better. But I should forget about split tunneling with it I guess ;( It's very sad. Thank you f...

Hello! I need help! I have rb951g-2hnd router and SoftEther VPN server, connected to my router over L2TP protocol. I want to config split tunneling with my VPN. I have configured dnsmasq on my VPN to push static routes with 121 option (for example: "dhcp-option=121,175.25.32.0/24,10.100.0.1&quo...

RafGan, thank you for posting this! I have mailed Mikrotik about this issue today, but have not received any answer from them by now. If so, I will not upgrade from rc56, until they add an option to disable this new "mega-useful" feature. It's very pity that they have broken a thing, which...

I have to stick with rc56 until DNS issue got fixed. Please, Mikrotik, we need a fix as soon as it possible!

Hi! I can confirm this issue too. I have choosen the simplest solution and have reverted back to v6.41rc56 which works fine. I hope this issue will be fixed in the next RC.