Just tried without adblock or manual DNS, same error:
Thu Aug 24 19:32:03 2023 daemon.notice netifd: Interface 'wgclient' is setting up now Thu Aug 24 19:32:03 2023 daemon.notice netifd: wgclient (16825): Error: inet6 prefix is expected rather than "".
Also, I can connect to another Wireguard server, the problem is specific to a BRUME 2 Wireguard server, I just cannot connect from the Beryl to the Brume 2. I have other devices like iPhones with Wireguard configured and they all connect the Brume 2 just fine. Thanks.
Had same issue connecting to my pfsense using wire guard with slate 1800ax after 4.4.5 upgrade
Hello. I left it trying to connect to my Brume 2 again, here is the log:
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Rule 'out_conn_mark_restore'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Zone 'lan'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Zone 'wan'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Zone 'guest'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Zone 'tailscale'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Set tcp_ecn to off
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Set tcp_syncookies to on
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Set tcp_window_scaling to on
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Running script '/etc/firewall.nat6'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'
Sat Aug 26 12:17:53 2023 daemon.notice netifd: wgclient (427): * Running script '/etc/firewall.vpn_server_policy.sh'
Sat Aug 26 12:17:54 2023 daemon.notice netifd: wgclient (427): * Running script '/var/etc/gls2s.include'
Sat Aug 26 12:17:54 2023 daemon.notice netifd: wgclient (427): ! Skipping due to path error: No such file or directory
Sat Aug 26 12:17:54 2023 daemon.notice netifd: wgclient (427): * Running script '/usr/bin/gl_block.sh'
Sat Aug 26 12:17:54 2023 daemon.notice netifd: wgclient (427): RTNETLINK answers: No such process
Sat Aug 26 12:17:54 2023 daemon.notice netifd: Interface 'wgclient' is now down
Sat Aug 26 12:17:54 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sat Aug 26 12:17:54 2023 daemon.notice netifd: wgclient (538): Error: inet6 prefix is expected rather than "".
Sat Aug 26 12:17:54 2023 user.notice mwan3[537]: Execute ifdown event on interface wgclient (unknown)
Sat Aug 26 12:17:54 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Beryl CAN NOT do 4.5.5 firmware did you mean Beryl AX GL-MT3000.
Beryl GL-MT1300 can only do firmware Beta 4.3.7 release 1 or Snapshot 4.3.7
Hello.
Sorry if wasn’t specific, but I’m referring to the GL-MT3000 Beryl AX, that can run v4.4.5
Either way, I never had mentioned v4.5.5, just v4.4.5. I think there’s a nightly snapshot of v4.5, but never tried it.
Thanks.
I just tried connecting to Brume2 wireguard on MT3000, 4.4.5 and it connects.
Can you let me know how did you set up? Just put the wireguard config to MT3000? Did you do this before upgrade or after upgrade?
Can you check if the wireguard configure is complete after you put on MT3000?
Hello @alzhao, thanks for the reply. I had it working before the update, I’ve uploaded the config file generated from the Brume 2 to the MT3000, it worked flawlessly. Then I just updated to the latest FW, keeping settings, it stopped working, unfortunately. I also tried to remove and upload again the config file, a newly generated one, no luck. Thanks.
I going to say it may be the keep settings is causing it. If possible do a clean install then make changes or make a Backup config of the system and re-upload it after update.
Got it, sadly I have about 10 fixed IP leases, VPNs, DNS, DHCP, a lot of settings that I had changed for my needs. I’ll give a try as soon as I had the time. Thanks.
Can you send me your Wireguard that has problems to have a try? You can pm me or send via email.
Hello, thanks for the reply. Just tested @K3rn3l_Ku5h idea: backed up my current settings, performed a reset, connected the router to the internet, imported a just generated wireguard config file from the Brume 2 and it still doesn’t work…
This is the config file:
[Interface]
Address = 10.0.0.2/24
ListenPort = 52879
PrivateKey = {{REDACTED}}
DNS = 64.6.64.6
MTU = 1420
[Peer]
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = {{REDACTED}}:51820
PersistentKeepalive = 25
PublicKey = {{REDACTED}}
I can connect to the Brume 2 Wireguard server using all of my mobile phones successfully.
Thanks.
I wanted to follow up that the issue I was seeing with my Beryl router failing to connect to my Wireguard server after the 4.4.5 firmware update turned out to be due to a mistake in my network configuration.
After more troubleshooting, I realized the problem went away when I switched the Beryl’s internet connection method from repeater mode to USB tethering. This made me recognize the issue was with how I had the router set up on my network, not with the 4.4.5 firmware itself.
To be honest, I had no idea that having the Beryl in repeater mode could cause problems connecting to the VPN. I’m relieved to find the root cause and that there doesn’t seem to be a regression with Wireguard support in the latest update.
Thanks for the suggestions from those who replied. I’m happy I was able to get to the bottom of this and learn more about how network configurations can impact VPN connectivity. Please disregard my previous post reporting an issue - user error strikes again! Let me know if you have any other tips for a networking novice like me.
So is this problem solved? Sounds like everyone is still having the same issue
How can switching from repeater to USB mode fix the issue when you need repeater to connect to a WIFI network?
I believe the firmware 4.4.5 is working fine. The problem here was that the router was in repeater mode using the same internet (DHCP) from my Brume 2 (wireguard server). When I disabled the repeater and switched for the USB tether from my iPhone, Beryl got the WAN from the mobile phone, so it was not in the same network or using the same ISP as for the Brume 2 server.
I’m using the client server model, 1 MT1300 at home, and travel router 1800 abroad. All of the connection issues started when I upgraded the router. All of this was working a couple weeks ago… There seems to be no fix
The stability of wireguard server/client has degraded since the latest firmware patch. Now twice in one night I’ve had the connection go down.
running the server on MT1300, the client on Slate Plus
last logs:
Tue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Set tcp_syncookies to on\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Set tcp_window_scaling to on\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Running script '/etc/firewall.nat6'\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Running script '/etc/firewall.vpn_server_policy.sh'\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Running script '/var/etc/gls2s.include'\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): ! Skipping due to path error: No such file or directory\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): * Running script '/usr/bin/gl_block.sh'\nTue Aug 29 18:52:14 2023 daemon.notice netifd: wgclient (26849): uci: Entry not found\nTue Aug 29 18:52:14 2023 daemon.notice netifd: Network device 'wgclient' link is down\nTue Aug 29 18:52:15 2023 daemon.notice netifd: wgclient (26849): sh: 1: unknown operand\nTue Aug 29 18:52:19 2023 daemon.notice netifd: Interface 'wgclient' is now down\nTue Aug 29 18:52:19 2023 daemon.notice netifd: Interface 'wgclient' is setting up now\nTue Aug 29 18:52:19 2023 user.notice wgclient-up: env value:T_J_V_ifname=string J_V_address_external=1 USER=root ifname=wgclient ACTION=KEYPAIR-CREATED N_J_V_address_external=address-external SHLVL=2 J_V_keep=1 HOME=/ HOTPLUG_TYPE=wireguard T_J_V_interface=string J_V_ifname=wgclient T_J_V_link_up=boolean LOGNAME=root DEVICENAME= T_J_V_action=int TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin CONFIG_LIST_STATE= J_V_interface=wgclient K_J_V= action ifname link_up address_external keep interface J_V_link_up=1 J_V_action=0 T_J_V_address_external=boolean N_J_V_link_up=link-up T_J_V_keep=boolean PWD=/ JSON_CUR=J_V CONFIG_SECTIONS=global AzireVPN Mullvad FromApp group_9708 group_9027 group_1993 group_7245 peer_4335 CONFIG_cfg030f15_ports=\nTue Aug 29 18:52:19 2023 daemon.notice netifd: wgclient (27364): Error: inet6 prefix is expected rather than \"\".\nTue Aug 29 18:52:19 2023 kern.info kernel: [349871.377761] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED\nTue Aug 29 18:52:20 2023 user.notice mwan3[27363]: Execute ifdown event on interface wgclient (unknown)\nTue Aug 29 18:52:21 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()\nTue Aug 29 18:54:20 2023 kern.info kernel: [349992.209095] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED\nTue Aug 29 18:56:24 2023 kern.info kernel: [350115.643116] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED\n
Basically you need to connect to a different network (from the wireguard server network) to use the wireguard.