What's new

YazFi YazFi v4.x - continued

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

When YazFi is enabled, all connected clients lose LAN access every time the internet connection (WAN) is lost. We can simulate this scenario by unplugging the WAN cable for 5 seconds and then plugging it back in. Within a minute, the WiFi will restart, and all devices lose LAN access, including the main network (non-guest). This becomes problematic when watching a Netflix show or transferring large files between two computers.

Interestingly, the loss of WiFi also occurs when the internet remains connected. It appears to be random. There might be an underlying trigger causing this reset. However, if I disable all YazFi Guest Networks, everything works normally, and there are no connection issues.

Is there a way to resolve this problem? And why is a reset necessary when the internet connection is lost?
 
Yeah, find out what's causing the WAN to drop and fix it.
Certainly! The issue lies in the fact that the “/jffs/scripts/YazFi runnow” command is invoked when the “/jffs/scripts/firewall-start” script runs. Specifically, the “runnow” command triggers the execution of the “Config_Networks” function, which in turn calls “Iface_BounceClients”. It is within this function that clients are forced to reauthenticate by toggling the WiFi radio off and then back on.

The question at hand is: Is there a way to prevent reauthentication when the WAN cable is unplugged or Internet access is lost?

If you have any other constructive comments or insights, feel free to share them! ;)
 
Last edited:
When YazFi is enabled, all connected clients lose LAN access every time the internet connection (WAN) is lost.
What router?
What YazFi version?
Are any other ad-on scripts running?
What do does the system log show at the time the WAN goes down?

Edit to add: Just did a quick test and observed similar. It appears, per the system log, that the firewall and dnsmasq get restarted then YazFi is restarted after WAN access is lost and restored. Relevant portion of system.log (some information redacted):
Code:
Mar 26 14:34:00 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link DOWN.
Mar 26 14:34:06 WAN_Connection: WAN(0) link down.
Mar 26 14:34:54 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 1) Link Up at 1000 mbps full duplex
Mar 26 14:34:57 WAN_Connection: WAN(0) link up.
Mar 26 14:34:57 rc_service: wanduck 1543:notify_rc restart_wan_if 0
Mar 26 14:34:57 custom_script: Running /jffs/scripts/service-event (args: restart wan_if)
Mar 26 14:34:57 lldpd[2473]: removal request for address of 11.111.111.111%17, but no knowledge of it
Mar 26 14:34:57 dnsmasq[27317]: read /etc/hosts - 24 names
Mar 26 14:34:57 dnsmasq[27317]: read /jffs/addons/YazDHCP.d/.hostnames - 44 names
Mar 26 14:34:57 kernel: potentially unexpected fatal signal 6.
Mar 26 14:34:57 kernel: CPU: 0 PID: 27317 Comm: dnsmasq Tainted: P           O      4.19.183 #1
Mar 26 14:34:57 kernel: Hardware name: RTAX86U_PRO (DT)
Mar 26 14:34:57 kernel: pstate: 00070010 (nzcv q A32 LE aif)
Mar 26 14:34:57 kernel: pc : 00000000f78a63a4
Mar 26 14:34:57 kernel: lr : 00000000ff8028a0
Mar 26 14:34:57 kernel: sp : 00000000ff8028a0
Mar 26 14:34:57 kernel: x12: 0000000000000000
Mar 26 14:34:57 kernel: x11: 00000000ff802b30 x10: 00000000f799cde0
Mar 26 14:34:57 kernel: x9 : 0000000000000002 x8 : 0000000000000001
Mar 26 14:34:57 kernel: x7 : 00000000000000af x6 : 00000000ff802ae0
Mar 26 14:34:57 kernel: x5 : 00000000ff802ae0 x4 : 0000000000000006
Mar 26 14:34:57 kernel: x3 : 0000000000000008 x2 : 0000000000000000
Mar 26 14:34:57 kernel: x1 : 00000000ff8028a0 x0 : 0000000000000000
Mar 26 14:34:58 lldpd[2473]: removal request for address of 311.111.111.111%17, but no knowledge of it
Mar 26 14:34:58 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Mar 26 14:34:58 wan: finish adding multi routes
Mar 26 14:34:58 YazFi: Firewall restarted - sleeping 10s before running YazFi
Mar 26 14:34:58 dhcp_client: bound 11.111.111.111/255.255.248.0 via 11.111.111.111 for 1800 seconds.
Mar 26 14:35:01 rc_service: watchdog 2384:notify_rc start_dnsmasq
Mar 26 14:35:01 custom_script: Running /jffs/scripts/service-event (args: start dnsmasq)
Mar 26 14:35:01 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Mar 26 14:35:01 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Mar 26 14:35:01 dnsmasq[17679]: started, version 2.90 cachesize 1500
Mar 26 14:35:01 dnsmasq[17679]: asynchronous logging enabled, queue limit is 5 messages
Mar 26 14:35:01 dnsmasq-dhcp[17679]: DHCP, IP range 192.168.7.2 -- 192.168.7.254, lease time 1d
Mar 26 14:35:01 dnsmasq-dhcp[17679]: DHCP, IP range 192.168.4.2 -- 192.168.4.254, lease time 1d
Mar 26 14:35:01 dnsmasq-dhcp[17679]: DHCP, IP range 192.168.102.2 -- 192.168.102.254, lease time 1d
Mar 26 14:35:01 dnsmasq-dhcp[17679]: DHCP, IP range 192.168.101.2 -- 192.168.101.254, lease time 1d
Mar 26 14:35:01 dnsmasq-dhcp[17679]: DHCP, IP range 192.168.2.2 -- 192.168.2.254, lease time 1d
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for _dns.resolver.arpa
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for use-application-dns.net
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for lan
Mar 26 14:35:01 dnsmasq[17679]: read /etc/hosts - 24 names
Mar 26 14:35:01 dnsmasq[17679]: read /jffs/addons/YazDHCP.d/.hostnames - 44 names
Mar 26 14:35:01 dnsmasq-dhcp[17679]: read /jffs/addons/YazDHCP.d/.staticlist
Mar 26 14:35:01 dnsmasq-dhcp[17679]: read /jffs/addons/YazDHCP.d/.optionslist
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 9.9.9.11#53
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 149.112.112.11#53
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for _dns.resolver.arpa
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for use-application-dns.net
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for lan
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 9.9.9.11#53
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 149.112.112.11#53
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for _dns.resolver.arpa
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for use-application-dns.net
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for lan
Mar 26 14:35:01 WAN_Connection: WAN was restored.
Mar 26 14:35:01 dnsmasq[17679]: read /etc/hosts - 24 names
Mar 26 14:35:01 dnsmasq[17679]: read /jffs/addons/YazDHCP.d/.hostnames - 44 names
Mar 26 14:35:01 dnsmasq-dhcp[17679]: read /jffs/addons/YazDHCP.d/.staticlist
Mar 26 14:35:01 dnsmasq-dhcp[17679]: read /jffs/addons/YazDHCP.d/.optionslist
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 9.9.9.11#53
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 149.112.112.11#53
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for _dns.resolver.arpa
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for use-application-dns.net
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for lan
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 9.9.9.11#53
Mar 26 14:35:01 dnsmasq[17679]: using nameserver 149.112.112.11#53
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for _dns.resolver.arpa
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for use-application-dns.net
Mar 26 14:35:01 dnsmasq[17679]: using only locally-known addresses for lan
Mar 26 14:35:08 YazFi: YazFi v4.4.4 starting up
Mar 26 14:35:10 YazFi: wl0.2 (SSID: Asus2) - sending all interface internet traffic over WAN interface
Mar 26 14:35:14 YazFi: wl1.2 (SSID: Asus2_5G) - sending all interface internet traffic over WAN interface
Mar 26 14:35:17 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
 
Last edited:
What router?
What YazFi version?
Are any other ad-on scripts running?
What do does the system log show at the time the WAN goes down?
RT-AX88U (YazFi 4.4.4). I use YazFi and YazDHCP. I explained the problem in the message I posted just before you sent yours. YazFi turns the WiFi radio off for 10 seconds, then back on every time the WAN cable is unplugged and then plugged back in.

EDIT: I did try YazFi 4.4.5, but the same issue persists. Chromecast doesn’t auto-reauthenticate when it is in sleep mode after a WiFi radio restart. Consequently, there is no way to turn it on using a Google Home speaker. I need to manually turn it back on for it to reconnect to the WiFi automatically. Additionally, my Canon printer is picky and won’t always obtain a new IP from the DHCP when the WiFi radios are restarted. To resolve this, I either power off/on my printer or restart the WAN interface or the router for it to acquire an IP.
 
Last edited:
YazFi turns the WiFi radio off for 10 seconds, then back on every time the WAN cable is unplugged and then plugged back in.
Yep. The YazFi script is performing as expected when the Firewall starts/restarts. The script would likely have to be rewritten to account for keeping YazFi WiFi up rather than restarting when the WAN goes down which triggers the Firewall restart when it comes back up. Its possible/likely there is a valid reason why YazFi is restarted after the Firewall is started/restarted. Perhaps @Martinski may have some input or explanation as to the script's actions due to their recent working with YazFi.
 
Last edited:
Yep. The YazFi script is performing as expected when the Firewall starts/restarts. The script would likely have to be rewritten to account for keeping YazFi WiFi up rather than restarting when the WAN goes down which triggers the Firewall restart when it comes back up. Its possible/likely there is a valid reason why YazFi is restarted after the Firewall is started/restarted. Perhaps @Martinski may have some input or explanation as to the script's actions due to their recent working with YazFi.

For now, I have commented out that code in the Iface_BounceClients() function:

Bash:
    for IFACE in $IFACELIST; do
        wl -i "$IFACE" radio off >/dev/null 2>&1
    done

    sleep 10

I hope this won’t break the script too much while waiting for a better solution.
 
Last edited:
Yep. The YazFi script is performing as expected when the Firewall starts/restarts. The script would likely have to be rewritten to account for keeping YazFi WiFi up rather than restarting when the WAN goes down which triggers the Firewall restart when it comes back up. Its possible/likely there is a valid reason why YazFi is restarted after the Firewall is started/restarted. Perhaps @Martinski may have some input or explanation as to the script's actions due to their recent working with YazFi.
I don't know the specific reasons behind @Jack Yaz's design decision to essentially do a full reset & reconfiguration of the YazFi Guest Networks (including turning OFF & then back ON the WiFi radios) when the script is called from within the firewall-start script. My guess is that since the firewall can be restarted for several different reasons and YazFi doesn't know the specific reason each time it happens, the only way to ensure a clean setup of the Guest Networks is to reset/reconfigure from scratch. But again, only Jack Yaz would know with certainty.
 
Hi, i know ac86u is not desing for caffee but im trying to manage it. So my main problem is when 15-17 clients join on wifi next one is unable to join. Message on phone is device is unable to connect to wifi. Bandwitch is not a problem, cpu and ram usage is not a problem. Even in that moment all are like 1-3% used. Most devices are idle. Idk what is a problem so i want to ask can this script potentionally help? Also i try to make 2x 2.4 and 2x 5ghz same ssid network so i get 4 same guest networks, i saw also that devices are spread over mostly 2 5ghz network but i didnt get any benefit of it. My target will be maybe 30-40 devices max in peak time. Regards
 
Does YazFi work correctly w/o using the Merlin DHCP server? Using my PiHole as a DCHP server as well for a few reasons and wanted to understand that - and if there is a way to use YazFi w/o the alternate subnet (but guessing that is how much if it's features function).
 
Hoping someone can help me with a simple IPtables question. I am completely unfamiliar with IPtable syntax.

I have a guest network set up for devices that need access amongst themselves. I have turned on 1-way access to this guest network from the LAN.

For 1 specific device, 192.168.4.36, I need to open access back to the LAN to IP address 192.168.1.78.

1714882944941.png


I've made a myscript.sh with the following line:

iptables -I YazFiFORWARD -i w10.3 -o br0 -s 192.168.4.36 -d 192.168.1.78 -j ACCEPT

Is this right? I'm not getting consistent results.

I do not know what ports or protcols are being used so I cannot limit those.

(Specifically, I have an AV receiver on the guest network. Using the music app on my phone, I can only send commands but receive no feedback from the receiver. I'm trying to open up the receiver so that it can send data back to the phone).
 
Hoping someone can help me with a simple IPtables question. I am completely unfamiliar with IPtable syntax.

I've made a myscript.sh with the following line:

iptables -I YazFiFORWARD -i w10.3 -o br0 -s 192.168.4.36 -d 192.168.1.78 -j ACCEPT

Is this right? I'm not getting consistent results.
The following post I made a while back on custom scripting with YazFi may provide some help and examples:
https://www.snbforums.com/threads/allowing-access-to-selected-network-devices.80405/#post-784521

An example from that post of a single guest WiFi client to/from a single main LAN client (all ports):
Code:
#!/bin/sh
iptables -I YazFiFORWARD -i wl0.1 -o br0 -s 192.168.3.50 -d 192.168.1.100 -j ACCEPT
iptables -I YazFiFORWARD -i br0 -o wl0.1 -s 192.168.1.100 -d 192.168.3.50 -j ACCEPT
 
The following post I made a while back on custom scripting with YazFi may provide some help and examples:
https://www.snbforums.com/threads/allowing-access-to-selected-network-devices.80405/#post-784521

An example from that post of a single guest WiFi client to/from a single main LAN client (all ports):
Code:
#!/bin/sh
iptables -I YazFiFORWARD -i wl0.1 -o br0 -s 192.168.3.50 -d 192.168.1.100 -j ACCEPT
iptables -I YazFiFORWARD -i br0 -o wl0.1 -s 192.168.1.100 -d 192.168.3.50 -j ACCEPT
Thank you so much. I had actually used a different instructional post of yours https://www.snbforums.com/threads/help-with-iptables-script.87827/ to get started with my attempt!

After reviewing the post you pointed out, I had made a silly mistake. L ≠ 1! w10.3 ≠ wl0.3.

I was already open one way, so I just needed to open up the other direction.
 
Last edited:
@Jack Yaz and or @Martinski, noticed something strange recently where YazFi restarts the firewall when I visit the Adaptive QoS section in the Asus-Merlin firmware then leave that section.

Visiting the Adaptive QoS page then leaving the page appears to trigger YazFi to issue a Firewall restart for some reason. I've gone so far as to do a hard reset and manual reconfiguration from scratch and the issue still persists. Any thoughts on why visiting the Adaptive QoS page/section then leaving would trigger a YazFi firewall restart? I do not have Adaptive QoS enabled.

RT-AX86U Pro
Asus-Merlin 3004.388.7
YazFi 4.4.4
YazDHCP v1.0.6

The following is from the log right around when I visit Adaptive QoS and YazFi triggers a firewall restart and reauthentication.
Code:
May 26 15:43:22 kernel: Init chrdev /dev/idp with major 190
May 26 15:43:22 kernel: tdts: tcp_conn_max = 8000
May 26 15:43:22 kernel: tdts: tcp_conn_timeout = 300 sec
May 26 15:43:24 kernel: SHN Release Version: 2.0.6 9d6bb506
May 26 15:43:24 kernel: UDB Core Version: 0.2.20
May 26 15:43:24 kernel: Init chrdev /dev/idpfw with major 191
May 26 15:43:24 kernel: Registered DNS Req parsing
May 26 15:43:24 kernel: IDPfw: flush fc
May 26 15:43:24 kernel: IDPfw: IDPfw is ready
May 26 15:43:24 kernel: sizeof forward pkt param = 280
May 26 15:43:24 BWDPI: fun bitmap = 3
May 26 15:43:35 BWDPI: force to flush flowcache entries
May 26 15:43:35 kernel: IDPfw: Exit IDPfw
May 26 15:43:35 kernel: mod epilog takes 0 jiffies
May 26 15:43:35 kernel: IDPfw: Exit IDPfw
May 26 15:43:35 kernel: Exit chrdev /dev/idpfw with major 191
May 26 15:43:35 kernel: udb_core lock_num = 17
May 26 15:43:35 kernel: Exit chrdev /dev/idp with major 190
May 26 15:43:35 BWDPI: rollback fc
May 26 15:43:35 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
May 26 15:43:35 YazFi: Firewall restarted - sleeping 10s before running YazFi
May 26 15:43:45 YazFi: YazFi v4.4.4 starting up
May 26 15:43:48 YazFi: wl0.2 (SSID: XXXXX2) - sending all interface internet traffic over WAN interface
May 26 15:43:52 YazFi: wl1.2 (SSID: XXXXX2_5G) - sending all interface internet traffic over WAN interface
May 26 15:43:55 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Note: redacted YazFi SSID's in above log snippet.
 
@Jack Yaz and or @Martinski, noticed something strange recently where YazFi restarts the firewall when I visit the Adaptive QoS section in the Asus-Merlin firmware then leave that section.

Visiting the Adaptive QoS page then leaving the page appears to trigger YazFi to issue a Firewall restart for some reason. I've gone so far as to do a hard reset and manual reconfiguration from scratch and the issue still persists. Any thoughts on why visiting the Adaptive QoS page/section then leaving would trigger a YazFi firewall restart? I do not have Adaptive QoS enabled.

RT-AX86U Pro
Asus-Merlin 3004.388.7
YazFi 4.4.4
YazDHCP v1.0.6

I just ran the quick test 3 times. On the WebGUI, I went to the "Adaptive QoS" page and clicked on the "QoS" tab (setting is OFF); then I went to the "System Log - General Log" page. I checked the "/tmp/syslog.log" file searching for recent "firewall-start" or "YazFi" entries but none were found.
Bash:
grep -E "firewall-start|YazFi" /tmp/syslog.log

Tested on:
-------------
RT-AC86U
Asus-Merlin 3004.386.13_2
YazFi 4.4.5 (develop version)
YazDHCP 1.0.6
scMerlin 2.5.3
Adaptive QoS: OFF/DISABLED

I wonder if the behavior you described is limited to your particular router model or your specific router configuration. This evening I'll try the same test on an RT-AX86U router that I have access to.

The following is from the log right around when I visit Adaptive QoS and YazFi triggers a firewall restart and reauthentication.
To clarify: I don't see YazFi triggering the firewall restart. Instead, something else appears to be triggering the firewall restart which, in turn, ends up calling YazFi to reset/reconfigure the wireless radios.

YazFi calls a firewall restart only when a new version of the script is installed, or when the add-on is uninstalled.
 
I wonder if the behavior you described is limited to your particular router model or your specific router configuration. This evening I'll try the same test on an RT-AX86U router that I have access to.

To clarify: I don't see YazFi triggering the firewall restart. Instead, something else appears to be triggering the firewall restart which, in turn, ends up calling YazFi to reset/reconfigure the wireless radios.

YazFi calls a firewall restart only when a new version of the script is installed, or when the add-on is uninstalled.
Wonder if its something related to the Asus-Merlin 3004.388.7 firmware. Only noticed this happening on my RT-AX86U Pro recently due to going to the Internet Speed Test page in the GUI under Adaptive QoS and noticed the WiFI clients getting disconnected for a period of time and the speed test page throwing an error on the page (see screen cap below) when running the speedtest. Looking further it seems it was just going to Adaptive QoS section then leaving seemed to trigger the /jffs/scripts/firewall-start to run. Don't recall this happening on earlier Merlin firmware on this router.

SpeedTestPage.jpg


I assumed (perhaps incorrectly) that this was related to YazFi due to the use of /jffs/scripts/firewall-start file which seem to either be created or updated when installing YazFi.
 
@Martinski, Did some more testing on this. Some additional commentary.

Synopsis: It appears when Guest Network is activated there is initially a noticeable WiFi disconnect of approx 2-3 minutes. Without YazFi installed and with Guest Network enabled there doesn't appear to be a noticeable disconnect of the WiFi when accessing and leaving the Adaptive QoS page or seeing an error when running the Internet Speed test under the Adaptive QoS section. With YazFi installed and Guest Networks active however there is noticeable WiFi disconnect of 2 to 3 minutes when accessing and leaving (or running a speed test) in the Adaptive QoS page/section.

What appears to be happening is the Adaptive QoS page is, for some reason, triggering the firewall restart script added by YazFi, then when Guest Network is enabled and when YazFi gets run, it is combining to introduce the noticeable 2 to 3 minute drop of the WiFI that otherwise doesn't seem to happen on the Adaptive QoS section when either YazFi isn't installed or Guest Network is disabled. Its possible this issue has been there for some time and I never noticed it prior to moving to using WiFi only on my main laptop PC recently. (Note: just my wild guess/speculation.)

What follows are my quick notes on what I saw/did just in case it helps:

Did a hard factory reset and initial QIS setup. Do not see a noticeable WiFi disconnect when going to the Adaptive QoS page and running a Internet Speed test, nor do I see an error on the speed test page (like prior posted screen capture show).

The /jffs/scripts folder does not contain any files at this point.

Installed YazFi via amtm. After YazFi install did not do any configuration of YazFi. Did not setup Guest Network. The /jffs/scripts folder has 6 files in it including firewall-start. Went to Adaptive QoS page and did a Internet Speed test. There did not appear to be a noticeable WiFi disconnection.

Activating Guest Network and inputting the information (SSID, set authentication method, and input password) into Guest Network #2 2.4Ghz and 5Ghz sections, then applied the changes. It was then I noticed a wifi disconnect of approx two to three minutes.

When WiFi came back, I went to the Adaptive QoS page and then returned to the System Log page. After a few seconds the WiFi disconnected for approx 2-3 minutes. Once WiFi was reenabled I went to the Adaptive QoS Internet Speed page and ran a speed test. A few seconds after speed test completed WiFi dropped again for approx 2-3 minutes and the speed test page indicated the error per the previously posted speed test screen capture posted previously.

I next went in and disabled Guest Network(s). Each time I selected the disable button the WiFi was lost for approx 2-3 minutes.

After disabling Guest Network WiFi, accessed and left the Adaptive QoS page. No noticeable WiFi disconnect.

Used the YazFi CLI to remove YazFi including removing configuration files. After YazFi uninstall 5 files were left in the /jffs/scripts folder (dnsmasq.postconf, firewall-start, openvpn-event, service-event, services-start). The firewall-start file did not have the YazFi line of code in it, only text in file was "#!/bin/sh".

With YazFi uninstalled, reenabled Guest Network #2, there was a noticeable drop of the Wifi, again approx 2-3 minutes when each band (2.4Ghz and 5Ghz) was enabled.

Once WiFi returned with YazFi uninstalled and Guest Network #2 enabled, went to Adaptive QoS page and back to System Log page. No noticeable WiFi disconnect. Went to Adaptive QoS and did a Internet Speed test. No error on speed test page, no noticeable WiFi disconnect.
 
Last edited:
I wonder if the behavior you described is limited to your particular router model or your specific router configuration. This evening I'll try the same test on an RT-AX86U router that I have access to.
It’s the Bandwidth Monitor page that triggers the BWDPI activation when Adaptive QoS is disabled, for device and app analysis.
 
Last edited:
It’s the Bandwidth Monitor page that triggers the bwpdi activation when Adaptive QoS is disabled, for device and app analysis.
Yeah the QoS -WAN/LAN Bandwidth Monitor page is the default landing page when selecting Adaptive QoS from the left menu. I typically don't regularly visit this menu section, and when I do its because I'm navigating to the Internet Speed test page to run a speed test. Obviously something is getting run on that page, when combined with Guest Network and YazFi, is causing the WiFi drop for 2-3 minutes that I'm seeing.

AdaptiveQoS_BandwidthMonitor.jpg


Note: Just did a search through the system log for "bwpdi" and nothing comes up.
 
Last edited:
Seeing similar with my router. However the WiFi (2.4GHz) is only down a matter of a few seconds.
Nothing BWDPI in the logs.
Another thing it seems to do is kill IPv6 DDNS. I have to wait a good 10 minutes before I can get it working again.
Code:
 ppp0 has not yet obtained an WAN IPv6 address.(8)
However, that's for me to deal with simply by not visiting a page I don't need to visit. If it wasn't for this turn in this thread I wouldn't even have known I could possibly have a problem
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top