GLI AX1800 Flint V4 Wireguard Server Issues

Technical Support for Routers VPN, DNS, Leaks
1

Hello Team,
GLI AX1800 Flint Devices when set as Wireguard Server, clients are not able to connect to the internet.
On the same network, when I use my old GLI AX1800 Flint running V3 , clients are able to connect to the internet.

On further investigation, I found out that On V4 the sysctl.conf is not auto populated

Can you please help here / assist further

@hansome @yuxin.zou @alzhao

2

What is firmware version of your Flint? It is 4.2.1?

3

Hi, what option should be in sysctl.conf?
What device do you use for the wireguard client?

4

Running version 4.1.0

5

Port forwarding shall be automatically selected and on on the sysctl.conf
I am using an I Phone, as mentioned above in the comments : When I use the GLI AX1800 Flint running V3 as WG server, the client can connect and access the internet but on GLI AX1800 running V4 and above it cannot

6

Did you run sysupgrade with keep setting? And from which version? Please make a backup of the config
http://192.168.8.1/cgi-bin/luci/admin/system/flash – Generate archive

and reset to factory and set up wireguard server again to see if it works.

7

This is a brand new router, and I was configuring a new Wireguard server.

8

Could you generate the config backup and export log(Admin panel - System - log) for analysis? Send to Email handongming#gl-inet.com

9

I have emailed the logs as requested

10

The mail was rejected, did you want me to send to : handongming@gl-inet.com

11

Yes, if it is always rejected, then try workspace4hdm@gmail.com

12

I don’t think sysctl.conf is the issue. I run f/w v 4.2.1 on my Slate AX & Flint:

root@GL-AXT1800:~# cat /etc/sysctl.conf
# Defaults are configured in /etc/sysctl.d/* and can be customized in this file

root@GL-AXT1800:~# wg show
interface: wgclient
  public key: [redacted]=
  private key: (hidden)
  listening port: 32

peer: [redacted]=
  endpoint: 37.19.211.7:51820
  allowed ips: 0.0.0.0/0
  latest handshake: 1 minute, 49 seconds ago
  transfer: 1.69 GiB received, 503.36 MiB sent
  persistent keepalive: every 25 seconds

(I would point out that, in WG, it is a misnomer to call it a ‘client/server’ architecture. It really is all just peer-to-peer but I agree w/ GL that it’s easier for people to understand client/server as if it was similar to OpenVPN.)

13

What about the firewall config?

14

What about it? That should be handled automatically by GL’s customizations. Others have successfully used the defaults to connect over disparate networks using f/w 4.2.1. See