Ah, the failure for uf would be because switching branch triggers a firewall restart (in fact any update of YazFi does), and this waits 60 seconds for it to complete - my apologies! With @RMerlin 's guidance on uname it is a simple enough fix, but I can't promise that the separate busybox installed in Entware won't cause any other issues down the road!
Hi Jack
….and firstly my apologies for the slow reply! As ever your explanation adds much value to my on-going networking education, and I completely understand that the presence of the separate "Entware installed" busybox may well have implications 'down the tracks' as these things are complex (at least to my somewhat feeble mind!! LOL) and the inter-relationship/interaction between Merlin's base firmware, add-ons (like YazFi) and scripts clearly leaves many opportunities for conflicts to arise. I am grateful that, in this regard at least, your expertise was able to unravel the issue and ultimately to present a functional WebUI.
I have however experienced another issue, which may (or may not) turn out to be related to the busybox clash, in that since installing YazFi my VPN Client is no longer working (despite being connected and correctly reporting) with both the network PC's and my iPhone revealing the public (ISP) IP . The issue persists following a router re-start both soft (from the WebUI) and hard (with the removal of power).
(NB. As a result of advice proffered on these forums my Network has been configured (for enhanced security) to establish a VPN Server hosted on the AX88U so that activity away from home (cell or Wi-Fi) is directed through my secure home network. Thanks to a clever script lodged in "firewall-start" kindly offered by forum expert Martineau I was then also then able to direct this traffic through my existing VPN Client thus enjoying the full advantages of my home network as if I was at home!)
I should note that the issue reported persists on the iPhone whether or not it is connected through the VPN Server, thus with the VPN Client active ALL devices connected to my network are still being routed via the Public IP. Perhaps the explanation is simple, but I felt by offering an insight into the way my VPN Client/VPN Server is configured may well hold some significance, please ignore if this is not the case.
Thank you for your continuing kind assistance
PC Pilot