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

[TheUntouchable]

Its blinking like hell so its tring to connect to the WLAN without success. Sadly even after a reboot of the device its now not possible to connect them again.. Somehow I don't see any DHCP messages in the log

 

[skeal]

Its blinking like hell so its tring to connect to the WLAN without success. Sadly even after a reboot of the device its now not possible to connect them again.. Somehow I don't see any DHCP messages in the log

I had the same issue. I'm not at home right now so I can't troubleshoot, sorry Jack.

 

[TheUntouchable]

I am using the beta 3 of 3.8.10 currently, will upgrade to final and test again

 

[Jack Yaz]

Its blinking like hell so its tring to connect to the WLAN without success. Sadly even after a reboot of the device its now not possible to connect them again.. Somehow I don't see any DHCP messages in the log

Make sure Hide DHCP/RA queries isn't set to Yes on LAN -DHCP Server

 

[TheUntouchable]

Looking much more better now:

Mar 28 21:31:55 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Mar 28 21:31:56 WLCEVENTD: wl0.1: Assoc 7C:49:EB:AF:92:0C
Mar 28 21:31:57 WLCEVENTD: wl0.1: Assoc 08:EA:40:9C:B1:27
Mar 28 21:31:57 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.1.224 7c:49:eb:af:92:0c
Mar 28 21:31:57 dnsmasq-dhcp[312]: DHCPNAK(wl0.1) 192.168.1.224 7c:49:eb:af:92:0c wrong network
Mar 28 21:32:00 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 7c:49:eb:af:92:0c
Mar 28 21:32:00 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 192.168.1.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c zhimi-humidifier-ca1_mibt98804778
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 192.168.1.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c zhimi-humidifier-ca1_mibt98804778
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27

And both got a .2.x IP address! So I will have to add the bounceclients thing in a startup script?

 

[Jack Yaz]

Looking much more better now:

Mar 28 21:31:55 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Mar 28 21:31:56 WLCEVENTD: wl0.1: Assoc 7C:49:EB:AF:92:0C
Mar 28 21:31:57 WLCEVENTD: wl0.1: Assoc 08:EA:40:9C:B1:27
Mar 28 21:31:57 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.1.224 7c:49:eb:af:92:0c
Mar 28 21:31:57 dnsmasq-dhcp[312]: DHCPNAK(wl0.1) 192.168.1.224 7c:49:eb:af:92:0c wrong network
Mar 28 21:32:00 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 7c:49:eb:af:92:0c
Mar 28 21:32:00 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 192.168.1.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c zhimi-humidifier-ca1_mibt98804778
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 192.168.1.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c zhimi-humidifier-ca1_mibt98804778
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27

And both got a .2.x IP address! So I will have to add the bounceclients thing in a startup script?

It's already called as part of YazFi's startup routine - maybe it's running too soon for your router?

 

[Jack Yaz]

It's already called as part of YazFi's startup routine - maybe it's running too soon for your router?

Tell a lie....

 

[Jack Yaz]

Looking much more better now:

Mar 28 21:31:55 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Mar 28 21:31:56 WLCEVENTD: wl0.1: Assoc 7C:49:EB:AF:92:0C
Mar 28 21:31:57 WLCEVENTD: wl0.1: Assoc 08:EA:40:9C:B1:27
Mar 28 21:31:57 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.1.224 7c:49:eb:af:92:0c
Mar 28 21:31:57 dnsmasq-dhcp[312]: DHCPNAK(wl0.1) 192.168.1.224 7c:49:eb:af:92:0c wrong network
Mar 28 21:32:00 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 7c:49:eb:af:92:0c
Mar 28 21:32:00 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 192.168.1.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c zhimi-humidifier-ca1_mibt98804778
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPDISCOVER(wl0.1) 192.168.1.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPOFFER(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.224 7c:49:eb:af:92:0c zhimi-humidifier-ca1_mibt98804778
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPREQUEST(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27
Mar 28 21:32:04 dnsmasq-dhcp[312]: DHCPACK(wl0.1) 192.168.2.110 08:ea:40:9c:b1:27

And both got a .2.x IP address! So I will have to add the bounceclients thing in a startup script?

Run uf in YazFi menu - hotfixed 3.1.0 released https://github.com/jackyaz/YazFi/commit/4aed91903680954bfe00bb4608a775edc0887f46

 

[TheUntouchable]

Thanks a lot! I updated with YazFi forceupdate as uf or fu was not recognizes in the menu

Sadly I will not be able to test it today as I have a different problem with my entware installation und stubby.. (seems that the /opt/etc/init.d scripts are not called after a reboot and therefore stubby is also not started..)

 

[Jack Yaz]

Thanks a lot! I updated with YazFi forceupdate as uf or fu was not recognizes in the menu

Sadly I will not be able to test it today as I have a different problem with my entware installation und stubby.. (seems that the /opt/etc/init.d scripts are not called after a reboot and therefore stubby is also not started..)

Ah - it's 3f for YazFi (head stuck in ntpMerlin mode) (uf coming in 3.2.0)

 

[TheUntouchable]

Okay, I had to fix/test that two problems.. I couldn't resist
Reinstalled entware and now init.d scripts are called after reboot, yeah!
Also the clients are now connected to the right network after a short time, thanks a lot

 

[thelonelycoder]

@Jack Yaz could you add an option to run force update in the menu?
I know there's 3f but I have this coming feature in amtm and it shows a minor update is available but YazFi does not do the md5sum check.

 

[Jack Yaz]

@Jack Yaz could you add an option to run force update in the menu?
I know there's 3f but I have this coming feature in amtm and it shows a minor update is available but YazFi does not do the md5sum check.

Can do (btw renaming it to uf in 3.2.0) - its just a case of exposing the menu option I take it?

Or I switch to md5 updates too (I try to avoid non-version number updates at all costs, so hopefully a forced update with be a rarity)

 

[thelonelycoder]

Can do (btw renaming it to uf in 3.2.0) - its just a case of exposing the menu option I take it?

Or I switch to md5 updates too (I try to avoid non-version number updates at all costs, so hopefully a forced update with be a rarity)

I do an md5 check if no version update is available. So I just had amtm telling me there's a minor update (which are md5 checks) and YazFi would tell me there's no update.
Unless you want me to drop the md5 check in amtm.

 

[Jack Yaz]

I do an md5 check if no version update is available. So I just had amtm telling me there's a minor update (which are md5 checks) and YazFi would tell me there's no update.
Unless you want me to drop the md5 check in amtm.

Can you post/PM the md5 update code please? I may as well drop it in so I'm working from the same rulebook!

 

[Zonkd]

First time user of YazFi! Installation worked on AC68U. Spent over an hour trying everything I can think of but cannot get LAN access to work on any guest network. What settings do you guys use? I assume applying YazFi config should override the Web GUI settings anyway?

My goal...
Primary: 192.168.1.1 + force redirect clients to use ntpMerlin, Diversion and Stubby
Guest 1: 192.168.2.1 + LAN access true + client isolation false + force filtering as above.
Guest 2: 192.168.3.1 + LAN access false + client isolation true + force filtering as above.

 

[Jack Yaz]

First time user of YazFi! Installation worked on AC68U. Spent over an hour trying everything I can think of but cannot get LAN access to work on any guest network. What settings do you guys use? I assume applying YazFi config should override the Web GUI settings anyway?

My goal...
Primary: 192.168.1.1 + force redirect clients to use ntpMerlin, Diversion and Stubby
Guest 1: 192.168.2.1 + LAN access true + client isolation false + force filtering as above.
Guest 2: 192.168.3.1 + LAN access false + client isolation true + force filtering as above.

What are the target devices on the LAN? i.e. how are you testing LAN access?

 

[binarybin]

Does anybody know what the iptables are to get a guest network to be able to query a local intranet dns server (pihole)?
Wireless Guest 2 - 2.4ghz is on, which is wl0.2, the dns server 192.168.1.2 is given out by the router, but nothing i try will allow a device connected to that wifi to be able to query the dns server because it is on the intranet side.

 

[Zonkd]

What are the target devices on the LAN? i.e. how are you testing LAN access?

Testing by trying to access web interface of NAS (192.168.1.5) and router while connected to guest network with dhcp ip address of (192.168.2.20)

 

[AitschPi]

Is there a way to use YazFi on multiple APs (Asus router with merlin, running in AccessPoint-Mode) and one Router (also Asus router with merlin) but limit the network transfer to

1. limit traffic guest-wifi to router
2. no LAN-access (like NAS, TV, printers,..)
   
3. DHCP from router

The buid in guest wifi supports DHCP and traffic from/to router but full LAN access. Limiting LAN access causes access to nothing (AP-mode).