Beryl AX (GL-MT3000) suddenly unable to connect to VPN

Technical Support for Routers VPN, DNS, Leaks
1

Hello,

I have been using the Beryl AX (GL-MT3000) to connect to my home router via port forwarding for 2 days. It was working fine up until today, when I tried to connect it was unable to do so. Below is a copy of the log.

I then tried to connect the router to an OpenVPN Client using NordVPN and this is also not working, giving me a different set of errors. I have the log below as well.

Any and all help is appreciated. Thank you.

Port Forward
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Rule 'lan_in_conn_mark_restore'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Rule 'out_conn_mark_restore'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Zone 'lan'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Zone 'wan'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Zone 'guest'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Zone 'wgclient'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Set tcp_ecn to off
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Set tcp_syncookies to on
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Set tcp_window_scaling to on
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Running script '/etc/firewall.nat6'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Running script '/var/etc/gls2s.include'
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): ! Skipping due to path error: No such file or directory
Wed Jun 5 05:39:32 2024 daemon.notice netifd: wgclient (19564): * Running script '/usr/bin/gl_block.sh'
Wed Jun 5 05:39:33 2024 daemon.notice netifd: wgclient (19564): * Running script '/etc/firewall.vpn_server_policy.sh'
Wed Jun 5 05:39:33 2024 daemon.notice netifd: wgclient (19564): Failed to parse json data: unexpected character
Wed Jun 5 05:39:33 2024 daemon.notice netifd: wgclient (19564): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory
Wed Jun 5 05:39:33 2024 daemon.notice netifd: Interface 'wgclient' is now down
Wed Jun 5 05:39:33 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed Jun 5 05:39:33 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

VPN
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Populating IPv6 mangle table
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Rule 'process_mark'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Rule 'wan_in_conn_mark'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Rule 'lan_in_conn_mark_restore'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Rule 'out_conn_mark_restore'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Zone 'lan'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Zone 'wan'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Zone 'guest'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Zone 'ovpnclient'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Set tcp_ecn to off
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Set tcp_syncookies to on
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Set tcp_window_scaling to on
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Running script '/etc/firewall.nat6'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Running script '/var/etc/gls2s.include'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): ! Skipping due to path error: No such file or directory
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Running script '/usr/bin/gl_block.sh'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): * Running script '/etc/firewall.vpn_server_policy.sh'
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): Failed to parse json data: unexpected character
Wed Jun 5 05:45:01 2024 daemon.notice netifd: ovpnclient (23271): cat: can't open '/tmp/run/ovpn_resolved_ip': No such file or directory

2

Can you give me the log of ovpn?

The wireguard problem is generally the server side.

3

Hi alzhao, the ovpn log is below.

Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Populating IPv6 mangle table
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Rule 'process_mark'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Rule 'wan_in_conn_mark'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Rule 'lan_in_conn_mark_restore'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Rule 'out_conn_mark_restore'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Zone 'lan'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Zone 'wan'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Zone 'guest'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Zone 'ovpnclient'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Set tcp_ecn to off
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Set tcp_syncookies to on
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Set tcp_window_scaling to on
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Running script '/etc/firewall.nat6'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Running script '/var/etc/gls2s.include'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): ! Skipping due to path error: No such file or directory
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Running script '/usr/bin/gl_block.sh'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): * Running script '/etc/firewall.vpn_server_policy.sh'
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): Failed to parse json data: unexpected character
Wed Jun 5 06:31:20 2024 daemon.notice netifd: ovpnclient (21054): cat: can't open '/tmp/run/ovpn_resolved_ip': No such file or directory

4

There should be more log about ovpn. Can you check?

5

For nord ovpn pls check your credentials.

6

Thanks I think you're right and that this will be the issue. The log disappears so I can't send a full log.

If the wg is not a server issue do you have any ideas as to what these mean?

daemon.notice netifd: wgclient (30837): * Running script '/etc/firewall.nat6'
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): * Running script '/var/etc/gls2s.include'
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): ! Skipping due to path error: No such file or directory
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): * Running script '/usr/bin/gl_block.sh'
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): * Running script '/etc/firewall.vpn_server_policy.sh'
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): Failed to parse json data: unexpected character
Wed Jun 5 06:49:20 2024 daemon.notice netifd: wgclient (30837): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory

7

You can try the wireguard config on another device to see if it works.
If not work then it is server side issue.
If it works on another device, then could be issue of the client router.

You can just send you wireguad to me via message and I will test.

8

Confirming that it was a username and password login issue on NordVPNs side. Once I used the one provided via dashboard it worked.

9

As we talked via message, the Wireguard is server side problem. Maybe some network configuration changes. But it works now.

1 Like