The correct md5sum for file all_packages-mipsbe-6.3.zip is, in fact, 54dcacfa0f027be8f21071ab21a46793 as it is stated on our website. Please use official sources for your upgrades.
Thanks.
In draws only 50 bars and then stops updating the histogram.
I prefer it that Bandwidth tests, pings, tracert, etc. time out after a while, but maybe 50 is to quick.
To many times did someone leave a test running and forgot about it.
*) pptp, l2tp, sstp - allow to specify server via dns name;
Please add OpenVPN to that list. Seriously, that’s just unfair for users.
pptp - insecure.
sstp - supported only in windows.
l2tp - requires ipsec+l2tp combo, hard to configure by user.
Viscosity on Mac and Windows can simply import config with one click. Same for “free” Mac OpenVPN client - Tunnelblick.
Same applies for Ubuntu with NetworkManager.
Not sure about “OpenVPN GUI” for windows.
So yeah, not a problem at all.
Cross-platform. Not SSTP. Btw yours SSTP implementation can connect only to Win and mikrotik based VPN servers, not to SoftEther)
Portable, by portable i mean it can be used on both 3G/4G networks. VPNs that was stable on 3G connection was PPTP (but unsecure) and OpenVPN.
Easy to configure. Not IPSec/L2TP, because installing strong/openswan and writing all configs… doh.
We have mixed environment (both win/lin/mac) in our office network, same for my home network.
IPSec/L2TP is fairly easy to configure. You have built-in (or easily installable) support for all the platforms (ex. Windows Phone). We have users using: OSX, Windows 7 and 8, Ubuntu/Mint, Android and iOS. All of them can use graphical tools to connect to VPN server.
Plain policy-based IPsec. With all the recently added features to support road-warrior configurations this is now my #1 choice to be used with Mikrotik.
Mikrotik still lacks some very-nice-to-have features like Split-DNS support (I only need server-side (i.e. mode-cfg) Split-DNS support, and it should be extremely easy to implement) and RADIUS integration, though. But what we have at the moment is already usable.
The problem with both WinBox and WebFig misreporting the IPsec SA expiration time is not fixed yet in 6.3. The reported value is a) incorrect and b) counts up (but should count down). Everything is fine on console, the “/ip ipsec installed-sa print” command reports correct value.
It was working just fine for me in 6.2, and works fine in 6.3 now. The only problem is that SA expiration time is misreported in WinBox and WebFig (see 2 posts above), but that is definitely not a show-stopper.