YazFi Is YazFi gone?

[fotingo]

I recently updated to version 3006.102.4 and YazFi is gone. I tried to install it again in AMTM, but It's not working.
Any ideas?

 

[ColinTaylor]

Release - Asuswrt-Merlin 3006.102.4 is now available

Updated my GT-AX6000, update went smoot. I can't untick b/g protection in N only mode, it doesn't stay.

www.snbforums.com

 

[PoliteWaifer]

The owner doesn't own an Asus Router anymore, so I don't think it's getting many updates aside from one user who has faithfully been submitting PRs.

Personally I stopped running it, as it's a complicated add-on that needs upkeep so it doesn't interfere with router functions at the level it integrates at. I found it was becoming a bit unstable with how VLANs were being integrated. Maybe that's just me though!

 

[fotingo]

No way! It was working so good for me.

 

[bennor]

I recently updated to version 3006.102.4 and YazFi is gone. I tried to install it again in AMTM, but It's not working.
Any ideas?

YazFi is not gone. Rather YazFi is not supported on the 3006.102.x firmware. If you read through the Asus-Merlin 3006.102.4 release discussion you'll see several posts commenting about YazFi not working or people asking for alternatives. See this link for those posts. Guest Network Pro has some features that are also found in YazFi.

There are several add-ons that are not currently supported on the 3006 firmware and some which the user will need to manually update to the develop branch. See the following link for a listing of 3006 supported and not supported add-ons.

Compatibility Findings with AddOns with GT-BE98 Pro

I would but I don't have this router. Holding off to see what routers will be out later this year. Chances of routers being released later this year having Merlin firmware at launch or soon thereafter are slim to none. ASUS Unveils Cutting-Edge AI Router, Networking Solutions at CES 2025

www.snbforums.com

The YazFi developer (Jack Yaz) indicated several years ago (2022) they were no longer actively developing YazFi and his other addon scripts. User Martinski has done a little bit of YazFi updating (develop branch) since then.

I pop up occasionally, but since I moved to pfSense and UniFi, and my Asus routers decided to give up the ghost, I'm not actively developing anymore. I chime in on support requests when I have time as well

 

[jsbeddow]

I am well aware that YazFi will need to be removed before migrating to this 3006 branch of firmware, but I do recall that one user mentioned that it also required some manual intervention to fully remove all traces: anyone care to comment on more specific details or their experiences with that process (needed/not needed)?

 

[bennor]

I am well aware that YazFi will need to be removed before migrating to this 3006 branch of firmware, but I do recall that one user mentioned that it also required some manual intervention to fully remove all traces: anyone care to comment on more specific details or their experiences with that process (needed/not needed)?

Some are finding that they need to do a hard factory reset when updating from 3004 to 3006 firmware. A hard factory reset should get rid of any addon script remnants after a manual addon script uninstall.

Personally I took the time to do a hard factory reset when flashing Asus-Merlin 3006.102.x firmware on a RT-AX86U Pro, then a manual configuration (no saved router.cfg import). Personally I also took the time to review the addons I used on 3004 firmware (YazFi and YazDHCP) before attempting to install them on 3006. As indicated YazFi is depreciated due to Guest Network Pro and doesn't work on 3006 firmware. YMMV and all that.

3006 and it's Guest Network Pro/VLAN/SDN are a major change over prior 3004.x firmware.

 

[jsbeddow]

Thanks; I already knew that the ideal/ ultimate "housecleaning" step would be a full reset and manual setup on the new firmware, but like most people, I was hoping to avoid that. Lots of little details would have to be exported and re-integrated (Wireguard and OpenVPN configs and certificates, AdGuardHome setup, static DHCP assignments).

I was looking for the exact parts of YazFi that remain behind after removal so I can do some manual cleanup.

 

[bennor]

I was looking for the exact parts of YazFi that remain behind after removal so I can do some manual cleanup.

Exact parts left over may vary depending on how one has configured YazFi and if they've used custom firewall scripting.
Generally look at the various subfolders in the /jffs/ folder to see if there are any left over YazFi folders or files after one has manually uninstalled YazFi. In particular look at the following files to see if they have any YazFi code added into them:

/jffs/scripts/dnsmasq.postconf
/jffs/configs/dnsmasq.conf.add
/etc/dnsmasq.conf
/jffs/scripts/firewall-start
/jffs/scripts/service-event
/jffs/scripts/services-start

I fully understand that some have a strong aversion to performing a hard factory reset, for various reasons. But really, the best way to ensure no left over script code remains is to do a hard factory reset. And the best way to deal with quirky issues is to do a hard factory reset. Quite often can reset and manually reconfigure the router faster than trying to track down the odd ball issue that otherwise would be solved by a reset. YMMV