Gargoyle Forum

Posted: **Sun Feb 15, 2026 7:58 pm**

fifonik wrote: ↑
Sun Feb 15, 2026 7:25 am
Where can I get this information on router if I'm still on version 1.15.x_20250331?
Logread plugin is installed and it shows records for the last 20 hours right now.
However, there is nothing containing 'netifd', 'lease' or 'wan' in the system log right now.
Should I re-connect to ISP to get this info in system log?

P.S I'm on static external IP.

Try
ifstatus wan

At the bottom you’ll see data and leasetime.

If you’re not on a short lease, I’d be looking for other signs of wan up/down events that are shorter than 4 hours.

Posted: **Sun Feb 15, 2026 11:24 pm**

I do not have anything like this in the ifstatus output:
https://www.dropbox.com/scl/fo/669lvvz0 ... zplm9&dl=0

Posted: **Mon Feb 16, 2026 1:04 am**

Instead you might need to look in the logs for “pppd” (which handles your pppoe connection) to be making noise.

Posted: **Mon Feb 16, 2026 3:01 am**

coits wrote: ↑
Sun Feb 15, 2026 6:47 pm
Hi All,

Just want to mentioned using this released that when I enabled bandwidth monitoring, My internet connection is experiencing packet loss of around 40%-33% after 2-3 days, and it's not showing graph on the router gui.

To enable graph again, I manually run this command "/usr/lib/gargoyle/restart_firewall.sh" and all graph is showing and internet is back to normal, but after 2 days I will do it again.

Just want to check if anyone is experiencing this issue?

Thanks

Next time this happens can you capture a log please and also
nft list ruleset

Additional details about your connection type may be handy to understand why it’s falling over.

Posted: **Mon Feb 16, 2026 5:10 am**

Lantis wrote: ↑
Mon Feb 16, 2026 1:04 am
Instead you might need to look in the logs for “pppd” (which handles your pppoe connection) to be making noise.

Forced re-init, here what I have in system log (sorry, masked IP/MACs):

Code: Select all

Mon Feb 16 18:58:00 2026 daemon.err uhttpd[4816]: uci: Invalid argument
Mon Feb 16 18:58:01 2026 daemon.info dnsmasq[6521]: exiting on receipt of SIGTERM
Mon Feb 16 18:58:01 2026 daemon.notice netifd: Interface 'lan' is now down
Mon Feb 16 18:58:01 2026 daemon.notice hostapd: Set new config for phy phy1:
Mon Feb 16 18:58:01 2026 daemon.notice hostapd: Remove interface 'phy1'
Mon Feb 16 18:58:01 2026 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Mon Feb 16 18:58:01 2026 kern.warn kernel: [609134.591258] Ignoring NSS change in VHT Operating Mode Notification from xx:xx:xx:xx:xx:xx with invalid nss 2
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.279722] br-lan: port 9(phy1-ap1) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.295378] br-lan: port 8(phy0-ap1) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.301070] br-lan: port 7(phy0-ap0) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.306822] br-lan: port 6(phy1-ap0) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.312557] br-lan: port 5(lan5) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.317961] br-lan: port 4(lan4) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.323336] br-lan: port 1(lan1) entered disabled state
Mon Feb 16 18:58:01 2026 daemon.notice hostapd: phy1-ap1: AP-DISABLED
Mon Feb 16 18:58:01 2026 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.331483] device lan1 left promiscuous mode
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.336126] br-lan: port 1(lan1) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.514330] device phy1-ap1 left promiscuous mode
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.519126] br-lan: port 9(phy1-ap1) entered disabled state
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.594956] mt7530-mdio mdio-bus:1f lan1: Link is Down
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.602707] device lan2 left promiscuous mode
Mon Feb 16 18:58:01 2026 kern.info kernel: [615175.607241] br-lan: port 2(lan2) entered disabled state
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.690199] device lan3 left promiscuous mode
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.694806] br-lan: port 3(lan3) entered disabled state
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap1 from bridge br-lan: No such device
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.750018] device lan4 left promiscuous mode
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.754557] br-lan: port 4(lan4) entered disabled state
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.815750] mt7530-mdio mdio-bus:1f lan4: Link is Down
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.821672] device phy1-ap0 left promiscuous mode
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.826520] br-lan: port 6(phy1-ap0) entered disabled state
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.908222] device lan5 left promiscuous mode
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.912746] br-lan: port 5(lan5) entered disabled state
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.965938] mt7530-mdio mdio-bus:1f lan5: Link is Down
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.972447] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.984487] device phy0-ap0 left promiscuous mode
Mon Feb 16 18:58:02 2026 kern.info kernel: [615175.989314] br-lan: port 7(phy0-ap0) entered disabled state
Mon Feb 16 18:58:02 2026 kern.info kernel: [615176.063967] device phy0-ap1 left promiscuous mode
Mon Feb 16 18:58:02 2026 kern.info kernel: [615176.068781] br-lan: port 8(phy0-ap1) entered disabled state
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'lan' is disabled
Mon Feb 16 18:58:02 2026 daemon.notice netifd: bridge 'br-lan' link is down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'lan' has link connectivity loss
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'loopback' is now down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'loopback' is disabled
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network device 'lan1' link is down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network device 'lan4' link is down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network device 'lan5' link is down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network device 'eth0' link is down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan_6' is disabled
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network alias '' link is down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan_6' has link connectivity loss
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan6' is now down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan_6' is now down
Mon Feb 16 18:58:02 2026 daemon.info pppd[5903]: Terminating on signal 15
Mon Feb 16 18:58:02 2026 daemon.info pppd[5903]: Connect time 10263.5 minutes.
Mon Feb 16 18:58:02 2026 daemon.info pppd[5903]: Sent 1692648370 bytes, received 3492614983 bytes.
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network device 'pppoe-wan' link is down
Mon Feb 16 18:58:02 2026 daemon.notice pppd[5903]: Connection terminated.
Mon Feb 16 18:58:02 2026 daemon.info pppd[5903]: Connect time 10263.5 minutes.
Mon Feb 16 18:58:02 2026 daemon.info pppd[5903]: Sent 1692648370 bytes, received 3492614983 bytes.
Mon Feb 16 18:58:02 2026 daemon.info pppd[5903]: Exit.
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan' is now down
Mon Feb 16 18:58:02 2026 kern.info kernel: [615176.456624] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan' is disabled
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan6' is disabled
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: Set new config for phy phy0:
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: Remove interface 'phy0'
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: phy0-ap1: AP-DISABLED
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Network device 'eth1' link is down
Mon Feb 16 18:58:02 2026 daemon.notice hostapd: phy0-ap1: CTRL-EVENT-TERMINATING
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Feb 16 18:58:02 2026 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Feb 16 18:58:02 2026 daemon.notice wpa_supplicant[4134]: Set new config for phy phy1
Mon Feb 16 18:58:03 2026 daemon.notice netifd: Network device 'phy0-ap1' link is down
Mon Feb 16 18:58:03 2026 daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap1 from bridge br-lan: No such device
Mon Feb 16 18:58:03 2026 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:03 2026 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Mon Feb 16 18:58:03 2026 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Mon Feb 16 18:58:03 2026 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Mon Feb 16 18:58:03 2026 daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap0 from bridge br-lan: No such device
Mon Feb 16 18:58:03 2026 daemon.notice netifd: Network device 'phy0-ap0' link is down
Mon Feb 16 18:58:03 2026 daemon.notice wpa_supplicant[4134]: Set new config for phy phy0
Mon Feb 16 18:58:03 2026 daemon.notice netifd: Wireless device 'radio1' is now down
Mon Feb 16 18:58:03 2026 daemon.notice netifd: Wireless device 'radio0' is now down
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: bonding
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: 8021ad
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: 8021q
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: macvlan
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: veth
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: bridge
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: Network device
Mon Feb 16 18:58:04 2026 user.notice : Added device handler type: tunnel
Mon Feb 16 18:58:05 2026 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces?
Mon Feb 16 18:58:05 2026 kern.info kernel: [615178.980797] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615178.989320] device eth0 left promiscuous mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615178.989344] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Mon Feb 16 18:58:05 2026 kern.info kernel: [615178.994996] device eth0 entered promiscuous mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.007802] mt7530-mdio mdio-bus:1f lan1: configuring for phy/2500base-x link mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.062824] br-lan: port 1(lan1) entered blocking state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.068125] br-lan: port 1(lan1) entered disabled state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.074539] device lan1 entered promiscuous mode
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'lan' is enabled
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'lan' is setting up now
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'lan' is now up
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.088845] mt7530-mdio mdio-bus:1f lan2: configuring for phy/gmii link mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.098967] br-lan: port 2(lan2) entered blocking state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.104306] br-lan: port 2(lan2) entered disabled state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.111026] device lan2 entered promiscuous mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.122261] mt7530-mdio mdio-bus:1f lan3: configuring for phy/gmii link mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.132344] br-lan: port 3(lan3) entered blocking state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.137653] br-lan: port 3(lan3) entered disabled state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.144486] device lan3 entered promiscuous mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.155330] mt7530-mdio mdio-bus:1f lan4: configuring for phy/gmii link mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.165418] br-lan: port 4(lan4) entered blocking state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.170717] br-lan: port 4(lan4) entered disabled state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.177696] device lan4 entered promiscuous mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.188523] mt7530-mdio mdio-bus:1f lan5: configuring for phy/gmii link mode
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.198589] br-lan: port 5(lan5) entered blocking state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.203902] br-lan: port 5(lan5) entered disabled state
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.211040] device lan5 entered promiscuous mode
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'loopback' is enabled
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'loopback' is setting up now
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'loopback' is now up
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.502072] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:01] driver [RTL8221B-VB-CG 2.5Gbps PHY] (irq=62)
Mon Feb 16 18:58:05 2026 kern.info kernel: [615179.512386] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/sgmii link mode
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'wan' is enabled
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'wan6' is enabled
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Network device 'eth0' link is up
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Network device 'lo' link is up
Mon Feb 16 18:58:05 2026 daemon.notice netifd: Interface 'loopback' has link connectivity
Mon Feb 16 18:58:05 2026 daemon.notice netifd: radio0 (26443): WARNING: Variable 'data' does not exist or is not an array/object
Mon Feb 16 18:58:05 2026 daemon.notice netifd: radio1 (26444): WARNING: Variable 'data' does not exist or is not an array/object
Mon Feb 16 18:58:06 2026 daemon.notice hostapd: Set new config for phy phy0:
Mon Feb 16 18:58:06 2026 daemon.notice wpa_supplicant[4134]: Set new config for phy phy0
Mon Feb 16 18:58:06 2026 daemon.notice hostapd: Set new config for phy phy1:
Mon Feb 16 18:58:06 2026 daemon.notice wpa_supplicant[4134]: Set new config for phy phy1
Mon Feb 16 18:58:06 2026 daemon.notice wpa_supplicant[4134]: Set new config for phy phy0
Mon Feb 16 18:58:06 2026 daemon.notice wpa_supplicant[4134]: Set new config for phy phy1
Mon Feb 16 18:58:06 2026 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Mon Feb 16 18:58:06 2026 daemon.notice hostapd: Restart interface for phy phy0
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.051849] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mon Feb 16 18:58:06 2026 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=AU ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 chanlist=1 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmin=5 he_mu_edca_ac_vi_ecwmax=7 he_mu_edca_ac_vi_aif
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.157567] br-lan: port 6(phy0-ap0) entered blocking state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.163279] br-lan: port 6(phy0-ap0) entered disabled state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.169109] device phy0-ap0 entered promiscuous mode
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.174348] br-lan: port 6(phy0-ap0) entered blocking state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.180002] br-lan: port 6(phy0-ap0) entered forwarding state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.185957] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Mon Feb 16 18:58:06 2026 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Feb 16 18:58:06 2026 daemon.notice netifd: bridge 'br-lan' link is up
Mon Feb 16 18:58:06 2026 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Feb 16 18:58:06 2026 daemon.notice netifd: Network device 'phy0-ap0' link is up
Mon Feb 16 18:58:06 2026 user.info usteer: Creating local node hostapd.phy0-ap0
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.432907] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.533078] br-lan: port 7(phy0-ap1) entered blocking state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.538748] br-lan: port 7(phy0-ap1) entered disabled state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.544642] device phy0-ap1 entered promiscuous mode
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.551809] br-lan: port 7(phy0-ap1) entered blocking state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.557466] br-lan: port 7(phy0-ap1) entered forwarding state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.564510] device phy0-ap1 left promiscuous mode
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.569337] br-lan: port 7(phy0-ap1) entered disabled state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.642914] br-lan: port 7(phy0-ap1) entered blocking state
Mon Feb 16 18:58:06 2026 kern.info kernel: [615180.648569] br-lan: port 7(phy0-ap1) entered disabled state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.654377] device phy0-ap1 entered promiscuous mode
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.659481] br-lan: port 7(phy0-ap1) entered blocking state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.665131] br-lan: port 7(phy0-ap1) entered forwarding state
Mon Feb 16 18:58:07 2026 daemon.notice netifd: Network device 'phy0-ap1' link is up
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.671516] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap1: link becomes ready
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->ENABLED
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: phy0-ap0: AP-ENABLED
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: Set new config for phy phy1: /var/run/hostapd-phy1.conf
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: Restart interface for phy phy1
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.884103] mt7530-mdio mdio-bus:1f lan1: Link is Up - 2.5Gbps/Full - flow control rx/tx
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.884130] br-lan: port 1(lan1) entered blocking state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.897590] br-lan: port 1(lan1) entered forwarding state
Mon Feb 16 18:58:07 2026 daemon.notice netifd: Network device 'lan1' link is up
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=AU ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=149 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ac=1 vht_oper_chwidth=0 vht_oper_centr_freq_seg0_idx=151 vht_oper_centr_freq_seg1_idx= vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-4][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] ieee80211ax=1 he_oper_chwidth=0 he_oper_centr_freq_seg0_idx=151 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.929601] br-lan: port 8(phy1-ap0) entered blocking state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.935284] br-lan: port 8(phy1-ap0) entered disabled state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.941077] device phy1-ap0 entered promiscuous mode
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.946291] br-lan: port 8(phy1-ap0) entered blocking state
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: phy1-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.951945] br-lan: port 8(phy1-ap0) entered forwarding state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.959223] device phy1-ap0 left promiscuous mode
Mon Feb 16 18:58:07 2026 kern.info kernel: [615180.964118] br-lan: port 8(phy1-ap0) entered disabled state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.042550] br-lan: port 8(phy1-ap0) entered blocking state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.048219] br-lan: port 8(phy1-ap0) entered disabled state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.054043] device phy1-ap0 entered promiscuous mode
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.059151] br-lan: port 8(phy1-ap0) entered blocking state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.064810] br-lan: port 8(phy1-ap0) entered forwarding state
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.070739] br-lan: port 8(phy1-ap0) entered disabled state
Mon Feb 16 18:58:07 2026 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Mon Feb 16 18:58:07 2026 daemon.notice netifd: Wireless device 'radio0' is now up
Mon Feb 16 18:58:07 2026 user.info usteer: Found nl80211 phy on wdev hostapd.phy0-ap0, ssid=YuMiL
Mon Feb 16 18:58:07 2026 user.info usteer: Connecting to local node hostapd.phy0-ap0
Mon Feb 16 18:58:07 2026 user.info usteer: Creating local node hostapd.phy0-ap1
Mon Feb 16 18:58:07 2026 daemon.notice netifd: Wireless device 'radio1' is now up
Mon Feb 16 18:58:07 2026 user.info usteer: Found nl80211 phy on wdev hostapd.phy0-ap1, ssid=Guests
Mon Feb 16 18:58:07 2026 user.info usteer: Connecting to local node hostapd.phy0-ap1
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.600201] mt7530-mdio mdio-bus:1f lan5: Link is Up - 100Mbps/Full - flow control off
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.600220] br-lan: port 5(lan5) entered blocking state
Mon Feb 16 18:58:07 2026 daemon.notice netifd: Network device 'lan5' link is up
Mon Feb 16 18:58:07 2026 kern.info kernel: [615181.613508] br-lan: port 5(lan5) entered forwarding state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.012730] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.019507] br-lan: port 8(phy1-ap0) entered blocking state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.025162] br-lan: port 8(phy1-ap0) entered forwarding state
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Network device 'phy1-ap0' link is up
Mon Feb 16 18:58:08 2026 user.info usteer: Creating local node hostapd.phy1-ap0
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.152064] br-lan: port 9(phy1-ap1) entered blocking state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.157734] br-lan: port 9(phy1-ap1) entered disabled state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.160431] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.163582] device phy1-ap1 entered promiscuous mode
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.177155] br-lan: port 4(lan4) entered blocking state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.182493] br-lan: port 4(lan4) entered forwarding state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.190881] br-lan: port 9(phy1-ap1) entered blocking state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.196534] br-lan: port 9(phy1-ap1) entered forwarding state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.202834] device phy1-ap1 left promiscuous mode
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.207706] br-lan: port 9(phy1-ap1) entered disabled state
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Network device 'lan4' link is up
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.262133] br-lan: port 9(phy1-ap1) entered blocking state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.267796] br-lan: port 9(phy1-ap1) entered disabled state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.273683] device phy1-ap1 entered promiscuous mode
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.278850] br-lan: port 9(phy1-ap1) entered blocking state
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.284546] br-lan: port 9(phy1-ap1) entered forwarding state
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Network device 'phy1-ap1' link is up
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.292868] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap1: link becomes ready
Mon Feb 16 18:58:08 2026 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->ENABLED
Mon Feb 16 18:58:08 2026 daemon.notice hostapd: phy1-ap0: AP-ENABLED
Mon Feb 16 18:58:08 2026 user.info usteer: Found nl80211 phy on wdev hostapd.phy1-ap0, ssid=YuMiH
Mon Feb 16 18:58:08 2026 user.info usteer: Connecting to local node hostapd.phy1-ap0
Mon Feb 16 18:58:08 2026 user.info usteer: Creating local node hostapd.phy1-ap1
Mon Feb 16 18:58:08 2026 user.info usteer: Found nl80211 phy on wdev hostapd.phy1-ap1, ssid=Guests 5GHz
Mon Feb 16 18:58:08 2026 user.info usteer: Connecting to local node hostapd.phy1-ap1
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Network device 'eth1' link is up
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Interface 'wan' is setting up now
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Feb 16 18:58:08 2026 daemon.notice netifd: Interface 'wan6' is now up
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.613005] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Feb 16 18:58:08 2026 kern.info kernel: [615182.613020] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Mon Feb 16 18:58:08 2026 daemon.info pppd[27165]: Plugin pppoe.so loaded.
Mon Feb 16 18:58:08 2026 daemon.info pppd[27165]: PPPoE plugin from pppd 2.4.9
Mon Feb 16 18:58:09 2026 daemon.notice pppd[27165]: pppd 2.4.9 started by root, uid 0
Mon Feb 16 18:58:09 2026 daemon.info pppd[27165]: PPP session is 25267
Mon Feb 16 18:58:09 2026 daemon.warn pppd[27165]: Connected to xx:xx:xx:xx:xx:xx via interface eth1
Mon Feb 16 18:58:09 2026 kern.info kernel: [615183.120957] pppoe-wan: renamed from ppp0
Mon Feb 16 18:58:09 2026 daemon.info pppd[27165]: Renamed interface ppp0 to pppoe-wan
Mon Feb 16 18:58:09 2026 daemon.info pppd[27165]: Using interface pppoe-wan
Mon Feb 16 18:58:09 2026 daemon.notice pppd[27165]: Connect: pppoe-wan <--> eth1
Mon Feb 16 18:58:10 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Mon Feb 16 18:58:10 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Mon Feb 16 18:58:11 2026 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=sae
Mon Feb 16 18:58:11 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 9B696F283FBE6E88
Mon Feb 16 18:58:11 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Mon Feb 16 18:58:11 2026 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:16 2026 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Feb 16 18:58:16 2026 daemon.err uhttpd[4816]: udhcpc: started, v1.36.1
Mon Feb 16 18:58:16 2026 daemon.err uhttpd[4816]: udhcpc: broadcasting discover
Mon Feb 16 18:58:19 2026 daemon.err uhttpd[4816]: udhcpc: no lease, failing
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: started, version 2.90 cachesize 1000
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: DNS service limited to local subnets
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: UBus support enabled: connected to system bus
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq-dhcp[28224]: DHCP, IP range 192.168.1.100 -- 192.168.1.199, lease time 6h
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for test
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for onion
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for localhost
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for local
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for invalid
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for bind
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for lan
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using nameserver 1.0.0.1#53
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using nameserver 58.96.3.34#53
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for test
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for onion
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for localhost
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for local
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for invalid
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for bind
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for lan
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: read /etc/hosts - 10 names
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: read /plugin_root/adblock/block.hosts - 14723 names
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq[28224]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Mon Feb 16 18:58:19 2026 daemon.err uhttpd[4816]: sh: write error: Broken pipe
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq-dhcp[28224]: DHCPDISCOVER(br-lan) xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq-dhcp[28224]: DHCPOFFER(br-lan) 192.168.1.58 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq-dhcp[28224]: DHCPREQUEST(br-lan) 192.168.1.58 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:19 2026 daemon.info dnsmasq-dhcp[28224]: DHCPACK(br-lan) 192.168.1.58 xx:xx:xx:xx:xx:xx Pixel-7a
Mon Feb 16 18:58:19 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Mon Feb 16 18:58:20 2026 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=sae
Mon Feb 16 18:58:20 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 5A6D52AA6E88B636
Mon Feb 16 18:58:20 2026 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Mon Feb 16 18:58:20 2026 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:20 2026 daemon.info pppd[27165]: CHAP authentication succeeded
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: CHAP authentication succeeded
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: peer from calling number xx:xx:xx:xx:xx:xx authorized
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: local  IP address xx.xx.xx.xx
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: remote IP address xx.xx.xx.xx
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: primary   DNS address xx.xx.xx.xx
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: secondary DNS address xx.xx.xx.xx
Mon Feb 16 18:58:20 2026 daemon.notice netifd: Network device 'pppoe-wan' link is up
Mon Feb 16 18:58:20 2026 daemon.notice netifd: Interface 'wan' is now up
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using nameserver 1.0.0.1#53
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using nameserver 58.96.3.34#53
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using nameserver 1.0.0.1#53
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using nameserver 58.96.3.34#53
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for test
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for onion
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for localhost
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for local
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for invalid
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for bind
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq[28224]: using only locally-known addresses for lan
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: local  LL address fe80::b857:0b75:8a3a:616e
Mon Feb 16 18:58:20 2026 daemon.notice pppd[27165]: remote LL address fe80::e804:feff:fee3:4029
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq-dhcp[28224]: DHCPDISCOVER(br-lan) xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq-dhcp[28224]: DHCPOFFER(br-lan) 192.168.1.23 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq-dhcp[28224]: DHCPREQUEST(br-lan) 192.168.1.23 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:20 2026 daemon.info dnsmasq-dhcp[28224]: DHCPACK(br-lan) 192.168.1.23 xx:xx:xx:xx:xx:xx Pixel-7
Mon Feb 16 18:58:22 2026 daemon.info dnsmasq-dhcp[28224]: DHCPREQUEST(br-lan) 192.168.1.40 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:22 2026 daemon.info dnsmasq-dhcp[28224]: DHCPACK(br-lan) 192.168.1.40 xx:xx:xx:xx:xx:xx Babushka
Mon Feb 16 18:58:29 2026 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Mon Feb 16 18:58:29 2026 daemon.notice netifd: Interface 'wan_6' is enabled
Mon Feb 16 18:58:29 2026 daemon.notice netifd: Interface 'wan_6' has link connectivity
Mon Feb 16 18:58:29 2026 daemon.notice netifd: Interface 'wan_6' is setting up now
Mon Feb 16 18:58:37 2026 daemon.info dnsmasq-dhcp[28224]: DHCPDISCOVER(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:37 2026 daemon.info dnsmasq-dhcp[28224]: DHCPOFFER(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:37 2026 daemon.info dnsmasq-dhcp[28224]: DHCPREQUEST(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:37 2026 daemon.info dnsmasq-dhcp[28224]: DHCPACK(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx ATA-HT802
Mon Feb 16 18:58:47 2026 daemon.info dnsmasq-dhcp[28224]: DHCPDISCOVER(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:47 2026 daemon.info dnsmasq-dhcp[28224]: DHCPOFFER(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:47 2026 daemon.info dnsmasq-dhcp[28224]: DHCPREQUEST(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx
Mon Feb 16 18:58:47 2026 daemon.info dnsmasq-dhcp[28224]: DHCPACK(br-lan) 192.168.1.248 xx:xx:xx:xx:xx:xx ATA-HT802
Mon Feb 16 18:58:56 2026 user.notice firewall: Reloading firewall due to ifup of wan6 (eth1)
Mon Feb 16 18:59:07 2026 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)

I do not see anything related to external lease. Also, normally in log I do not have anything related to firewall loading.

P.S. Will try to flash without preserving settings on Wednesday.

Posted: **Mon Feb 16, 2026 5:38 am**

I note that you have no messages about the Gargoyle firewall initialising…
https://github.com/ericpaulbishop/gargo ... ll.hotplug

I’m a bit lost why hotplug isn’t triggering here

Posted: **Tue Feb 17, 2026 5:29 am**

Lantis wrote: ↑
Mon Feb 16, 2026 3:01 am

coits wrote: ↑
Sun Feb 15, 2026 6:47 pm
Hi All,

Just want to mentioned using this released that when I enabled bandwidth monitoring, My internet connection is experiencing packet loss of around 40%-33% after 2-3 days, and it's not showing graph on the router gui.

To enable graph again, I manually run this command "/usr/lib/gargoyle/restart_firewall.sh" and all graph is showing and internet is back to normal, but after 2 days I will do it again.

Just want to check if anyone is experiencing this issue?

Thanks
Next time this happens can you capture a log please and also
nft list ruleset

Additional details about your connection type may be handy to understand why it’s falling over.

I just notice this time that I have 44% to 35% packet loss,
I have disabled bandwidth monitoring and uhttpd since the last time it happen.
I have resolve the issue by running this script again "/usr/lib/gargoyle/restart_firewall.sh" and ping ping response is back to 12ms.

I am using cable internet, no unusual errors on the logs.

please see my ping response on the router.
===================================
64 bytes from 142.250.73.131: seq=275 ttl=117 time=707.483 ms
64 bytes from 142.250.73.131: seq=276 ttl=117 time=652.215 ms
64 bytes from 142.250.73.131: seq=277 ttl=117 time=686.758 ms
===================================

Thanks

Posted: **Tue Feb 17, 2026 6:02 am**

Sorry if I wasn’t clear, I need to see an “nft list ruleset” while you are experiencing the issue, I’m trying to see if the rules are not asserting correctly in the firewall.

Posted: **Tue Feb 17, 2026 7:02 pm**

I've just flashed the FW without preserving settings and only made the following changes:
- password/timezone on first login;
- System | Identification: name & domain, Save;
- Connection | Basic: pppoe (login & password), disabled 'connect via', ticked 'drop ping from WAN', added custom DNS servers (1.0.0.1 + one from ISP), Save;
- System | Time: set time format as 'dd/mm/yyyy' and selected '24 hour' format;
- Connection | DHCP: in ipv6 section set all dropdowns as 'disabled', in ipv4 ection set DHCP end range to 240, Save;
- System | Plugins: added plugin URLs and installed a few plugins (adblock, service manager, logread, wifi scanner full);
- System | Services: disabled 'minidlna', 'openvpn', 'p910nd', Save;
- Restart;

Unfortunately, the downloads are still displayed as zeroes in table and graphs (as in my original report when I preserved settings: viewtopic.php?p=67633#p67633).
Hostname and IP items in graphs dropdowns also instantly changing to 'None' as in my original report.
In addition I've noticed that on Status | Overview page 'WAN (PPPoE) Uptime' is displayed as 'Disabled', while internet connection is working (in previous version PPPoE up time displayed here).

I copied log and screenshots of 'Status | Overview' & 'Status | Connection' pages. Can supply if required (I can email it to you as is or post in the forum masking IP/MACs).

Reverted to 1.15.X (Built 20250330-2253 git@ca9ca6a5).

Posted: **Wed Feb 18, 2026 8:49 am**

fifonik wrote: ↑
Tue Feb 17, 2026 7:02 pm
I've just flashed the FW without preserving settings and only made the following changes:
- password/timezone on first login;
- System | Identification: name & domain, Save;
- Connection | Basic: pppoe (login & password), disabled 'connect via', ticked 'drop ping from WAN', added custom DNS servers (1.0.0.1 + one from ISP), Save;
- System | Time: set time format as 'dd/mm/yyyy' and selected '24 hour' format;
- Connection | DHCP: in ipv6 section set all dropdowns as 'disabled', in ipv4 ection set DHCP end range to 240, Save;
- System | Plugins: added plugin URLs and installed a few plugins (adblock, service manager, logread, wifi scanner full);
- System | Services: disabled 'minidlna', 'openvpn', 'p910nd', Save;
- Restart;

Unfortunately, the downloads are still displayed as zeroes in table and graphs (as in my original report when I preserved settings: viewtopic.php?p=67633#p67633).
Hostname and IP items in graphs dropdowns also instantly changing to 'None' as in my original report.
In addition I've noticed that on Status | Overview page 'WAN (PPPoE) Uptime' is displayed as 'Disabled', while internet connection is working (in previous version PPPoE up time displayed here).

I copied log and screenshots of 'Status | Overview' & 'Status | Connection' pages. Can supply if required (I can email it to you as is or post in the forum masking IP/MACs).

Reverted to 1.15.X (Built 20250330-2253 git@ca9ca6a5).

Hold off on supplying anything for now. I can confirm you're not crazy

I set up a local pppoe server here and was able to replicate the problem.
I am compiling a test kernel module which I think will fix the problem, but I've run out of steam for tonight so will pick it up again tomorrow.

Gargoyle Forum

Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-01-28