v4.4.4

All credit for this release goes to @Martinski4GitHub

• FIXED: Issue in the WebGUI to address false errors when validation failures occur with field values from DISABLED network interfaces. Now all field value validation is performed only for ENABLED networks. DISABLED networks are ignored during validation.
• FIXED: Problem where sometimes the Hostname & IP address values for all currently connected clients were being shown as "UNKNOWN" even though the YazFi Guest Network clients were working fine & were in fact connected to the correct Guest Network.
• IMPROVED: Code improvements to make sure the list of virtual wireless interface names is valid. This avoids getting strange errors when generating the list of currently connected clients via the CLI menu.

v4.4.3

All credit for this release goes to @Martinski4GitHub

• NEW: Added functionality to properly recognize and correctly map virtual interfaces to the corresponding WiFi radio bands on routers with 6GHz capability (e.g. Tri-band routers like the GT-AXE11000, and Quad-band routers like GT-AXE16000).
• NEW: New wl*_DHCPLEASE configuration variable and corresponding "DHCP Lease" input field in the WebGUI to allow setting a DHCP Lease time for each Guest Network independently from the NVRAM setting used for main LAN clients. The valid range is 120 to 7776000 seconds (2 minutes to 90 days). Time values can be entered in seconds (e.g. 86400s), minutes (e.g. 1440m), hours (e.g. 24h), days (e.g. 2d), or weeks (e.g. 2w). A single digit ZERO '0' or an upper-case letter 'I' indicates that an "infinite" lease time value will be applied.
• FIXED: Fixed a bug in the WebGUI list of "Connected Guests" where sometimes the wrong IP address was shown for some of the active clients; other times a client that was no longer connected to the network was shown as active and with the wrong IP address.

v4.4.2

FIXED: WebUI would fail to load last few settings

v4.4.1

FIXED: YazFi could erroneously delete VPN Director rules after YazFi's own redirected rule when disabling VPN redirection

v4.4.0

NEW: Added setting to control whether guest network can access internet or not
IMPROVED: Add cron persistence check earlier in startup
CHANGED: Script now downloads updates via Scarf Gateway (see bottom of README)
CHANGED: Decreased delay in running after firewall restart from 30s to 10s
CHANGED: Script now installs LICENSE and README files during install

v4.3.4

CHANGED: When enabling FORCEDNS, DNS1 is copied to DNS2 and DNS2 is disabled
CHANGED: service-event hook is more selective when it calls YazFi

v4.3.3

NEW: Generate QR Code for guest network at the command line (requires Entware for qrencode package) - credit @RMerl for QR code function in firmware WebUI for inspiration

v4.3.2

CHANGED: Connected client information will now only update when looking at the WebUI page for YazFi with auto refresh enabled

v4.3.1

FIXED: WebUI display clients list would show incomplete results with large numbers of connected clients

v4.3.0

NEW: View connected clients for YazFi networks on the YazFi WebUI page
NEW: Support/compatibility for VPN Director (Merlin firmware feature)
IMPROVED: Connected client output now includes extra information such as RSSI, Rx/Tx rates, connected time
IMPROVED: WebUI support for MIPS based routers running John's fork (WebUI updating still unsupported)
IMPROVED: Added check for LAN access being toggled to persistence check
IMPROVED: Allow YazFi guests to talk to local upstream DNS servers even if redirecting traffic to VPN e.g. YazFi is running on a router
behind a router and DNS is handled by upstream router
FIXED: Prevent NextDNS blocking YazFi from working correctly
CHANGED: Cookie expiry for collapsed WebUI sections increased to 10 years
CHANGED: Always block DoT if Force DNS is set, not just if router DoT is turned on
CHANGED: Allow YazFi to override exclusive DNS for VPN client