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

[bearever]

Is VPN client on yazfi OpenVPN or PPTP?
Sorry i'm newbie.

Openvpn


Sent from my iPhone using Tapatalk Pro

 

[Jack Yaz]

YazFi v3.0.0 has been released!

Changelog:

Add menu system for YazFi
Various bugfixes and improvements

To update:

/jffs/scripts/YazFi update

Very many thanks to @cmkelley , @HuskyHerder , @infra_red_dude , @L&LD and @Seamaster for helping test this new release, and providing very valuable feedback

 

[thelonelycoder]

YazFi v3.0.0 has been released!

Changelog:

Add menu system for YazFi
Various bugfixes and improvements

To update:

/jffs/scripts/YazFi update

Very many thanks to @cmkelley , @HuskyHerder , @infra_red_dude , @L&LD and @Seamaster for helping test this new release, and providing very valuable feedback

Welcome YazFi to amtm 1.8!

 

[thelonelycoder]

A force update option would be nice in the menu.
I now use md5sum to compare versions in amtm. This will tell the user if an update is available even if there's no version change.

 

[Jack Yaz]

A force update option would be nice in the menu.
I now use md5sum to compare versions in amtm. This will tell the user if an update is available even if there's no version change.

There's a hidden one (for now) - type 3f

 

[Bubbagump210]

Running an RT-AC68U with Merlin 384.9 and YazFi 3.0.0. It seems the guest network loses DHCP abilities after the initial lease. Subsequent renewals seemingly fail and clients are left dead in the water. Aka, reboot the router and the world is happy. An hour later all the guests are offline and only a reboot fixes the issue. Restarting Yaz using option 1 doesn't fix it either. When using the new option to show connected clients, all the MACs show up, but no IPs are assigned. Odd. Any thoughts or debug I can send?

 

[Jack Yaz]

Running an RT-AC68U with Merlin 384.9 and YazFi 3.0.0. It seems the guest network loses DHCP abilities after the initial lease. Subsequent renewals seemingly fail and clients are left dead in the water. Aka, reboot the router and the world is happy. An hour later all the guests are offline and only a reboot fixes the issue. Restarting Yaz using option 1 doesn't fix it either. When using the new option to show connected clients, all the MACs show up, but no IPs are assigned. Odd. Any thoughts or debug I can send?

Is there anything in the system log around the DHCP renewal time?

 

[Bubbagump210]

Is there anything in the system log around the DHCP renewal time?

Seemingly not. And I may be wrong about it being a DHCP issue. I am using /tmp/syslog.log FWIW as nothing else stands out.

The only log entries are things like

Feb 11 14:44:49 WLCEVENTD: wl0.1: Disassoc 18:B4:30:6C:09:7F
Feb 11 14:45:03 WLCEVENTD: wl0.1: Assoc 18:B4:30:6C:09:7F

It may well be a layer 2 wifi issue? Happy to post whatever other info is useful.

 

[Jack Yaz]

Seemingly not. And I may be wrong about it being a DHCP issue. I am using /tmp/syslog.log FWIW as nothing else stands out.

The only log entries are things like

Feb 11 14:44:49 WLCEVENTD: wl0.1: Disassoc 18:B4:30:6C:09:7F
Feb 11 14:45:03 WLCEVENTD: wl0.1: Assoc 18:B4:30:6C:09:7F

It may well be a layer 2 wifi issue? Happy to post whatever other info is useful.

Can you check what cat /etc/dnsmasq.conf looks like at the time?

What settings do the clients show for their IP, gateway etc.? Can the router ping them?

 

[Bubbagump210]

Can you check what cat /etc/dnsmasq.conf looks like at the time?

What settings do the clients show for their IP, gateway etc.? Can the router ping them?

I cannot ping the devices from the router. I was also mistaken, the devices DO show as having proper DHCP leases on themselves.

pid-file=/var/run/dnsmasq.pid
user=nobody
bind-dynamic
interface=br0
interface=pptp*
no-dhcp-interface=pptp*
no-resolv
servers-file=/tmp/resolv.dnsmasq
no-poll
no-negcache
cache-size=1500
min-port=4096
domain=local.net
expand-hosts
bogus-priv
domain-needed
local=/local.net/
dhcp-range=lan,192.168.178.50,192.168.178.100,255.255.255.0,86400s
dhcp-option=lan,3,192.168.178.1
dhcp-option=lan,6,192.168.178.5
dhcp-option=lan,15,local.net
dhcp-option=lan,44,192.168.178.1
dhcp-option=lan,252,"\n"
dhcp-authoritative
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore
dhcp-script=/sbin/dhcpc_lease
script-arp



### Start of script-generated configuration for interface wl0.1 ###
interface=wl0.1
dhcp-range=wl0.1,192.168.180.50,192.168.180.100,255.255.255.0,43200s
dhcp-option=wl0.1,3,192.168.180.1
dhcp-option=wl0.1,6,192.168.178.5,192.168.178.5
### End of script-generated configuration for interface wl0.1 ###

 

[Jack Yaz]

I cannot ping the devices from the router. I was also mistaken, the devices DO show as having proper DHCP leases on themselves.

pid-file=/var/run/dnsmasq.pid
user=nobody
bind-dynamic
interface=br0
interface=pptp*
no-dhcp-interface=pptp*
no-resolv
servers-file=/tmp/resolv.dnsmasq
no-poll
no-negcache
cache-size=1500
min-port=4096
domain=local.net
expand-hosts
bogus-priv
domain-needed
local=/local.net/
dhcp-range=lan,192.168.178.50,192.168.178.100,255.255.255.0,86400s
dhcp-option=lan,3,192.168.178.1
dhcp-option=lan,6,192.168.178.5
dhcp-option=lan,15,local.net
dhcp-option=lan,44,192.168.178.1
dhcp-option=lan,252,"\n"
dhcp-authoritative
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore
dhcp-script=/sbin/dhcpc_lease
script-arp



### Start of script-generated configuration for interface wl0.1 ###
interface=wl0.1
dhcp-range=wl0.1,192.168.180.50,192.168.180.100,255.255.255.0,43200s
dhcp-option=wl0.1,3,192.168.180.1
dhcp-option=wl0.1,6,192.168.178.5,192.168.178.5
### End of script-generated configuration for interface wl0.1 ###

Hm, strange that you cannot ping. Is the device able to connect successfully to the main wifi network? (just trying to rule out a generic wireless issue e.g. airtime fairness should be disabled)

 

[Bubbagump210]

Hm, strange that you cannot ping. Is the device able to connect successfully to the main wifi network? (just trying to rule out a generic wireless issue e.g. airtime fairness should be disabled)

This is multiple devices just for clarity. If I remove YazFi, things work perfectly fine on the plain old guest wireless. Like a dope I upgraded to 384.9 and YazFi 3.0.0 at the same time which of course makes it tough to say what broke what. Also, this was working fine on 2.x. Is there a way to reinstall the last in the 2.x (Was it 2.3.8?) just to rule out YazFi vs firmware? If YazFi 2.x works on 384.9, that tells us something. I see a commit for 2.3.7 and it seems you don't use releases - otherwise I'd just tweak the curl section myself.

 

[JohnSmith]

OK - that setting seems broken perhaps (@RMerlin ?) - I'll patch YazFi to ignore it for the AX88U

Just an FYI that on my AC3100 I previously used this script https://www.snbforums.com/threads/different-dhcp-range-of-different-wlan.37361/#post-306868 for my guest wifi network, and it works, so I tested it on my RT-AX88U, and it works as well, so not sure if there is any logic in this that you would incorporate into YazFi to make it work with the RT-AX88U.

 

[orion44]

Testing the new menu and it's not showing the hostname or IP address of my device (Raspberry PI) connected to the guest network.

I've confirmed the device is connected and the DHCP process completed successfully.
Feb 12 10:17:55 192.168.1.1 Feb 12 10:17:48 dnsmasq-dhcp[343]: DHCPACK(wl0.1) 172.16.1.171 b8:27:eb:b3:d8:33 raspberrypi

 

[Jack Yaz]

This is multiple devices just for clarity. If I remove YazFi, things work perfectly fine on the plain old guest wireless. Like a dope I upgraded to 384.9 and YazFi 3.0.0 at the same time which of course makes it tough to say what broke what. Also, this was working fine on 2.x. Is there a way to reinstall the last in the 2.x (Was it 2.3.8?) just to rule out YazFi vs firmware? If YazFi 2.x works on 384.9, that tells us something. I see a commit for 2.3.7 and it seems you don't use releases - otherwise I'd just tweak the curl section myself.

https://gist.githubusercontent.com/...9b6597f5d239869145e8b5ebcedf715597a78b7/YazFi

 

[Jack Yaz]

Just an FYI that on my AC3100 I previously used this script https://www.snbforums.com/threads/different-dhcp-range-of-different-wlan.37361/#post-306868 for my guest wifi network, and it works, so I tested it on my RT-AX88U, and it works as well, so not sure if there is any logic in this that you would incorporate into YazFi to make it work with the RT-AX88U.

With YazFi 3.0 try setting clientisolation to false

 

[JohnSmith]

With YazFi 3.0 try setting clientisolation to false

I can confirm that YazFi 3.0.0 works with the RT-AX88U with Merlin V384.9 Final as a Guest Wireless Network, and I did set client isolation to false, thanks Jack Yaz!

 

[L&LD]

Testing the new menu and it's not showing the hostname or IP address of my device (Raspberry PI) connected to the guest network.
View attachment 16234

I've confirmed the device is connected and the DHCP process completed successfully.
Feb 12 10:17:55 192.168.1.1 Feb 12 10:17:48 dnsmasq-dhcp[343]: DHCPACK(wl0.1) 172.16.1.171 b8:27:eb:b3:d8:33 raspberrypi

You're just querying for new clients faster than it has logged them.

Wait a minute or so and all will be shown as expected.

 

[SMS786]

Thanks again for the great script @Jack Yaz, the UI functionality is a great add!

Quick question: Do the YazFi settings persist after a router reboot, or does the config file need to be manually reprocessed after a reboot?

 

[L&LD]

Thanks again for the great script @Jack Yaz, the UI functionality is a great add!

Quick question: Do the YazFi settings persist after a router reboot, or does the config file need to be manually reprocessed after a reboot?

It persists for me.