YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

[Jack Yaz]

This is a great upgrade @Jack Yaz, thank you.

With my 192.168.254.254 'normal' IP for the router (RT-AX88U), this is what the defaults show for me. Just wondering if there might be an issue with some of the IP addresses it chooses as defaults?

View attachment 21480

View attachment 21480

There's always 1 person who uses a weird default IP range! The "autofill" naively assumes it can +1 the octet. I will add a check for hitting the 255 limit and increase the previous octet accordingly.

 

[Jack Yaz]

I got the following error even after upgrading lot of times with uf when I choose option 1:

mount: mounting /tmp/index_style.css on /www/index_style.css failed: No such file or directory

Anything I did wrong?

No, I missed deleting 2 lines when re-using a function. The just-published update (no version changes) will resolve it. You'll be pleased to know it was a harmless error any doesn't impact on YazFi at all.

 

[Jack Yaz]

Upgraded to 4.0.0; though took a detour.

I really like the GUI add-on!!!

--
I started YazFi and used "u" to update. All looked as if everything went OK.

Within the SSH terminal no issue reported. Went into the GUI and also had the error
404 Not Found
File not found.

I uninstalled YazFi then re-installed; problem fixed.

I did have the GUI open (don't remember which page) when I did the upgrade... perhaps unable to create the new path/page while GUI is open?

Anyway, quick and easy fix.

thx for the great work

Did you run u a second time after the first update? It is required. (apologies if you did, your message is unclear)

 

[Jack Yaz]

There's always 1 person who uses a weird default IP range! The "autofill" naively assumes it can +1 the octet. I will add a check for hitting the 255 limit and increase the previous octet accordingly.

@L&LD If you could update please (fix: https://github.com/jackyaz/YazFi/commit/97e7cc5ed4d9673fcca93c7767d20584ad5821d5) and blank out the _IPADDR for your non-used guests and re-open YazFi, can you please let me know if the new defaults work properly?

 

[L&LD]

@Jack Yaz, unfortunately not.

Choose an option:    1

YazFi: YazFi v4.0.0 starting up

YazFi: wl01_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl01_DHCPSTART is blank, setting to 2

YazFi: wl01_DHCPEND is blank, setting to 254

YazFi: wl01_DNS1 is blank, setting to 192.168.0.254

YazFi: wl01_DNS2 is blank, setting to 192.168.0.254

YazFi: wl02_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl02_DHCPSTART is blank, setting to 2

YazFi: wl02_DHCPEND is blank, setting to 254

YazFi: wl02_DNS1 is blank, setting to 192.168.255.254

YazFi: wl02_DNS2 is blank, setting to 192.168.255.254

YazFi: wl03_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl03_DHCPSTART is blank, setting to 2

YazFi: wl03_DHCPEND is blank, setting to 254

YazFi: wl03_DNS1 is blank, setting to 192.168.256.254

YazFi: wl03_DNS2 is blank, setting to 192.168.256.254

YazFi: wl11_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl11_DHCPSTART is blank, setting to 2

YazFi: wl11_DHCPEND is blank, setting to 254

YazFi: wl11_DNS1 is blank, setting to 192.168.257.254

YazFi: wl11_DNS2 is blank, setting to 192.168.257.254

YazFi: wl12_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl12_DHCPSTART is blank, setting to 2

YazFi: wl12_DHCPEND is blank, setting to 254

YazFi: wl12_DNS1 is blank, setting to 192.168.258.254

YazFi: wl12_DNS2 is blank, setting to 192.168.258.254

YazFi: wl13_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl13_DHCPSTART is blank, setting to 2

YazFi: wl13_DHCPEND is blank, setting to 254

YazFi: wl13_DNS1 is blank, setting to 192.168.259.254

YazFi: wl13_DNS2 is blank, setting to 192.168.259.254

YazFi: wl21_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl21_DHCPSTART is blank, setting to 2

YazFi: wl21_DHCPEND is blank, setting to 254

YazFi: wl21_DNS1 is blank, setting to 192.168.260.254

YazFi: wl21_DNS2 is blank, setting to 192.168.260.254

YazFi: wl22_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl22_DHCPSTART is blank, setting to 2

YazFi: wl22_DHCPEND is blank, setting to 254

YazFi: wl22_DNS1 is blank, setting to 192.168.261.254

YazFi: wl22_DNS2 is blank, setting to 192.168.261.254

YazFi: wl23_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl23_DHCPSTART is blank, setting to 2

YazFi: wl23_DHCPEND is blank, setting to 254

YazFi: wl23_DNS1 is blank, setting to 192.168.262.254

YazFi: wl23_DNS2 is blank, setting to 192.168.262.254

YazFi: No YazFi guests are enabled in the configuration file!

Press enter to continue...

 

[Jack Yaz]

@Jack Yaz, unfortunately not.

Choose an option:    1

YazFi: YazFi v4.0.0 starting up

YazFi: wl01_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl01_DHCPSTART is blank, setting to 2

YazFi: wl01_DHCPEND is blank, setting to 254

YazFi: wl01_DNS1 is blank, setting to 192.168.0.254

YazFi: wl01_DNS2 is blank, setting to 192.168.0.254

YazFi: wl02_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl02_DHCPSTART is blank, setting to 2

YazFi: wl02_DHCPEND is blank, setting to 254

YazFi: wl02_DNS1 is blank, setting to 192.168.255.254

YazFi: wl02_DNS2 is blank, setting to 192.168.255.254

YazFi: wl03_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl03_DHCPSTART is blank, setting to 2

YazFi: wl03_DHCPEND is blank, setting to 254

YazFi: wl03_DNS1 is blank, setting to 192.168.256.254

YazFi: wl03_DNS2 is blank, setting to 192.168.256.254

YazFi: wl11_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl11_DHCPSTART is blank, setting to 2

YazFi: wl11_DHCPEND is blank, setting to 254

YazFi: wl11_DNS1 is blank, setting to 192.168.257.254

YazFi: wl11_DNS2 is blank, setting to 192.168.257.254

YazFi: wl12_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl12_DHCPSTART is blank, setting to 2

YazFi: wl12_DHCPEND is blank, setting to 254

YazFi: wl12_DNS1 is blank, setting to 192.168.258.254

YazFi: wl12_DNS2 is blank, setting to 192.168.258.254

YazFi: wl13_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl13_DHCPSTART is blank, setting to 2

YazFi: wl13_DHCPEND is blank, setting to 254

YazFi: wl13_DNS1 is blank, setting to 192.168.259.254

YazFi: wl13_DNS2 is blank, setting to 192.168.259.254

YazFi: wl21_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl21_DHCPSTART is blank, setting to 2

YazFi: wl21_DHCPEND is blank, setting to 254

YazFi: wl21_DNS1 is blank, setting to 192.168.260.254

YazFi: wl21_DNS2 is blank, setting to 192.168.260.254

YazFi: wl22_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl22_DHCPSTART is blank, setting to 2

YazFi: wl22_DHCPEND is blank, setting to 254

YazFi: wl22_DNS1 is blank, setting to 192.168.261.254

YazFi: wl22_DNS2 is blank, setting to 192.168.261.254

YazFi: wl23_IPADDR is blank, setting to next available subnet above primary LAN subnet

YazFi: wl23_DHCPSTART is blank, setting to 2

YazFi: wl23_DHCPEND is blank, setting to 254

YazFi: wl23_DNS1 is blank, setting to 192.168.262.254

YazFi: wl23_DNS2 is blank, setting to 192.168.262.254

YazFi: No YazFi guests are enabled in the configuration file!

Press enter to continue...

That's definitely with the latest version?

 

[mcse]

Did you run u a second time after the first update? It is required. (apologies if you did, your message is unclear)

I (kinda) did.

Upgraded with "u", discovered error, then upgraded again with "uf", but error remained.

 

[L&LD]

@Jack Yaz, yes, I just checked again with amtm (no scripts need updates, there was one for Skynet earlier though...).

Before I did my test, I did 'u' and 'u' again and also a couple of 'uf' too.

I also just deleted the _IPADDR as instructed but when I saw no difference, I then deleted the start, end and DNS entries on each 'guest' too.

 

[Jack Yaz]

@Jack Yaz, yes, I just checked again with amtm (no scripts need updates, there was one for Skynet earlier though...).

Before I did my test, I did 'u' and 'u' again and also a couple of 'uf' too.

I also just deleted the _IPADDR as instructed but when I saw no difference, I then deleted the start, end and DNS entries on each 'guest' too.

Woops, I spotted the mistake. 2 mins!

 

[Jack Yaz]

@Jack Yaz, yes, I just checked again with amtm (no scripts need updates, there was one for Skynet earlier though...).

Before I did my test, I did 'u' and 'u' again and also a couple of 'uf' too.

I also just deleted the _IPADDR as instructed but when I saw no difference, I then deleted the start, end and DNS entries on each 'guest' too.

Try now please (after updating, of course!)

 

[kernol]

Updated perfectly - really enjoy the webUI page for config settings - great for noobs and non-coders like me .

 

[L&LD]

@Jack Yaz, thank you it works now (see last image).




But for anyone that has weird LAN IP's like myself, if they updated too fast, the DNS Entries won't match the IP Address given. Make sure to blank out all _IPADDR as instructed, then delete the start, end and DNS entries on each 'guest' too.

 

[Jack Yaz]

@Jack Yaz, thank you it works now (see last image).

View attachment 21481

View attachment 21482
But for anyone that has weird LAN IP's like myself, if they updated too fast, the DNS Entries won't match the IP Address given. Make sure to blank out all _IPADDR as instructed, then delete the start, end and DNS entries on each 'guest' too.

View attachment 21483
View attachment 21483

Only DNS should matter. Start and End are set to use 2 and 254 hardcoded. Which....means there's another problem with YazFi when using .254 for the router address

I'll have to fix that later, lunch break at work is over

 

[dave14305]

I'm taking a hiatus. You'll see the odd bug fix here there, but that's it for a while.

Five days later...

v4.0.0 is now available

I need to lookup the definition of "hiatus."

 

[Jack Yaz]

Five days later...

I need to lookup the definition of "hiatus."

I couldn't help it. Someone posted a WebUI teaser for another script, and I had to jump on the bandwagon.

 

[kernol]

Five days later...

I need to lookup the definition of "hiatus."

I couldn't help it. Someone posted a WebUI teaser for another script, and I had to jump on the bandwagon.

Be great for the two of you to get together for another "hiatus" - we just could see the blossoming of an awesome unbound bud .

 

[RMerlin]

Not directly related to YazFi, but something I've implemented last week.

More intuitive than hunting for the G flag (which wouldn't specify to which guest network instance the client is connected).

 

[FalconB]

v4.0.0 is now available
Changelog:

WebUI page to configure YazFi (requires Merlin 384.15)
Improvements to example/starting config file
Blanks are no longer permitted in the config file

You will need to run option u a second time after updating to download the new WebUI page. Config file will be backed up each run before being modified, so if something goes wrong when you first launch YazFi, please refer to the config.bak file in YazFi's directory in /jffs/addons to recover your settings

Hello @Jack Yaz and first off; thank you for your great work! I have a suggestion for what I think would be a better user experience. Now that we can see and configure YazFi from the router UI (wohoo!), I think it would be great (if possible) to add the SSID of each guest network below the "headlines" (Guest Network X) of both .24GHz and 5GHz in tha YazFi tab. If ones memory is short (like mine ) you now have to go back to the "Guest Network" tab to see which ssid corresponds to which guest network, and then back to the YazFi tab.

I haven't got a clue if it's even possible to implement it, or if it somehow is a bad idea, it's just a thought I had.

Not directly related to YazFi, but something I've implemented last week.

View attachment 21489

More intuitive than hunting for the G flag (which wouldn't specify to which guest network instance the client is connected).

@RMerlin The same goes for this (possible) feature/improvement, ie adding the actual SSID to the "Guest Network X" text...

Keep up your great work!!!

 

[RMerlin]

The same goes for this (possible) feature/improvement, ie adding the actual SSID to the "Guest Network X" text...

Shouldn't be a problem.

 

[Jack Yaz]

Shouldn't be a problem.

Seconded https://github.com/jackyaz/YazFi/commit/89a6b42452307a4dd4cea96533b2f949f02d85b1