Hardware acceleration for ipv6 WireGuard

Routers VPN, DNS, Leaks
1

Hi, first post here, fresh owner of a flint 2, I hope I chose the right category.

I configured my flint 2 as a WireGuard client, pointing it at my WireGuard server via its static ipv6 address (since due to it not having a static ipv4 this is the only possible stable configuration).

After the 4.8.3 update the only way to make the tunnel work is to disable hardware acceleration, otherwise I get ~30% packet loss and very slow speeds.

The settings page says that HA doesn’t support vpn via ipv6, but given that it was working fine before the update I thought it was old info.

3

Hi

Thank you for your feedback.
We have also observed this issue during internal testing and are currently working on a resolution.

In the meantime, there are two available workarounds:

  1. As you mentioned, disable hardware acceleration.
  2. If you prefer to keep hardware acceleration enabled, please switch the IPv6 mode to NAT6.
4

Thank you very much, will try that now and report eventual findings.

Any ETA on the fix yet?

5

This issue is related to hardware acceleration within the MTK SDK.
Resolving it may require significant development effort, so no timeline for a fix is currently available.

6

Using nat6 fixed the issue, thanks again.

So I assume the issue is not present in the op24 branch of firmwares?

7

I'm not entirely sure if the open-source driver has the same issue or not, but it might be worth trying.