That seems to have fixed the duplicating entry in the VPNC.Can you try
please? I've made some changes to align with the nvram changes in 384.18Code:YazFi develop
That seems to have fixed the duplicating entry in the VPNC.Can you try
please? I've made some changes to align with the nvram changes in 384.18Code:YazFi develop
Try running the below one-liner, then apply settings in YazFi
Code:touch /jffs/addons/YazFi.d/userscripts.d/AllowSMB.sh && chmod +x /jffs/addons/YazFi.d/userscripts.d/AllowSMB.sh && { echo '#!/bin/sh'; echo 'iptables -D YazFiINPUT -i wl0.1 -p tcp -m multiport --dports 139,445 -j ACCEPT'; echo 'iptables -D YazFiINPUT -i wl1.1 -p tcp -m multiport --dports 139,445 -j ACCEPT'; echo 'iptables -I YazFiINPUT -i wl0.1 -p tcp -m multiport --dports 139,445 -j ACCEPT'; echo 'iptables -I YazFiINPUT -i wl1.1 -p tcp -m multiport --dports 139,445 -j ACCEPT'; } >> /jffs/addons/YazFi.d/userscripts.d/AllowSMB.sh
question, can I just set this up to use guest network for my google mini/ smart home devices? they seem to be the most finicky and seperating them into their own SSID would be ideal, I don't need them to go through VPN or anything.
I'd just like to throw in that I would love to see this handle LAN ports as well. Especially on the newer models like the RT-AX88U where there is no robocfg.Correct. While VLAN support for LAN ports would be nice, it is messy when supporting lots of models that use different port configurations etc.
Can you try a port scan on the router from the guest ssid using nmap, to verify what ports are exposed please?Hi Sir, I tried this, copied the command then paste to ssh window. restarted the router, but still unable to see the smb drive connected to the router. I can ping the router though when I am connected to the guest ssid.
I also edited the Yazfi settings, enabled two way to guest, set the client isolation to false. and in the native Guest section, enabled intranet. Thanks for the help.. hope there's still a workaround.
IMPROVED: WebUI validation
Disable fields if guest disabled in firmware
Disable fields if not enabled in YazFi
Disable VPN number if not redirecting
CHANGED: 0.0.0.0 not needed in line with VPN policy routing nvram changes in 384.18 / 384.13_10
Do you get any errors if you runUpgraded to v4.1.2 alongside a fresh wipe and install of Merlin 384.18. Web UI tab not showing, due to this? Note from Post #1:
WebUI page for YazFi
You must be running firmware no older than:
TIA
- Asuswrt-Merlin 384.15
YazFi startup
As a datapoint. GUI page shows for me on Merlin 384.18 on an RT-AC68U.Upgraded to v4.1.2 alongside a fresh wipe and install of Merlin 384.18. Web UI tab not showing, due to this?
modprobe xt_comment
-m comment --comment "$(Get_Guest_Name "$2")"
if ! modprobe xt_comment 2>/dev/null; then
Print_Output "true" "Router does not support xt_comment module for iptables. Is a newer firmware available?" "$ERR"
CHECKSFAILED="true"
fi
Jul 9 22:48:39 RT-AC5300 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Jul 9 22:48:50 RT-AC5300 syslog: Error unlocking 6: 9 Bad file descriptor
Jul 9 22:48:50 RT-AC5300 syslog: Error unlocking 0: 9 Bad file descriptor
Jul 9 22:48:55 RT-AC5300 YazFi: YazFi v4.1.2 completed successfully
It's normal where networkmap gets restarted. Nothing to worry about!hello,
I've been seeing this in my logs for a while now... any ideas as to how to fix?
Code:Jul 9 22:48:39 RT-AC5300 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate Jul 9 22:48:50 RT-AC5300 syslog: Error unlocking 6: 9 Bad file descriptor Jul 9 22:48:50 RT-AC5300 syslog: Error unlocking 0: 9 Bad file descriptor Jul 9 22:48:55 RT-AC5300 YazFi: YazFi v4.1.2 completed successfully
i think the comment was so the script knew which rule(s) to delete if a yazfi network changes which vpn client is configured, i.e. was using 1 but moves to 2I tried to install YazFi on RT-N66U, but xt_comment was missing (running the latest john's LTS).
I got it working by removing the lines related to xt_comment, is there a better way to do it? (everything seems to be working fine)
Code:modprobe xt_comment -m comment --comment "$(Get_Guest_Name "$2")" if ! modprobe xt_comment 2>/dev/null; then Print_Output "true" "Router does not support xt_comment module for iptables. Is a newer firmware available?" "$ERR" CHECKSFAILED="true" fi
Luckily I don't use that feature, hopefully this helps anyone else on the RT-N66U having issues.i think the comment was so the script knew which rule(s) to delete if a yazfi network changes which vpn client is configured, i.e. was using 1 but moves to 2
It's normal where networkmap gets restarted. Nothing to worry about!
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!