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!

My typo. BWDPI.
No "BWDPI" in my system log. Even shortened the search to "BW" and nothing shows up.
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
That's where I'm at right now. Simply avoid that menu selection.
 
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
I saw this in your post yesterday.
 
I saw this in your post yesterday.
Your right. Sorry. Face palm moment. Had so many thing going on at the same time earlier that forgot that I hard reset that router and manually reconfigured and haven't visited the Adaptive QoS section since. So of course BWDPI wouldn't show up. Thought I was looking at a log from prior to the last hard reset, turns out I wasn't. Dug up a log from yesterday I saved and sure enough the "BWDPI" is there.

PS: Should have also mentioned that I was noticing the 2 to 3 minute WiFi drop on the 5Ghz band (non Guest WiFi). Just tested the non guest 2.4Ghz WiFi band and the WiFi drop is there but not as long. The WiFi outage lasted just under a minute on the 2.4Ghz band (approx 40 seconds). Could see people not realizing it dropped if they weren't looking for it or weren't trying to access LAN/WAN at exactly that short window if using the 2.4Ghz WiFi and not the 5Ghz WiFi. Don't even notice the WiFi drop when on a LAN connection.

Edit: Another look at the logs when PC is connected via Ethernet shows a disconnect running about 40 seconds with Guest Network enabled and YazFi installed and enabled. But Windows 11 doesn't indicate a Ethernet port disconnect (at least on screen/task bar network icon).
 
Last edited:
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.
...

I was able to recreate the scenario you described on the RT-AX86U router every time I visited the "Adaptive QoS" webpage and landed on the "Bandwidth Monitor" tab. It happens very consistently; the firewall appears to be restarted only *after* leaving the "Bandwidth Monitor" and the log entry "BWDPI: force to flush flowcache entries" appears; and then, as a result, the "/jffs/scripts/firewall-start" custom script is executed which launches YazFi to reset/reconfigure the wireless radios.

As @dave14305 pointed out, it's the "Bandwidth Monitor" with BWDPI that starts the sequence of events that leads to YazFi being executed. Unfortunately, at this point, I don't see how YazFi can prevent the problem since it's simply reacting to the firewall restart triggered by the separate component.
 
@Martinsk, thanks for taking a peak into this to narrow down the cause. Looks like its just something YazFi users will have to be aware of if they visit the Adaptive QoS - Bandwidth Monitor page or section when using a WiFi connected PC, particularly if using a 5Ghz WiFi connection. They may/will loose their WiFi connection for a short period of time (up to two or three minutes for the 5Ghz WiFi on a RT-AX86U Pro) if the YazFi user lands on the Bandwidth Monitor page.

The workaround for the GUI Internet Speed test is to just go direct to the page (/AdaptiveQoS_InternetSpeed.asp) rather than using the GUI menu navigation.
 
I have setup yazfi as a guest network with one way to guest enabled.
On my LAN, I have jellyfin running on 192.168.1.24:8096.

I would like to allow a few devices that are connected to my 5Ghz guest network to connect to jellyfin. This is what I setup for iptables:
Bash:
iptables -I YazFiFORWARD -i wl1.1 -o br0 -s 192.168.3.20 -d 192.168.1.24 -j ACCEPT

This works as expected. The client 192.168.3.20 (android phone running jellyfin app) can connect and is able to play media successfully.

My question is - does it make sense to restrict it further for specific port/protocol? As I have other services running on 192.168.1.24 on different ports and I don't want those to be accessible by this client?
If yes, I tried:
Bash:
iptables -I YazFiFORWARD -i wl1.1 -o br0 -s 192.168.3.20 -d 192.168.1.24 -p tcp --dport 8096 -j ACCEPT
This allows login to jellyfin, but gets stuck on loading the media.

Hope this is the right thread/forum for this question. If not, please point me to the right one. Thank you
 
@jbpcan, if you haven't seen some other past discussions on using YazFi custom scripting and port forwarding on YazFi you may want to see them incase they are relevant to your question.
I made a post on how to do basic forwarding on YazFi in the following post:
https://www.snbforums.com/threads/allowing-access-to-selected-network-devices.80405/#post-784521
And see another post where forwarding a specific port is shown that appeared to work for a person using YazFi:
https://www.snbforums.com/threads/help-with-iptables-script.87827/#post-878058
There may be additional past YazFi forwarding discussions that can be found using the Filter feature or by using the forum search feature.

It is up to you and your specific use case if you need to only forward specific ports or allow full access between the YazFi client(s) and the main LAN client(s). If you don't want a YazFi client to access other ports or services on the main LAN client, then you can choose to limit access with the IPTables YazFi custom scripting.
 
Hello, YazFi seems to have disappeared from the menu items in my Asus router UI.

Any ideas what could cause this?

Could someone please remind me where it would usually appear? Maybe I've just lost it.
 
Hello, YazFi seems to have disappeared from the menu items in my Asus router UI.

Any ideas what could cause this?

Could someone please remind me where it would usually appear? Maybe I've just lost it.
It should be under the Guest Network section.
 
Hello, YazFi seems to have disappeared from the menu items in my Asus router UI.

Any ideas what could cause this?

Could someone please remind me where it would usually appear? Maybe I've just lost it.
Guest Network > YazFi:
68747470733a2f2f7075752e73682f48676d4c6c2f313738333237623433372e706e67


Or use the CLI:
68747470733a2f2f7075752e73682f48676d46312f356138616537656438322e706e67


If the YazFi tab is missing or the installation is corrupt you may want to reinstall it via AMTM or the command line.
 
@Martinski, it appears YazFi (v4.4.4) is experiencing a bug with the stable 386.14 firmware just released. The scroll bars on the web UI disappear and the user cannot scroll down (using the mouse). See attached images from Guest Network page showing scroll bars, and YazFi page where they are missing.

Another user has pointed out this issue is also present in other add-on scripts. See the following posts/discussions:
https://www.snbforums.com/threads/a...eta-is-now-available.90810/page-2#post-917553
https://www.snbforums.com/threads/a...ow-available-for-ac-models.91060/#post-918726
And RMerlin's reply and commentary in the 386.14 discussion:
https://www.snbforums.com/threads/a...ow-available-for-ac-models.91060/#post-918744
 

Attachments

  • guestnetwork.jpg
    guestnetwork.jpg
    66.1 KB · Views: 38
  • yazfi.jpg
    yazfi.jpg
    86.1 KB · Views: 35
Last edited:
@Martinski, it appears YazFi (v4.4.4) is experiencing a bug with the stable 386.14 firmware just released. The scroll bars on the web UI disappear and the user cannot scroll down (using the mouse). See attached images from Guest Network page showing scroll bars, and YazFi page where they are missing.
Thanks for reporting the problem and providing enough context (add-on version & screenshots) to show what the problem is. I'm taking a look.

Another user has pointed out this issue is also present in other add-on scripts. See the following posts/discussions:
https://www.snbforums.com/threads/a...eta-is-now-available.90810/page-2#post-917553
https://www.snbforums.com/threads/a...ow-available-for-ac-models.91060/#post-918726
And RMerlin's reply and commentary in the 386.14 discussion:
https://www.snbforums.com/threads/a...ow-available-for-ac-models.91060/#post-918744

Other posts reporting the "missing scrollbar" problem with other add-ons don't include the specific add-on version being tested (or screenshots), and very little context is provided. The problem is add-on specific so context/details are important.
 
I'm taking a look.
Thanks for taking a look.

PS: Some additional observations with 386.14 and YazFi 4.4.4. I noticed I cannot use the browser back button (in Brave browser) or keyboard commands to go back to the previous page once I landed on the YazFi page with missing scroll bars. Had to either click a menu link or very quickly right click on the browser back button and select a previous page or very quickly use the back keyboard combo keys.

If I wasn't quick enough with right clicking on the browser back button it would only show YazFi pages in the back button history. Example of that back history showing multiple YazFi pages with a new one added every 5 seconds or so shown below. I assume the adding of the YazFi page every five seconds or so is tied to the "connected guests" being refreshed every 5 seconds in YazFi since I see it reflected on 3004.388.8 firmware as well where there isn't an issue with the missing scrollbars in YazFi.

Example of the back button (Brave browser) history on 386.14 with YazFi 4.4.4 showing multiple YazFi entries:
BackButton.jpg
 
Last edited:
To anyone experiencing the missing scrollbars issue with YazFi on 386.14 firmware. Use the CLI interface (accessed using SSH) to configure YazFI for now. CLI example from YazFi's Github page:

68747470733a2f2f7075752e73682f48676d46312f356138616537656438322e706e67
 
@Martinski, it appears YazFi (v4.4.4) is experiencing a bug with the stable 386.14 firmware just released. The scroll bars on the web UI disappear and the user cannot scroll down (using the mouse). See attached images from Guest Network page showing scroll bars, and YazFi page where they are missing.
...
Last night, I fixed the "missing vertical scrollbar" problem and submitted a pull request to @Jack Yaz's "develop" branch repository (it's not merged yet).

YazFi v4.4.5 (local development test):

YazFi_v4.4.5_OK.jpg


This evening after dinner, I'll fix the same problem found on the uiScribe webGUI.

EDIT [UPDATE]:
The "missing vertical scrollbar" problem has been fixed for uiScribe. A PR has now been submitted to @Jack Yaz's 'develop' branch.

uiScribe v1.4.6 (local development run)

uiScribe_v1.4.6_OK.jpg


FYI.
 
Last edited:
@Martinski, thanks for the updates. Ran the 4.4.5 developer version of YazFi onto a RT-AC68U running 386.14 and the scrollbars are active and the YazFi page can be scrolled. As a reminder to others if they want to use the YazFi developer version, you can run the following via SSH on the router running YazFi to update to the developer version.
Code:
/jffs/scripts/YazFi develop
/jffs/scripts/YazFi forceupdate

Example of the YazFi 4.4.5 developer version showing the scrollbar.
YazFi_4_4_5_developer.jpg
 
Using the great advice given here, I've created multiple IPtable exceptions that I've put into the myscripts.sh file.

What is the proper syntax to add my own comment line within the file, just so I can keep track of what each exception is for?

#? Or ##?

I found this tutorial, but this seems very different from what I need:
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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