Clients suddenly disconnect from Flint 2

Routers
1

Hi all, I have had my Flint 2 set up and configured for about a month now. I’ve tested it from different locations, everything has worked fine. However today the clients suddenly stopped connecting, despite the router being online. I have no idea why.

I tried to reconfigure the clients to see if that would help, but it didn’t work. Here’s the issue log:

Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section wgserver2ovpnclient option 'src' specifies invalid value 'wgserver'
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section wgserver2ovpnclient skipped due to invalid options
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section wgserver2wan option 'src' specifies invalid value 'wgserver'
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section wgserver2wan skipped due to invalid options
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section lan2wgserver option 'dest' specifies invalid value 'wgserver'
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section lan2wgserver skipped due to invalid options
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section nat6 option 'reload' is not supported by fw4
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section gls2s option 'reload' is not supported by fw4
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section gls2s specifies unreachable path '/var/etc/gls2s.include', ignoring section
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section glblock option 'reload' is not supported by fw4
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Section vpn_server_policy option 'reload' is not supported by fw4
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Automatically including '/usr/share/nftables.d/chain-pre/mangle_output/01-process_mark.nft'
Tue Feb 13 15:00:08 2024 daemon.notice netifd: wgclient (8209): [!] Automatically including '/usr/share/nftables.d/chain-post/mangle_output/out_conn_mark_restore.nft'
Tue Feb 13 15:00:09 2024 daemon.notice netifd: wgclient (8209): DROP all opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 match-set GL_MAC_BLOCK src
Tue Feb 13 15:00:10 2024 daemon.notice netifd: wgclient (8209): Failed to parse json data: unexpected character
Tue Feb 13 15:00:10 2024 daemon.notice netifd: wgclient (8209): uci: Entry not found
Tue Feb 13 15:00:10 2024 daemon.notice netifd: Interface 'wgclient' is now down
Tue Feb 13 15:00:10 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Tue Feb 13 15:00:12 2024 user.notice mwan3[8438]: Execute ifdown event on interface wgclient (unknown)
Tue Feb 13 15:00:14 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

Can anyone advise how to resolve? I have an international trip coming in just a couple days and this has to be resolved before I leave!

2

What version in use?

3

And what kind of VPN provider? Is the contract still active?

4

Im wondering if this is your issue, its worth the try to temporary disable client block list?, or mac vpn policies?

Maybe this rule is not restored as disabled, or a regression in the firmware maybe?, in luci you can see if it reflects a block in luci → firewall → traffic rules, you can also extra check the portforwards but i think its only in the traffic rules tab.