Reloading firewall due to ifdown of wgclient ()

Routers
1

MT3000 travel router

Wed Jul 23 16:19:04 2025 daemon.notice netifd: Network device 'wgclient' link is down
Wed Jul 23 16:19:04 2025 daemon.notice netifd: Interface 'wgclient' is now down
Wed Jul 23 16:19:04 2025 daemon.notice netifd: Interface 'wgclient' is setting up now
Wed Jul 23 16:19:04 2025 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

Running into this issue again... config file was working this morning, tested a different one and they all failed now, even the ones that were set up on my phone. I had this issue before and it was fixed by getting a new config file from the router server however I am now locked out of it until I get to remote access it again (later tonight)

3

Is there anything going on with the WAN-side of the device? netifd handles all network interfaces. What's the output of logger -e netifd & logger -e firewall?

/etc/init.d/network restart can manually trigger a restart... obviously.

4

Agree. It's necessary to ensure the connection status of your WAN - side network and check the log records.

Check whether the DNS on the device side resolves properly, and when you check the VPN server router next time, please confirm the VPN configuration again.

5

How do I go about looking that up? Sorry I'm a noob...

Server side router is an ASUS RT-AX58U. I had it working again after getting remote access to the server router, rebooting it and pulling a new config file (not sure if config file was even the issue but...). Started working again and now I got the same issue after stepping away for an hour

6

Jul 24 07:24:22 acsd: eth5: selected_chspec is 1002 (2)
Jul 24 07:24:22 acsd: eth5: Adjusted channel spec: 0x1002 (2)
Jul 24 07:24:22 acsd: eth5: selected channel spec: 0x1002 (2)
Jul 24 07:24:22 acsd: eth5: txop channel select: Performing CSA on chspec 0x1002
Jul 24 07:24:37 miniupnpd[2225]: upnp_event_process_notify: connect(IP address): Connection timed out
Jul 24 07:24:41 miniupnpd[2225]: upnp_event_process_notify: connect(IP address): Connection timed out
Jul 24 07:24:41 miniupnpd[2225]: upnpevents_processfds: 0x1680030, remove subscriber uuid:589e3690-da84-45e5-8a9b-264a41a35752 after an ERROR cb: http://IP address /upnp/eventing/udvehegnpc
Jul 24 07:27:58 dropbear[3317]: Login attempt for nonexistent user from IP address:35820
Jul 24 07:31:45 acsd: acs_candidate_score_intf(1083): eth6: intf check failed for chanspec: 0xe832
Jul 24 07:31:45 acsd: acs_candidate_score_bgnoise(1503): eth6: bgnoise check failed for chanspec: 0xe832
Jul 24 07:31:45 acsd: acs_candidate_score_txop(1761): eth6: txop check failed for chanspec: 0xe832
Jul 24 07:31:45 acsd: acs_candidate_score_intf(1083): eth6: intf check failed for chanspec: 0xe932
Jul 24 07:31:45 acsd: acs_candidate_score_bgnoise(1503): eth6: bgnoise check failed for chanspec: 0xe932
Jul 24 07:31:45 acsd: acs_candidate_score_txop(1761): eth6: txop check failed for chanspec: 0xe932
Jul 24 07:31:45 acsd: acs_candidate_score_intf(1083): eth6: intf check failed for chanspec: 0xea32
Jul 24 07:31:45 acsd: acs_candidate_score_bgnoise(1503): eth6: bgnoise check failed for chanspec: 0xea32
Jul 24 07:31:45 acsd: acs_candidate_score_txop(1761): eth6: txop check failed for chanspec: 0xea32
Jul 24 07:31:45 acsd: acs_candidate_score_intf(1083): eth6: intf check failed for chanspec: 0xeb32
Jul 24 07:31:45 acsd: acs_candidate_score_bgnoise(1503): eth6: bgnoise check failed for chanspec: 0xeb32
Jul 24 07:31:45 acsd: acs_candidate_score_txop(1761): eth6: txop check failed for chanspec: 0xeb32
Jul 24 07:47:09 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind mac address, status: 0, reason: Previous authentication no longer valid (2), rssi:-43
Jul 24 07:47:09 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind mac address, status: 0, reason: Disassociated due to inactivity (4), rssi:-43
Jul 24 07:52:54 acsd: eth5: selected_chspec is 1005 (5)
Jul 24 07:52:54 acsd: eth5: Adjusted channel spec: 0x1005 (5)
Jul 24 07:52:54 acsd: eth5: selected channel spec: 0x1005 (5)
Jul 24 07:52:54 acsd: eth5: txop channel select: Performing CSA on chspec 0x1005

This is the last 30min log from the router server side, I'm hoping I'm pulling the right log info

7

Well based on these latest logs I'm starting to suspect you might have a noisy environment to contend with. You should do a site survey to see what other AP's you're battling against & adjust settings in the GL GUI accordingly:

Those are executed while logged into your GL device over SSH. root is the username, same password as the GL GUI. ssh [email protected] would be the default connection. If you use Windows I'd install, use MobaXterm. It's free.