Good luck with the last minute gift shopping.
curl -kLSs --retry 3 --retry-delay 5 --retry-connrefused https://raw.githubusercontent.com/Martinski4GitHub/YazFi/develop/YazFi.sh -o /jffs/scripts/YazFi.445.DEV.sh
chmod 755 /jffs/scripts/YazFi.445.DEV.shcp -fp /jffs/scripts/YazFi.445.DEV.sh /jffs/scripts/YazFi/jffs/scripts/YazFi runnowThanks for taking a look at the issue. Seems I still have issues with not being able to access main LAN clients with the new YazFi file you posted. Maybe someone else can do some testing on their end to see if maybe its just my router. Some observations using the 4.4.5 YazFi file you put up.
/jffs/scripts/YazFi runnow command./jffs/scripts/YazFi runnow command, WiFi client picked up the 2.4Ghz SSID's right away but later again had trouble seeing the 2.4Ghz SSID's. Wonder if firmware issue, will look at the system logs later to see if anything strange is happening.It looks like you forgot to run the "chmod 755 /jffs/scripts/YazFi.445.DEV.sh" command that I posted in my download instructions before overwriting the script (cp -fp /jffs/scripts/YazFi.445.DEV.sh /jffs/scripts/YazFi).
Yes, that's expected because your original script was simply replaced with the develop branch version *without* doing a full installation so the webGUI has not been "told" that a new version was just "installed." When a proper installation is performed, such details are taken care of automatically.
Those are very strange behaviors but, AFAICT (and as you later found out), unrelated to the YazFi changes.
Just tried the 4.4.5 again on RT-AX86U Pro 3.0.0.4.388.5. Still no go on my end. With internet disabled and two way to guest enabled on YazFi Guest Network 2 the WiFI client cannot access main LAN client even though the main LAN client can ping the WiFi client. If internet access is enabled then the WiFi client can access main LAN client. If it is working on your end, but not working on mine it would help if others could test on their routers to see if its something specific to my settings (or yours) or something limited to specific routers.
Same here, out of ideas for the cause on a RT-AX86U Pro. Might break out a RT-AC68U to test with to see if it exhibits this same issue as the RT-AX86U Pro when using YazFi.
iptables outputs you provided and ran them through diffs but did not catch anything that seemed "out of place" or any clues that would indicate a possible issue. Granted, I'm not a true expert in reviewing/analyzing firewall rules so it's possible that I may be missing something that would jump out when seen by fully expert eyes.Yeah, I'm starting to suspect that something like that might be at play here. Although at this point we can't rule anything out completely, I highly doubt that Entware would be a factor in this situation, especially since I don't have any Entware-based add-ons installed, and the only Entware services installed are OpenSSH & Fail2Ban, which were not running at the time the tests were performed (they run occasionally & on-demand under very specific & limited conditions).
The professional settings for a hard factory reset RT-AC68U who's YazFi clients cannot access main LAN clients when internet is disabled and two way to guest enabled shown below. These were default values, some are different than yours. I tried using the exact same values in your screen capture (where I could), didn't work to fix the issue.
curl -kLSs --retry 3 --retry-delay 5 --retry-connrefused https://raw.githubusercontent.com/Martinski4GitHub/YazFi/develop/YazFi.sh -o /jffs/scripts/YazFi.445.DEV.sh
chmod 755 /jffs/scripts/YazFi.445.DEV.sh#!/bin/sh
#################################################################
# GetYazFiDebugInfo2.sh
# Last Modified by: Martinski W. [2024-Jan-02]
#################################################################
_GetYazFiDebugInfo_()
{
printf "$(nvram get productid): "
printf "$(nvram get firmver).$(nvram get buildno).$(nvram get extendno)"
printf " [$(date)]\n"
echo "========================================================="
nvram show 2>/dev/null | grep -E "(wl[0-2]\.[1-3])(_bss_enabled=|_ap_isolate=|_lanaccess=)" | sort -d -t '=' -k 1
nvram show 2>/dev/null | grep -E "lan_ifname=|wan0_ifname="
WAN_IFN="$(nvram get wan0_ifname)"
echo "========================================================="
printf "brctl show\n----------\n" ; brctl show
echo "========================================================="
printf "ip route show\n-------------\n"
ip route show | grep -v "dev $WAN_IFN"
echo "========================================================="
printf "ifconfig\n--------\n" ; ifconfig
echo "========================================================="
[ -f /tmp/YazFi.lock ] && \
yazfiPID="$(cat /tmp/YazFi.lock 2>/dev/null || echo "NONE")" && \
printf "YazFi Lock found. PID: [$yazfiPID]\n--------------------------------\n"
TABLES="nat filter mangle raw"
findStr="br0|eth0|wl[0-2]\.[1-3]|YazFi|$WAN_IFN"
for tableID in $TABLES
do
printf "${tableID}\n------------\n"
iptables -t $tableID -S | grep -E "$findStr"
echo "========================================================="
done
}
_GetYazFiDebugInfo_ > ${HOME}/YazFi_DEBUG_$(date +"%Y-%m-%d_%H-%M-%S").txt
#EOF#Not sure how helpful the following will be as something weird happened with the RT-AC68U when I enabled Intranet access on the Guest Network 1 to do some testing (see Test Two below) and generate a log result per your script. The IP address of the WiFi client changed (see notes below) and from then on in the testing that WiFi client had internet access even though I configured internet access to be blocked initially in the Parental Controls, then after removing that Parental Control setting and installing YazFi then disabling internet access in YazFi. Repeatedly double checked to ensure the WiFi client was connected to the Guest Network 1. WiFi client would complain about no internet access when connected to Guest Network 1 (with internet blocked) yet web browser could access internet. It appears somehow the WiFi client Brave browser was picking up Cellular data connection instead of WiFi connection bypassing the settings. Something that did not happen in past testing. There are a total of five log files rather than three as I was trying to do more testing.
Thank you very much. I appreciate your taking the time to run all the tests & post the results. I reviewed the last 4 debug output files, and I continue to be puzzled as to why the YazFi 4.4.5 changes don't work in your specific routers. All the firewall rules and related NVRAM settings for 2-Way comms between Guest & LAN clients (e.g. intranet enabled & isolation disabled) appear to be correct, and I don't see anything else that would interfere with the Guest Network pinging/accessing LAN clients. Perhaps I'm looking in the wrong place, and there might be some other router setting(s) that somehow is/are affecting your tests.
Is the brother's router running any other add-on scripts or using AiMesh?
No AiMesh nodes at all. Single router + one TP-Link WiFi Range Extender placed near the garage for the door opener & 2 surveillance cameras on the far end of the house. Only YazFi & YazDHCP for add-ons. One USB 3.0 drive with Entware but no services are running from it (it's used only to have diagnostics & extra CLI tools available and store some of my custom personal scripts).
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!
