Disappointed that VPN client & server cannot be active together

[him]

I have encountered an issue with this beta for the flint in regards to Wireguard in the VPN Dashboard page, after I updated the server list to add addition countries from mullvad it shows the amber colour icon and the option to turn off/on and select a new server is missing, I will have to factory reset as I have no internet connectivity

Here is the log:

Wed May 25 17:25:18 2022 daemon.notice netifd: Interface 'wgclient' is now down
Wed May 25 17:25:18 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed May 25 17:25:19 2022 daemon.notice netifd: wgclient (29475): Error: any valid prefix is expected rather than "".
Wed May 25 17:25:19 2022 daemon.notice netifd: wgclient (29475): Line unrecognized: `PrivateKey='
Wed May 25 17:25:19 2022 daemon.notice netifd: wgclient (29475): Configuration parsing error
Wed May 25 17:25:24 2022 daemon.notice netifd: Interface 'wgclient' is now down
Wed May 25 17:25:24 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed May 25 17:25:25 2022 daemon.notice netifd: wgclient (29812): Error: any valid prefix is expected rather than "".
Wed May 25 17:25:25 2022 daemon.notice netifd: wgclient (29812): Line unrecognized: `PrivateKey='
Wed May 25 17:25:25 2022 daemon.notice netifd: wgclient (29812): Configuration parsing error
Wed May 25 17:25:30 2022 daemon.notice netifd: Interface 'wgclient' is now down
Wed May 25 17:25:30 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed May 25 17:25:31 2022 daemon.notice netifd: wgclient (30140): Error: any valid prefix is expected rather than "".
Wed May 25 17:25:31 2022 daemon.notice netifd: wgclient (30140): Line unrecognized: `PrivateKey='
Wed May 25 17:25:31 2022 daemon.notice netifd: wgclient (30140): Configuration parsing error
Wed May 25 17:25:36 2022 daemon.notice netifd: Interface 'wgclient' is now down
Wed May 25 17:25:36 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed May 25 17:25:37 2022 daemon.notice netifd: wgclient (30466): Error: any valid prefix is expected rather than "".
Wed May 25 17:25:37 2022 daemon.notice netifd: wgclient (30466): Line unrecognized: `PrivateKey='
Wed May 25 17:25:37 2022 daemon.notice netifd: wgclient (30466): Configuration parsing error

[Blobbie01]

The log makes it look like there’s just an error in the config. Try selecting another config to connect to

[him]

I am unable to connect to another config. I don’t know how to force stop it. So it is stuck at “The client is starting., please wait…”

[Blobbie01]

Try force closing wireguard through LuCi, that might work.

LuCi - System - Startup. Scroll down to the bottom and press stop on “wireguard”.

[alzhao]

Is the log for Mullvad? Or another config.

Seems the config file is crashed in format.

[him]

There is no “wireguard” option there. I see one for openvpn but no wireguard.

[him]

Where the amber message saying “The client is starting., please wait…” is, to the right I clicked on the “view log” option.

[lord]

Do I understand correctly that you cannot turn off AX for 2.4GHz in 4.0?

[alzhao]

AX is hardware. It is compatible with AC.

[lord]

I mean this:

This is screenshot from 3.x. But 4.x does not allow to set legacy modes without ax, so my old WiFi adapter without ac/ax cannot even discover it. It’s bug or what?

[alzhao]

@lord

so my old WiFi adapter without ac/ax cannot even discover it

It should discover. Maybe just channel issue? Can you change channel?

[lord]

Have tried different, no success. I ended up with buying a new adapter.

[Blobbie01]

There appears to be a bug with the Wireguard VPN status. After being connected a while (to WeVPN), the status changes to “vpn.client_starting”.

We’re still connected, and MyIP still shows the VPN IP, so does the WeVPN website, even after clearing cache & using a different browser. It appears to be just a bug with the status.

Stopping the core & starting again fixes it for a little while, but after a few hours the status changes to “vpn.client_starting” again.

[LLethur]

There seems to be a new GL-iNet Beta build out here. The ax1800.tar.gz file needs to be extracted fully. Have not tested it myself.

[Blobbie01]

@alzhao could you start pushing the V4 snapshot to the download center? Easier to keep an eye out there for new snapshot updates🙏

[alzhao]

Pls check now
https://dl.gl-inet.com/?model=ax1800&type=beta

[Blobbie01]

Perfect! Thank you very much🙏

[K3rn3l_Ku5h]

Your bandwidth should be set to 20ghz for legacy devices this should allow it to discover.

[Maximilious]

Implement the fixes posted here. I just implemented these and made an account to send kudos to the poster. It works as my PiHole DNS entries are working correctly now when connected to the router.

Wireguard client not honoring DNS setting [workaround discovered]

Update: now using dhcp.@dnsmasq[0].noresolv. A followup to my previous comment. I solved the issue in /etc/init.d/wireguard by checking if Stubby is enabled and if it is, removing the entry from the dnsmasq forwarders list and setting dhcp.@dnsmasq[0].noresolv=0 to force dnsmasq to use /tmp/resolv.conf.vpn. When disconnecting from the VPN I revert the DNS forwarder value back to the default Stubby forwarding address (127.0.0.1#53535) and revert back to dhcp.@dnsmasq[0].noresolv=1 to ignore /t…

[acw210ee]

Any update to fix the vpn policy based routing? I see there has been may updates to GL-AXT1800 Slate AX firmware but nothing for the flint in a while.