Hallo everybody,
couple of mipsbe devices upgraded in a long-term line (i.e. from 6.44.6) with no issues encountered so far (IPv6, GRE tunnels over IPsec, OSPF v2 and v3, BGP, etc.). Thanks to Mikrotik for their work.

I believe that due to an old Linux kernel in RouterOS you cannot set an IPv6 route blackhole. The nearest workaround (which will do the same job well in many situations) is to set a route unreachable.

Hello,
I successfully operate GRE6 tunnels (i.e. tunnels between two public IPv6 addresses, Mikrotik router on both sides) secured with IPsec. That means IPsec between two IPv6 hosts is possible.
Regards.

I believe the reason for this is the old Linux kernel in RouterOS which does not support blackhole routes in IPv6. You might consider using unreachable routes as a workaround if this is an issue for you.

Couple of devices updated and so far so good ... (IPv6, OSPF v2 and v3, wifi 2GHz, 5GHz, VLAN, GRE/IPsec, VPN - SSTP, L2TP/IPsec, ...). Stability and "conservative" approach of the bugfix channel greatly appreciated. Thanks.

I upgraded a couple of devices (different types of mipsbe architecture) and encountered no problems (IPv4, IPv6, VPN servers - SSTP and L2TP/IPsec, wifi 2G and 5G, VLANs, GRE6/IPsec tunnels, OSPFv2/v3, ...). Bugfix releases seem pretty stable last time, the idea to separate development/current/bugfi...

Thanks alot for the swift reply! 24Mbit is sufficient for my needs. So I can use this board as a router/ipsec router providing VLANs and and wifi?

Definitely yes (and for many other tasks as well).

Hallo, I use a function human (see below) to convert integers into human-readable format (KiB, MiB, GiB) in a couple of my scripts. :local human do={ :local input $1; :local q; :local r; :local output; :if ($input<1024) do={:set output "$input B"} else={ :if ($input<1048576) do={:set q ($i...

Hi everybody,
yesterday I upgraded couple of mipsbe devices (IPv4/v6, VPN - SSTP, L2TP/IPsec, OpenVPN, GRE6/IPsec tunnels, PPPoE, OSPFv2/v3, wlan 2Ghz/5GHz, etc.). I did not encounter any problems so far (neither during upgrade nor during function). Thanks to developer!

Hello,
I believe the five numerical values in the log mean:
- session time in seconds,
- received bytes,
- transmitted bytes,
- received packets,
- transmitted packets.

Unfortunately, policy routing on IPv6 is not supported by the RouterOS at the moment.

Hello, I believe the answer to your question is to create a peer with address 0.0.0.0/0 (or ::/0). As far as I know (and my own setup shows) it catches every client address (consequently no dynamic peer is generated) and thus you have all the settings (cipher, hash strength, etc.) in your hands. Mor...

I share my hope in RouterOS 7 with ZeroByte. I expect IPv6 to be on the level similar to IPv4 - which would probably result also in the menu redesign (items like DNS, IPsec, etc. serve to both protocol versions equally). Next most desired feature for myself is IPv6 policy routing (I am really missin...

There is no answer/suggestion what to do yet, so I believe it's a bug in Router OS. In the meantime I checked with the current firmware release (6.34.2) - behaviour has not changed. It looks like the problem is not SSTP related only, exactly the same situation happens with L2TP (with or without IPse...

My setup for IPv6 tunnel is as follows (in fact it is for 6in4 tunnel, not 6to4, but MikroTik uses 6to4 interface for both). /interface 6to4 add !keepalive local-address=a.b.c.d mtu=1480 name=v6_tunnel remote-address=e.f.g.h /ipv6 address add address=2001:xxx:yyy:zzz::2 advertise=no interface=v6_tun...

I would like to ask the kind audience for a help. I have an RB2011 with FW 6.32.3 (last bugfix release). I have fully working IPv4 and IPv6 Internet connection and (I believe) well working SSTP server. Everything works great, there are no problems with connection from Windows 7/8.1/10 clients to VPN...