After upgrading, I'm getting these: invalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c .. warnings. Not sure what to do about it, since it's the upstream gateway to the router and I have no control over it, and the interface is set to mtu 1500. Same here. I've been getting "radvd, ...

It's closed because they unable to reproduce it the ticket is SUP-78547

Hi,

any update?

Where can I track support tickets related to this bug? I could't find any here: https://help.mikrotik.com/servicedesk/s ... all&page=1

hap ac^2, hex r3 updated to 7.4beta2 – wireguard peers still cannot use IPv6 simultaneously, the bug is not fixed yet

No, nothing specific.

Good news, everyone!

Support answered that they were able to reproduce the issue and hopefully issue will be sorted shortly.

hex, hap ac^2 -- wireguard peers still cannot use IPv6 simultaneously on 7.3beta40, SUP-78547, viewtopic.php?p=933150, last working version is 7.1rc4 (downgrading from any version after to 7.1rc4 without touching the config)

updated to 7.3beta40 – wireguard peers still cannot use IPv6 simultaneously

Yes, it seems so. Same for me.

Sob, could you please test with two wireguard interfaces where the first one is default gateway and the second one is used for incoming connections? Please look into my first post.

I'm seeing the same issue on 7.3 beta 35. And no, that isn't a typo, I'm testing a private beta with support to iron out a CPU consumption bug. Have you heard anything back from support on your ticket? I'm unsure if opening my own ticket for this would be helpful since it seems like it would just b...

Same problem here, stucked in v7.1rc4
Could you try without any change with this version to confirm this issue ?

I’ve told that in the first post. From 7.1rc5 version concurrent ipv6 connectivity for wireguard peers stop working. Last working version for me is 7.1rc4.

Thank you Sob for this test. What I've done: netinstalled my hex with new 7.3beta33 and added this config (there is no firewall, just allowing peers to connect and run ping tests to local fd02:21::1 and 10.2.1.1): And still no IPv6 for peers simultaneously, only for one peer at the time, reentering ...

If you are sure it has nothing to do with the config itself

Export config.
Reset device to clean config
Reapply config being careful with what is already present as default.

Done this, even netinstalled. It does not work.

Added: on two devices: netinstall, no config, hap ac2 and hex.

any reason to you still be on 7.1rc4? this wireguard bug was introduced in this version (7.1rc4) and was fixed in the 7.2 stable and 7.1.3 stable. What's new in 7.2 (2022-Mar-31 12:11): ... *) wireguard - fixed IPv6 traffic processing with multiple peers; ... What's new in 7.1.3 (2022-Feb-11 21:20)...

There is no concurrent IPv6 connection for wireguard peers after 7.1rc4 routeros version, support ticket SUP-78547, tested on hap ac^2, hap ac and hex. While IPv4 for wireguard peers working as they should (peers are able to connect to each other, LAN and WAN via default route). You have to reenter ...

IPv6 traffic processing with multiple peers is not fixed, broken since 7.1rc4. Have to reenter allowed address to allow IPv6 but only for one peer. SUP-78547. Are you sure your config is correct? This was broken before for me aswell. But it has been working since some rc-versions now and still work...

*) wireguard - fixed IPv6 traffic processing with multiple peers;

IPv6 traffic processing with multiple peers is not fixed, broken since 7.1rc4. Have to reenter allowed address to allow IPv6 but only for one peer. SUP-78547.

he has two wireguard interfaces, one containing that peer with ::/0 and another interface with two other peers, they shouldn't interfere as long as he has proper routing for all that, which I didn't check.

please look into an export, i’ve included all the details

wireguard with ipv6 peers still doesn't work, you ought to reenter peer's ipv6 address (in allowed address) to allow ipv6 connection for that peer, meanwhile other peers loose ipv6 tested on 7.2rc5 hex and hap ac^2 # mar/24/2022 11:38:03 by RouterOS 7.2rc5 # software id = # # model = RouterBOARD 750...

still only one peer can use ipv6, not fixed Works for me. Please double check your configuration. /ipv6 address add address=fd02:28::1 interface=lo1 add address=fd02:29::1 interface=ep1 /ipv6 route add disabled=no distance=1 dst-address=/0 gateway=fd03:1337::1 scope=30 target-scope=10 add disabled=...

*) wireguard - fixed IPv6 traffic processing with multiple peers;

still only one peer can use ipv6, not fixed

viewtopic.php?t=179755#p887914

resolved after manually reentered peer allowed addresses via winbox

hap ac2, after upgrading to rc5 from rc4 wireguard peers lost ability to connect with ipv6, local clients can use ipv6 as before

after downgrading to rc4 with the same config everything run as it should be

I don't think you can do that. If you have some service running on router (e.g. WinBox on tcp/8291), it's listening on all addresses/interfaces. Even if you limit allowed client addresses in "/ip services", it won't allow you to connect from elsewhere, but port will still show as open fro...

You have some internal server with address 10.2.0.X and one or more dstnat rules to forward traffic from public address to 10.2.0.X, right? If so, you want dst-address=10.2.0.X in your last rule. If it does not help, post more info (exact dstnat rule(s), additional details about what exactly are yo...

Hello, I've got the same problem. I'd like to scan my mikrotik router's public IP. But every time I run nmap it shows open ports for lan, not the wan interface. Here is my ip firewall nat rules: chain=srcnat action=masquerade src-address-list=portlane out-interface=portlane chain=srcnat action=masqu...

Thank you!

Well I believe asking about eta of these functions to be implemented is no go

Hello there, I'm trying to setup my Mikrotik to be a client for ipredator.se. By going to this link https://ipredator.se/guide/openvpn/settings you could find general settings info. As for now Mikrotik doesn't support UDP transport in OpenVPN so I choose TCP and I believe other settings are compatib...