I recently updated the firmware on my Beryl router to version 4.4.5 and I’m now having issues connecting it to my Wireguard VPN server. I’m getting the error "Error: "inet6 prefix is expected rather than "" when trying to connect.
This issue doesn’t happen on firmware version 4.2.3 - I downgraded to that and it connected to the Wireguard server normally. It seems to be something introduced in 4.4.5 that’s causing this problem.
Has anyone else seen this? I wanted to check if the developers are aware of this regression after the latest firmware update. If there’s a workaround I can use in the meantime, please let me know. Otherwise, I may stick to downgrading to 4.2.3 for now until this bug can get fixed.
Let me know if you need any other details about my setup. Thanks for any help you can provide!
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.
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 ()
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.
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…
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.
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
