Menu
What's new
By:
Filters Better Search

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

  • 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!

Hi Jack,

I updated to 4.1.1 directly from 4.0.5 and i noticed a couple of things.... i got a couple of syslog error and also the SSH session dropped when the the guest clients were bounced.......

Code: 
Jun 21 15:02:09 RT-AC68U-4690 YazFi: New version of YazFi available - updating to v4.1.1
Jun 21 15:02:11 RT-AC68U-4690 YazFi: New version of YazFi_www.asp downloaded
Jun 21 15:02:11 RT-AC68U-4690 YazFi: Mounting YazFi WebUI page as user1.asp
Jun 21 15:02:12 RT-AC68U-4690 YazFi: YazFi successfully updated - restarting firewall to apply update
Jun 21 15:02:12 RT-AC68U-4690 rc_service: service 26126:notify_rc restart_firewall
Jun 21 15:02:12 RT-AC68U-4690 custom_script: Running /jffs/scripts/service-event (args: restart firewall)
Jun 21 15:02:13 RT-AC68U-4690 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jun 21 15:02:13 RT-AC68U-4690 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Jun 21 15:02:14 RT-AC68U-4690 YazFi: Firewall restarted - sleeping 30s before running YazFi
Jun 21 15:02:44 RT-AC68U-4690 YazFi: YazFi v4.1.1 starting up
Jun 21 15:02:51 RT-AC68U-4690 YazFi: wl0.1 (SSID: TOmsKGuest) - sending all interface internet traffic over WAN interface
Jun 21 15:02:59 RT-AC68U-4690 YazFi: wl1.1 (SSID: TOmsKGuest_5G) - sending all interface internet traffic over WAN interface
Jun 21 15:03:05 RT-AC68U-4690 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Jun 21 15:03:16 RT-AC68U-4690 syslog: Error unlocking 5: 9 Bad file descriptor
Jun 21 15:03:16 RT-AC68U-4690 syslog: Error unlocking 0: 9 Bad file descriptor
Jun 21 15:03:19 RT-AC68U-4690 acsd: selected channel spec: 0x100a (10)
Jun 21 15:03:19 RT-AC68U-4690 acsd: Adjusted channel spec: 0x100a (10)
Jun 21 15:03:19 RT-AC68U-4690 acsd: selected channel spec: 0x100a (10)
Jun 21 15:03:19 RT-AC68U-4690 acsd: acs_set_chspec: 0x100a (10) for reason APCS_CSTIMER
Jun 21 15:03:21 RT-AC68U-4690 dropbear[27378]: Exit (tOmsK): Error reading: Connection timed out
Jun 21 15:03:22 RT-AC68U-4690 YazFi: YazFi v4.1.1 completed successfully
 
Last edited:
tomsk said:
Hi Jack,

I updated to 4.1.1 directly from 4.0.5 and i noticed a couple of things.... i got a couple of syslog error and also the SSH session dropped when the the guest clients were bounced.......

Code: 
Jun 21 15:02:09 RT-AC68U-4690 YazFi: New version of YazFi available - updating to v4.1.1
Jun 21 15:02:11 RT-AC68U-4690 YazFi: New version of YazFi_www.asp downloaded
Jun 21 15:02:11 RT-AC68U-4690 YazFi: Mounting YazFi WebUI page as user1.asp
Jun 21 15:02:12 RT-AC68U-4690 YazFi: YazFi successfully updated - restarting firewall to apply update
Jun 21 15:02:12 RT-AC68U-4690 rc_service: service 26126:notify_rc restart_firewall
Jun 21 15:02:12 RT-AC68U-4690 custom_script: Running /jffs/scripts/service-event (args: restart firewall)
Jun 21 15:02:13 RT-AC68U-4690 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jun 21 15:02:13 RT-AC68U-4690 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Jun 21 15:02:14 RT-AC68U-4690 YazFi: Firewall restarted - sleeping 30s before running YazFi
Jun 21 15:02:44 RT-AC68U-4690 YazFi: YazFi v4.1.1 starting up
Jun 21 15:02:51 RT-AC68U-4690 YazFi: wl0.1 (SSID: TOmsKGuest) - sending all interface internet traffic over WAN interface
Jun 21 15:02:59 RT-AC68U-4690 YazFi: wl1.1 (SSID: TOmsKGuest_5G) - sending all interface internet traffic over WAN interface
Jun 21 15:03:05 RT-AC68U-4690 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Jun 21 15:03:16 RT-AC68U-4690 syslog: Error unlocking 5: 9 Bad file descriptor
Jun 21 15:03:16 RT-AC68U-4690 syslog: Error unlocking 0: 9 Bad file descriptor
Jun 21 15:03:19 RT-AC68U-4690 acsd: selected channel spec: 0x100a (10)
Jun 21 15:03:19 RT-AC68U-4690 acsd: Adjusted channel spec: 0x100a (10)
Jun 21 15:03:19 RT-AC68U-4690 acsd: selected channel spec: 0x100a (10)
Jun 21 15:03:19 RT-AC68U-4690 acsd: acs_set_chspec: 0x100a (10) for reason APCS_CSTIMER
Jun 21 15:03:21 RT-AC68U-4690 dropbear[27378]: Exit (tOmsK): Error reading: Connection timed out
Jun 21 15:03:22 RT-AC68U-4690 YazFi: YazFi v4.1.1 completed successfully
Click to expand...
I've seen the bad file descriptor when networkmap gets killed, as far as I can tell it's harmless.

Is your SSH client wired or wireless? Looks like auto channel selection kicked in?
 
Jack Yaz said:
I've seen the bad file descriptor when networkmap gets killed, as far as I can tell it's harmless.

Is your SSH client wired or wireless? Looks like auto channel selection kicked in?
Click to expand...
Yeah its wireless.... strange it shouldn't be on auto... thats what all that acsd stuff was i guess....thanks will adjust that.
 
@Jack Yaz
After updating to 4.1.1 on a RT-AC68U running Merlin 384.17, noticed the YazFi GUI page/tab now looks like the attached screen shot. It has the text; "Feature expansion of guest WiFi networks on AsusWRT-Merlin." and an Apply button. Should users be selecting the Apply button in order to get to the YazFi GUI configuration page?
 

Attachments

  • Screenshot_2020-06-21 YazFi.jpg
    Screenshot_2020-06-21 YazFi.jpg
    38.2 KB · Views: 188
bennor said:
@Jack Yaz
After updating to 4.1.1 on a RT-AC68U running Merlin 384.17, noticed the YazFi GUI page/tab now looks like the attached screen shot. It has the text; "Feature expansion of guest WiFi networks on AsusWRT-Merlin." and an Apply button. Should users be selecting the Apply button in order to get to the YazFi GUI configuration page?
Click to expand...
No, suggests something has gone wrong with the page. Can you run option uf and then try again?

If it still doesn't load, check the browser console
 
Jack Yaz said:
Can you run option uf and then try again?
Click to expand...
Forcing the update did the trick. GUI pages loads now. :)

On a different subject, it's I think been asked in the past about guests using IP addresses from the main pool of IP addresses like the Asus/Merlin Guest settings typical use (when YazFi is not installed). User SammyG inquired about it last week. I've tried to find the past posts on the subject as I swear I read a few, but not finding them. Any particular reason why the YazFi guests cannot use IP addresses from the router's main/default IP address pool? Was it a coding decision or is there something under the hood in the router firmware that prevents it?
 
bennor said:
Forcing the update did the trick. GUI pages loads now. :)

On a different subject, it's I think been asked in the past about guests using IP addresses from the main pool of IP addresses like the Asus/Merlin Guest settings typical use (when YazFi is not installed). User SammyG inquired about it last week. I've tried to find the past posts on the subject as I swear I read a few, but not finding them. Any particular reason why the YazFi guests cannot use IP addresses from the router's main/default IP address pool? Was it a coding decision or is there something under the hood in the router firmware that prevents it?
Click to expand...
Decision as part of the core basis of the project. Not sure why you would want to use IPs from the LAN pool?
 
Jack Yaz said:
Decision as part of the core basis of the project. Not sure why you would want to use IPs from the LAN pool?
Click to expand...
Was just curious as that other person's post got me wondering. LOL

Only reasons I can think of would be to have the ability to use fixed/static IP addresses or just a general IP address that are in the main pool, and I assume would then be picked up by the network map section, where as currently one has to use the wifi log to see the assigned IP addresses for the YazFi guests, and if one wants to use static IP address they have to follow the cumbersome methods discussed earlier in the thread.

The issue, if I remember right, occasionally comes up in conjunction with people using Pi-Hole. If one configures Pi-Hole to poll the router for the device name (used by the IP address) the router doesn't return the YazFi Guest clients because the IP address used by them are not found in the client IP address pool (obviously a problem with the router's firmware by not including IP address ranges used outside the main pool IP address).

So for Pi-Hole users, if they want to have Pi-Hole list the device name they generally had to manually create a Host list on the Pi-Hole device with the YazFi Guest client's IP addresses. This obviously necessitates creating static IP addresses on the router so the Pi-Hole correctly polls the right YazFi guest client every time. I remember one person commenting that this process it (keeping two sets of IP lists, one on the router, one on the Pi-Hole device) was too cumbersome to use as they didn't want to edit both lists every time they added or removed a YazFi Guest client.

I don't add or remove WiFi guests often so maintaining two lists isn't an issue for me at this point. :)
 
bennor said:
Was just curious as that other person's post got me wondering. LOL

Only reasons I can think of would be to have the ability to use fixed/static IP addresses or just a general IP address that are in the main pool, and I assume would then be picked up by the network map section, where as currently one has to use the wifi log to see the assigned IP addresses for the YazFi guests, and if one wants to use static IP address they have to follow the cumbersome methods discussed earlier in the thread.

The issue, if I remember right, occasionally comes up in conjunction with people using Pi-Hole. If one configures Pi-Hole to poll the router for the device name (used by the IP address) the router doesn't return the YazFi Guest clients because the IP address used by them are not found in the client IP address pool (obviously a problem with the router's firmware by not including IP address ranges used outside the main pool IP address).

So for Pi-Hole users, if they want to have Pi-Hole list the device name they generally had to manually create a Host list on the Pi-Hole device with the YazFi Guest client's IP addresses. This obviously necessitates creating static IP addresses on the router so the Pi-Hole correctly polls the right YazFi guest client every time. I remember one person commenting that this process it (keeping two sets of IP lists, one on the router, one on the Pi-Hole device) was too cumbersome to use as they didn't want to edit both lists every time they added or removed a YazFi Guest client.

I don't add or remove WiFi guests often so maintaining two lists isn't an issue for me at this point. :)
Click to expand...
does this help re. separate lists? https://github.com/jackyaz/YazFi/wi...t-name-resolutionarp-settings-for-lan-clients
 
Jack Yaz said:
v4.1.1 is now available
Changelog:
Code: 
CHANGED: Flush arp and kill networkmap (watchdog restarts it) when bouncing clients
CHANGED: Increase space for hostnames in Status output
FIXED: Fix hostname lookup in DHCP leases (grep -i)
UNTESTED: WebUI may now work on John's fork
Click to expand...
great job with your recent updates ! Thanks a lot for your hard work.!
 
@Jack Yaz
on the "System log/Port Forwarding" page, under the "Virtual servers" table, i have:

Source Proto Port range Redirect to Local Port Chain
ALL ALL <empty> 192.168.50.1 <empty> YazFiDNSFILTER
ALL ALL <empty> 192.168.50.1 <empty> YazFiDNSFILTER

are these entries expected/correct?

on my YazFi page for the 2 guest wifi i use, i do have ForceDNS=192.168.50.1
but the entries above look rather, 'generic' ?

thanks
 
Last edited:
Jack Yaz said:
v4.1.1 is now available
Changelog:
Code: 
CHANGED: Flush arp and kill networkmap (watchdog restarts it) when bouncing clients
CHANGED: Increase space for hostnames in Status output
FIXED: Fix hostname lookup in DHCP leases (grep -i)
UNTESTED: WebUI may now work on John's fork
Click to expand...

Hello,

Since updating to 4.1.1 I am seeing the following in my log:
Code: 
Jun 24 06:20:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 06:30:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 06:30:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 06:40:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 06:40:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 06:50:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 06:50:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:00:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:00:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:10:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:10:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:20:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:20:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:30:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:30:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:40:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:40:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:50:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:50:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 08:00:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules

I've tried force updating - I'm not sure what else to try to fix it. Can you help?
 
joe68000 said:
Hello,

Since updating to 4.1.1 I am seeing the following in my log:
Code: 
Jun 24 06:20:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 06:30:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 06:30:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 06:40:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 06:40:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 06:50:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 06:50:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:00:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:00:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:10:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:10:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:20:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:20:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:30:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:30:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:40:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:40:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 07:50:00 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 07:50:00 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 08:00:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules

I've tried force updating - I'm not sure what else to try to fix it. Can you help?
Click to expand...
something is going wrong if the firewall rules aren;t applying. can you share a full syslog please?
 
Hi, thanks... I run scribe so what other logs do you need to see? Here is some preceding info.

Code: 
Jun 24 08:43:13 RT-AC5300 rc_service: httpds 390:notify_rc restart_vpnclient1
Jun 24 08:43:13 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: restart vpnclient1)
Jun 24 08:43:14 RT-AC5300 YazFi: VPN client (re)started - sleeping 15s before running YazFi
Jun 24 08:43:49 RT-AC5300 rc_service: httpds 390:notify_rc stop_vpnclient1
Jun 24 08:43:49 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: stop vpnclient1)
Jun 24 08:44:09 RT-AC5300 rc_service: httpds 390:notify_rc start_vpnclient2
Jun 24 08:44:09 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: start vpnclient2)
Jun 24 08:44:10 RT-AC5300 YazFi: VPN client (re)started - sleeping 15s before running YazFi
Jun 24 08:44:14 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5 init)
Jun 24 08:44:14 RT-AC5300 YazFi: Firewall restarted - sleeping 30s before running YazFi
Jun 24 08:44:17 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5)
Jun 24 08:44:17 RT-AC5300 YazFi: Lock file found (age: 3 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:31 RT-AC5300 rc_service: httpds 390:notify_rc restart_vpnclient2
Jun 24 08:44:31 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: restart vpnclient2)
Jun 24 08:44:32 RT-AC5300 YazFi: VPN client (re)started - sleeping 15s before running YazFi
Jun 24 08:44:33 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5 init)
Jun 24 08:44:33 RT-AC5300 YazFi: Firewall restarted - sleeping 30s before running YazFi
Jun 24 08:44:33 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5 init)
Jun 24 08:44:33 RT-AC5300 YazFi: Lock file found (age: 0 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:37 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.3.10.10 10.3.10.9 init)
Jun 24 08:44:38 RT-AC5300 YazFi: Lock file found (age: 5 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:40 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.3.10.10 10.3.10.9)
Jun 24 08:44:40 RT-AC5300 YazFi: Lock file found (age: 7 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:44 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 08:45:03 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 08:50:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 08:50:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 09:00:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
 
joe68000 said:
Hi, thanks... I run scribe so what other logs do you need to see? Here is some preceding info.

Code: 
Jun 24 08:43:13 RT-AC5300 rc_service: httpds 390:notify_rc restart_vpnclient1
Jun 24 08:43:13 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: restart vpnclient1)
Jun 24 08:43:14 RT-AC5300 YazFi: VPN client (re)started - sleeping 15s before running YazFi
Jun 24 08:43:49 RT-AC5300 rc_service: httpds 390:notify_rc stop_vpnclient1
Jun 24 08:43:49 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: stop vpnclient1)
Jun 24 08:44:09 RT-AC5300 rc_service: httpds 390:notify_rc start_vpnclient2
Jun 24 08:44:09 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: start vpnclient2)
Jun 24 08:44:10 RT-AC5300 YazFi: VPN client (re)started - sleeping 15s before running YazFi
Jun 24 08:44:14 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5 init)
Jun 24 08:44:14 RT-AC5300 YazFi: Firewall restarted - sleeping 30s before running YazFi
Jun 24 08:44:17 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5)
Jun 24 08:44:17 RT-AC5300 YazFi: Lock file found (age: 3 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:31 RT-AC5300 rc_service: httpds 390:notify_rc restart_vpnclient2
Jun 24 08:44:31 RT-AC5300 custom_script: Running /jffs/scripts/service-event (args: restart vpnclient2)
Jun 24 08:44:32 RT-AC5300 YazFi: VPN client (re)started - sleeping 15s before running YazFi
Jun 24 08:44:33 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5 init)
Jun 24 08:44:33 RT-AC5300 YazFi: Firewall restarted - sleeping 30s before running YazFi
Jun 24 08:44:33 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.67.10.6 10.67.10.5 init)
Jun 24 08:44:33 RT-AC5300 YazFi: Lock file found (age: 0 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:37 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.3.10.10 10.3.10.9 init)
Jun 24 08:44:38 RT-AC5300 YazFi: Lock file found (age: 5 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:40 RT-AC5300 custom_script: Running /jffs/scripts/openvpn-event (args: tun12 1500 1558 10.3.10.10 10.3.10.9)
Jun 24 08:44:40 RT-AC5300 YazFi: Lock file found (age: 7 seconds) - stopping to prevent duplicate runs
Jun 24 08:44:44 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 08:45:03 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 08:50:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Jun 24 08:50:01 RT-AC5300 YazFi: YazFi v4.1.1 starting up
Jun 24 09:00:01 RT-AC5300 YazFi:  firewall rules not detected during persistence check, re-applying rules
Click to expand...
the messages log in that case please
 
Do you have instructions how to rollback to an earlier version. I'm having problems with the latest version on clients list and wanted to see if 4.0.5 will fix it.

When a guest connects to a different subnet my client list in network map changes to 0.
 
Last edited:
bmn1 said:
Do you have instructions how to rollback to an earlier version. I'm having problems with the latest version on clients list and wanted to see if 4.0.5 will fix it.

When a guest connects to a different subnet my client list in network map changes to 0.
Click to expand...
Expected, wait 30s or so and the network map should repopulate
 
You must log in or register to reply here.

Similar threads

Astronautspiff
YazFi GUI Tab not showing up under Guest Networks Page
Replies
3
Views
373
Tech9
Tech9
M
YazFi Problem with YazFi
Replies
19
Views
1K
bennor
B
Jack Yaz
YazFi YazFi v4.x - continued
6 7 8
Replies
147
Views
25K
fotingo
F
T
Make IoT devices on one-way-to-guest YazFi VLANs discoverable on main LAN
Replies
8
Views
2K
fotingo
F
B
Yazfi: VPN Server for guest network access only
Replies
10
Views
1K
jrmathis
jrmathis
Similar threads
Thread starter Title Forum Replies Date
J YazFi Can't make Yazfi working with Wireguard Asuswrt-Merlin AddOns 13
Z YazFi YazFi on Subnet Router Asuswrt-Merlin AddOns 10
Siff Solved YazFi Offline Install Asuswrt-Merlin AddOns 3
Astronautspiff YazFi GUI Tab not showing up under Guest Networks Page Asuswrt-Merlin AddOns 3
M YazFi Problem with YazFi Asuswrt-Merlin AddOns 19
macster2075 YazFi YazFi on AC86U Asuswrt-Merlin AddOns 3
SevenFactors YazFi YazFi 4.4.4 GUI Page Becomes Unscrollable on Merlin 386.14 Asuswrt-Merlin AddOns 3
novusB YazFi Issues with YazFi - Gnuton - RT-AX58U_V2 3004.388.7_1-gnuton1 Asuswrt-Merlin AddOns 1
P YazFi YazFi on GT-BE98 Pro Asuswrt-Merlin AddOns 15
R YazFi YazFi and Port forwarding to get to server? Asuswrt-Merlin AddOns 2

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!

Members online

Total: 749 (members: 12, guests: 737)
Top