What's new

YazFi YazFi Lite with Router in AP Mode?

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

drewski22785

Occasional Visitor
Hi @Jack Yaz , your addon has been outstanding, especially for my recent needs.

Are there any plans to implement a lite version of your addon to operate in AP Mode? Most of the functions wouldn't work but I think it would be a great function to add. It would allow soft handoff between SSID's on guest for example.

Right now I converted my two AP Mode routers back to Routed mode but had to do some hacks to get it to function similar for non guest SSID's. It wasn't too complicated to get working but still a hack none the less.

I would be more than happy to help with it and test since I have a multi AP mode environment.

In another post which I tag'd incorrectly so you probably never saw I implemented a multi-vpn capability via vpn director to allow for failover between vpns. It's simple but it looks at all vpn's that are up and adds the appropriate rules etc... The failover is based on TUN # obviously since that is how vpn director makes its decision. I did not make it for the old version though...
 
Last edited:
There isn't a YazFi member present in these forums. :)

@Jack Yaz is who you need to direct your post, to.

YazFi can't be used when the router isn't in router mode.
 
There isn't a YazFi member present in these forums. :)

@Jack Yaz is who you need to direct your post, to.

YazFi can't be used when the router isn't in router mode.
You are right, current state and full featured it definitely can't. But a lite version I think would be possible, just Guest IP/SSID setup.

On the AP mode router, I was able to separate a guest ssid, add an ip to it, and ping the router in Router Mode which had a corresponding SSID with the same subnet. I did add these into the br0 so they would be reachable and had to do secondary ip's on the br0's. Clearly this isn't ideal but it shows multi subnet connectivity is viable.

I did attempt to setup dhcp with no luck, either connecting through the AP router (got the local brn IP) or on the Full router wasn't getting any ip. If there is a way to properly identify the dhcp request that is on the AP at the Full Router this becomes very much workable. What is the best way to identify that traffic I am not sure, some kind of unique tag maybe, possibly enabling dhcp and setting up some kind of relay to the Full router?

Technically, I think it is very much possible, and yes we are probably stepping into some of the AIMESH territory because now the routers will likely have to communicate for this to work, pass config files potentially etc...
 
YazFi relies on the firewall and DHCP to achieve most/all of its features, so fundamentally conflicts with AP mode. A future version may be compatible, but its not a small task.
 
YazFi relies on the firewall and DHCP to achieve most/all of its features, so fundamentally conflicts with AP mode. A future version may be compatible, but its not a small task.
Is this possible with 4.4.4? I currently have two AX86U, one in AP-mode, and would like that one to use Yazfi fo my IoT.
 
Is this possible with 4.4.4? I currently have two AX86U, one in AP-mode, and would like that one to use Yazfi fo my IoT.
You are replying to a post from 2021. Jack Yaz has previously indicated, on Jul 8, 2022, they are no longer actively developing YazFi. Another user (@Martinski) has taken up fixing certain specific issues with YazFi. But in general YazFi still appears to rely on the firewall and IPTables. One and or both of which may be disabled when the router is configured for AP or AiMesh mode. As such YazFi generally only works on the main router's WiFi and does not extend to the AP or AiMesh nodes attached to the main router.
 
Oh nuts!! I had no idea he has moved on... I remember 4.4.4 was released not THAT long ago (i think), so i assumed Jack Jaz was still developing it. I had no reason to believe he wasn't the main developer anymore, as I don't visit these forums that frequently. Thanks for notifying me.

I guess getting the AX86uU PRO and Guest Network Pro is the way forward then, since YazFi probably is on maintenance-mode / life-support?
 
I guess getting the AX86uU PRO and Guest Network Pro is the way forward then, since YazFi probably is on maintenance-mode / life-support?
Note that the Guest Network Pro feature of the 3.0.0.6.x firmware of the WRT5.0 supported Asus routers (which includes the RT-AX86U Pro) does not generally extend to non WRT5.0/Guest Network Pro supported routers. This generally means Guest Network Pro feature won't be available on your existing RT-AX86U's if you plan on using those routers as AiMesh nodes or as AP nodes down stream from a RT-AX86U Pro. Further Asus-Merlin 3006.102.x firmware (and Gnuton 3006.x firmware) only supports a few routers at this time. The RT-AX86U Pro is not currently supported by the Asus-Merlin 3006.102.x firmware.

The Guest Network Pro feature while it generally works as advertised by ASUS, has its own quirks and limitations. I wound up back on YazFi/3004.388.8_2 firmware on a RT-AX86U Pro because Guest Network Pro had some limitations/quirks in my use case. Its a case of Guest Network Pro (at its current development) may work for one person's use case, but not another person's use case.

Edit to add: See below, one person is reporting they have Guest Network Pro and VLAN working on their non pro nodes. I couldn't get it working properly in my quick testing with an RT-AX86U Pro and a couple of RT-AC68U nodes when the stable Asus 3006.x firmware was initially released for that AX86U Pro router several months ago. This may be a case of works for you but not me kind of thing, I would suggest one read through the various posts on Guest Network Pro/VLAN and AiMesh/AP nodes (use forum search) to see what others are saying and what issues they may be experiencing if any.
 
Last edited:
This generally means Guest Network Pro feature won't be available on your existing RT-AX86U's if you plan on using those routers as AiMesh nodes or as AP nodes down stream from a RT-AX86U Pro.
Ah for crying out loud!!!! So in a couple years time I'm stuck with ywo paperweights, unless it's possible to run the Guest Network Pro just on the ax86u pro, and let all the IoT connect to that one on the wideband 2.4Ghz band, and let the non-pro ax86u's handle the main network on 5Ghz in AP-mode. That would work, wouldn't it? I'm sure in a couple years time AsusWRT 5.0 will have matured?
 
Note that the Guest Network Pro feature of the 3.0.0.6.x firmware of the WRT5.0 supported Asus routers (which includes the RT-AX86U Pro) does not generally extend to non WRT5.0/Guest Network Pro supported routers. This generally means Guest Network Pro feature won't be available on your existing RT-AX86U's if you plan on using those routers as AiMesh nodes or as AP nodes down stream from a RT-AX86U Pro. Further Asus-Merlin 3006.102.x firmware (and Gnuton 3006.x firmware) only supports a few routers at this time. The RT-AX86U Pro is not currently supported by the Asus-Merlin 3006.102.x firmware.
This is simply not true! I have GT-BE98 Pro as primary router with GT-AXE16000 and RT-AX86U as AiMesh nodes (among others). Guest Network Pro extends its features to these nodes just fine, including VLANs.
 
and RT-AX86U as AiMesh nodes (among others). Guest Network Pro extends its features to these nodes just fine, including VLANs
I’d be very interested to hear about the details of this.

Both @bennor and @Tech9 have noted for some time that e.g. only AsusWRT 5.0 devices with AsusWRT 5.0-based nodes can propagate all Guest Wi-Fi (presumably using VLANs) to the nodes, vs the current Guest Network 1 (GN1 only), even for AsusWRT 5.0 Routers but with AsusWRT 4.0 Nodes. Or am I misunderstanding what is meant by VLAN features here?

If you’re correct and I really hope you are, this would be great!
 
Last edited:
This is simply not true! I have GT-BE98 Pro as primary router with GT-AXE16000 and RT-AX86U as AiMesh nodes (among others). Guest Network Pro extends its features to these nodes just fine, including VLANs.
If it worked for you, good. Didn't work for me in some quick testing with RT-AC68U AiMesh nodes. Had various issues and node drops. Features were not extending to the nodes for what ever reason in my quick testing. Shrugs.
 
Last edited:
I’d be very interested to hear about the details of this.

Both @bennor and @Tech9 have noted for some time that e.g. only AsusWRT 5.0 devices with AsusWRT 5.0:-based nodes can propagate all Guest Wi-Fi (presumably using VLANs) to the nodes, vs the current Guest Network 1 (GN1 only), even for AsusWRT 5.0 Routers but with AsusWRT 4.0 Nodes. Or am I misunderstanding what is meant by VLAN features here?

If you’re correct and I really hope you are, this would be great!
Primary network available on all AiMesh nodes. You are able to push two (2) guest networks to each AiMesh node per frequency (2.4, 5, and 6 GHz). VLANs are pushed out as well. It's basically mix and match to fit your needs.
 
I would like to see an example of Guest Network Pro propagation to non-Pro AiMesh node.
@Tech9: Here you go...

I have GT-BE98 Pro running latest Merlin 3006.102.1 with the following AiMesh nodes:
  1. GT-AX6000 with latest Asus 3.0.0.6.102_34791-g92f56f9_385-g2830d (aka study)
  2. GT-AX6000 with latest Asus 3.0.0.6.102_34791-g92f56f9_385-g2830d (aka basement)
  3. GT-AXE16000 with latest Merlin 3004.388.8_2 (aka office)
  4. RT-AX86U with latest Merlin 3004.388.8_2 (aka garage)
Primary wired/wifi network is 192.168.222.0/24, available on all nodes.

For Guest Network Pro guest networks, each with its own VLAN (Access Internet disabled for all):
  • IoT_24: 2.4 GHz IoT devices; VLAN 192.168.52.0/24 (primary and nodes study/basement/garage)
  • IoT_5: 5 GHz IoT devices; VLAN 192.168.53.0/24 (primary and nodes study/basement/garage)
  • Guests: 2.4/5/6 GHz guest network; VLAN 192.168.54.0/24 (primary and node office)
  • VPNClients: 2.4/5 GHZ VPN clients to reach distant site via OpenVPN; VLAN 192.168.55.0/24 (primary only)
 
Sorry, but with 4 routers transmitting long range 2.4GHz Wi-Fi it's hard to tell which one is actually doing GN Pro. Allowed to setup in GUI doesn't necessarily mean it's working. Every single attempt done by other forum members to propagate anything else than standard AiMesh GN1 to non-Pro nodes so far failed including ExpertWiFi EBG15 to non-Pro consumer routers as nodes. Any chance for a simpler test GT-AX6000 to RT-AX86U?
 
Any chance for a simpler test GT-AX6000 to RT-AX86U?
Yes, you are welcome to test whatever configuration that you'd like.
 
I already have RT-AX86U, EBG15 is about $100.

If it works as you say I get a $100 hit. If it doesn't - you pay me $100. The price of finding the truth. Deal?

 
Last edited:
I already have RT-AX86U, EBG15 is about $100.

If it works as you say I get a $100 hit. If it doesn't - you pay me $100. The price of finding the truth. Deal?

I'm not going to continue to debate this with you, but rather I'd rather show you what I see (and can verify) for my 2.4 GHz guest network used for IoT devices.

AiMesh nodes configured for guest network GetYourOwnDarnInternet (aka VLAN 52) include RT-AX86U:

1. IoT24.png
VLAN 52 configured with subnet 192.168.52.0/24:
2. .52subnet.png
IP addresses for devices connected to GetYourOwnInternet via RT-AX86U (Garage) have IP addresses associated with VLAN 52 (i.e., 192.168.52.x). Similarly, the last client in the list has an address associated with VLAN 53 (i.e., 192.168.53.100), which is connected to 5 GHz IoT guest network iotAndCrumpets:
3. AX86Udevices.png
 
I'd rather show you what I see

Thank you. I'll test this at first opportunity and report back the results with isolation and everything. I really hope it works - it will give a new life to many non-Pro routers out there. Otherwise I can have 802.11g (legacy) 2.4GHz network with MU-MIMO and Explicit Beamforming, according to the GUI. Last time I played with AiMesh half of the node connected wirelessly clients were shown as wired. I don't trust the GUI too much.
 

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