MV1000 WireGuard IPv6 traffic routing

lizh · 2021-07-30T03:21:47.747Z

Hi xyber，
I’m so sorry to have caused you trouble.I have verified a lot of tests and ‘the WAN port probability fails to obtain ipv6 after reboot,then WireGuard will not work propertly’.Thank you very much for your feedback.

Currently, we are actively optimizing ipv6 capabilities.This may take some time.

xyber · 2021-07-30T11:28:07.705Z

Hi Lizh,

I am actually no longer experiencing this issue. WG reconnects automatically now after I do a reboot. The WG connection also obtains both IPv4/6 addresses from my VPN provider and clients that tunnel through that also use the same IPv4/6 addresses.

However, please check my other post here. There is an IPV6 leak when using WG and when the MV1000 has both IPv4/6 WAN IPs from my ISP.

Thanks,

alzhao · 2021-07-31T03:41:14.734Z

xyber:

However, please check my other post here. There is an IPV6 leak when using WG and when the MV1000 has both IPv4/6 WAN IPs from my ISP.

Noticed and recorded in bug list.

mfld · 2021-08-02T02:43:11.623Z

How are you guys seeing IPv6 in Wireguard ? I just got my MV1000 and was about to ask support whats up with this when I found this thread.

I have the MV1000W with firmware 3.105.

I imported a wireguard client.conf that has two IP addresses, IPv4 and IPv6. Using them on Android, Linux or Windows the client will get the two addresses and route IPv6 over WG even if WAN has only IPv4.

On the MV1000W under VPN → WG → Interface → IP Address it has ignored all IPv6. If I add it manually, it fails “Invalid IP”.

I CAN set AllowedIPs to 0.0.0.0/0, ::/0 but if I put any IPv6 address into my interface address field, it will not accept it. I tried comma seperated and space separated addresses. Also tried IPv6 address only.

xyber · 2021-08-02T02:54:41.114Z

You would need to install firmware 3.203 for IPv6 to work with WG

mfld · 2021-08-02T03:09:10.934Z

Is that released already or do I need the beta4 from http://download.gl-inet.com/firmware/snapshots/3.203_beta4/mv1000-emmc/

xyber · 2021-08-02T03:47:11.875Z

Yes you need beta 4. You have the correct link

mfld · 2021-08-03T16:15:42.337Z

Cool I installed 3.203 beta4 and it does let me import a wg profile that is dual-stack but when I ssh into the device and check wg0 interface it only has IPv4 address. And I see npwhere to assign IPv6 ULA to the LAN. Do I need to toggle the global IPv6 switch on to make things work ? The IPv6 switch is off by default but it seems to talk only about IPv6 on WAN ? I want to have IPv4 WAN (hotel wifi) and have my LAN clients get IPv6 ULA or a /64 that comes in over the wg client.

Edit: This here gives an auto generated LAN ULA.

gli1869×1545 112 KB

But when I check ifconfig wg0 in SSH, the WG interface shows no IPv6 address which is weird because the profile and WG client settings in the UI clearly show there is a /128

xyber · 2021-08-05T00:34:59.624Z

Mine has an IPv6 address in ifconfig. Do you have an IPv6 address in the IP address fields of your WG setup?

mfld · 2021-08-05T01:18:30.157Z

Yes. The profile will be dual stack when I paste it into wireguard android or windows client.

It has a single public IPv4 /32 and IPv6 /128

xyber · 2021-08-05T02:00:35.074Z

So when you go on whatismyipaddress.com on a client you don’t see the VPN’s IP address either? Does your ISP provide you with an IPv6 address?

mfld · 2021-08-05T02:40:57.956Z

WAN is IPv4 only. WG client profile I put on the MV1000W is dual stack with a public IPv4 /32 and public IPv6 /128. From same WAN, same profile can be used on a Windows client or Anroid client and it functions as expected. When used on the MV1000W then the wg0 interface of the MV1000W shows the IPv4 address only. Clients onMV1000W LAN get normal 192.168.8.0/24 network and an IPv6 ULA. They can then only connect to the internet via IPv4, IPv6 times out. Globa IPv6 setting is set to NAT6 as in the screenshot I had there.

xyber · 2021-08-05T02:55:20.798Z

Your setup is the same as mine. I’m guessing your VPN provider/server is IPv4-only and is not giving your MV1000 an IPv6 address.

mfld · 2021-08-05T02:58:20.869Z

The provider is the ISP I am working at. We have full control. We own the IP space and it is giving me a functioning IPv6 /128. As stated the exact profile as I pasted it into the MV1000W will perform as normal if I plug it into Windows Wireguard client or import to Android.

I have VPN killswitch feature turned on. For testing I will factory reset, turn on IPv6, reimport the profile and not turn on the killswitch just to see if it will work. Might also try IPv6 only profile. Will report back.

xyber · 2021-08-05T02:59:33.671Z

In the WireGuard client screen of the GUI do you see an IPv6 address when you’re connected?

mfld · 2021-08-05T03:34:29.600Z

No. I see it in the GUI in the client settings I see IPv4/32,IPv6/128 and it has also taken my IPv6 DNS server thats in the WG profile. But in WG status part of GUI it shows connected IPv4 only and ifconfig wg0 shows IPv4 only.

If I SSH in, where is the wg0.conf located ? I did not see in /etc/
I am curious if maybe it did not import correctly because I imported when IPv6 global setting was still disabled. This may be why client config shows good in GUI but no IPv6 is applied!

Edit: Nope. The config is applied fine.

find / -name wireguard && find / -name wg0

I found /etc/config/wireguard and it has IPv4 and IPv6 separated by a comma in the Interface section. Looks correct.

xyber · 2021-08-05T03:38:44.527Z

There is a bug in the WireGuard client GUI where if you edit the parameters within the GUI for whatever reason it will copy the DNS server IP into the IP Address field of the WireGuard config. Check if that’s the case.

Because of this bug in the GUI whenever I need to edit the config I just delete the existing and edit the config in Notepad then paste it back into the GUI.

@alzhao You might wanna take a look at this one too and add it to the list for the developers

mfld · 2021-08-05T03:42:58.744Z

I removed the profile now via GUI. Then I imported a new client config, also known-good working. Also with a public ipv4/32 and ipv6/128. I encounter the same issue. This one I imported and connected without any editing. Still only seeing IPv4 address on wg0.

The MV1000W is awesome by the way. I found it by accident and will buy more now I found it when I got to a hotel that only had WiFi and I needed to connect a Netgate SG-1100. I have a crappy netgear repeater I normally use in this situation to catch public WiFi and get it into ethernet but for some reason it hates the Ruckus AP that this hotel have in production. I was about to try a different model netgear when I found the MV1000W. We have 5 people working remotely and they will all get an MV1000W now. It’s perfect for what we do.

xyber · 2021-08-05T03:56:58.764Z

Hmm… unfortunately there is nothing else I can think of. My WAN is setup as DHCP in the MV1000 and I have mine connected to my main Asus router (not my ISP’s modem). I have IPv6 disabled in my main router. The MV1000 gets both IPv4/6 addresses from my VPN provider and all clients connected to it can also use the VPN’s IPv4/6 addresses.

Have you tried to connect to your WG server through your phone or PC and see if you get an IPv6 address?

I bought the MV1000 because it is one of the few consumer-grade routers that support IPv6 over VPN. IPv6 addresses are less likely to be blocked by services online (for now).

mfld · 2021-08-05T23:43:13.452Z

xyber:

Have you tried to connect to your WG server through your phone or PC and see if you get an IPv6 address?

Yes. The profile I imported into the MV1000W works fine on Android and Windows, now tested on Linux, too. It will be fully functionial dual stack in all cases getting 20/20 in https://ipv6-test.com/

In the MV1000W it seems to ignore the IPv6 addresses altogether.