Shouldn't be a problem.
I've said it before: this forum is so freakin' awesome! You make a suggestion and within hours you get a response and often your suggestion is approved, sometimes declined with an explanation why not. Nevertheless, a big thanks to all you script writers out there, and of course @RMerlin , mr maestro himself, making all of this possible! I am deeply impressed with all your work and effort you guys put in to making our routers better than they orginally were!v4.0.1 is now available
Changelog:
Code:Add SSID to table header
Is anyone else having problems with the WebUI not surviving a reboot?
Works fine for me after the install, after I hit 'u' twice, but when I reboot the YazFi tab no longer appears in the guest network menu.
If I go to a shell, it still seems to be operating fine behind the scenes...?
On 384.15 on an AX88U, I've tried installing both through amtm and from the command line, a couple of times each way.
That sounds like something is erroring in the browser. Are you waiting until YazFi has run as per syslog? There's a 60 second delay, so if you visit the page too soon, the config symlinking won't exist.Same here, WebUI doesn't survive reboot. Only YazFi tab with apply button visible but nothing else. If I use ssh and chose apply settings the WebUI appears. (AC86U)
That sounds like something is erroring in the browser. Are you waiting until YazFi has run as per syslog? There's a 60 second delay, so if you visit the page too soon, the config symlinking won't exist.
Can you please check for any console errors in the browser?Yes, after about 60 seconds the YazFi tab appears in the guest network menu but there is only an apply button and nothing else. I also have the NextDNS client installed but nothing else.
Can you please check for any console errors in the browser?
That gives me enough to start investigating. For some reason the symlink isn't being created (which is strange because applying settings manually is no different to the on boot run)
That gives me enough to start investigating. For some reason the symlink isn't being created (which is strange because applying settings manually is no different to the on boot run)
Hotfix uploaded, no version changeThanks, let me know if there is anything else I can do to provide more debug info!
YazFi tells the wireless driver to deauth all connections, which should make the cameras reconnect and get a new ip. If you ping the cameras while YazFi is running, do you see it drop?
pc-append local=/RT-AC87U/
pc-append dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,120s
pc-append sleep 600
pc-append dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,86400s
I'm concerned that your devices are ignoring a de-auth from the wireless network, to be honest! dnsmasq.postconf would be the place to do it, it will run whenever dnsmasq (responsible for DNS and DHCP) startsJack do you have any thoughts on how to set the DHCP lease time to 120s on boot, then back after a time period?
I was thinking of modifying the dnsmasq.postconf script with the following:
Code:pc-append local=/RT-AC87U/ pc-append dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,120s pc-append sleep 600 pc-append dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,86400s
I don't know if the Dnsmasq.postconf script is the right place to try doing this. I am guessing that it gets called too late in the boot process to catch the issues I'm having with my cameras.
I'm also okay with blocking all DHCP until everything is booted up...but I don't know where to do that either
They seem to respond if they are properly addressed, I'm not sure why they hang on to the original lease. I've done a factory reset on the devices so they don't "know" about the primary network. I'll do more experimenting and report back.I'm concerned that your devices are ignoring a de-auth from the wireless network, to be honest! dnsmasq.postconf would be the place to do it, it will run whenever dnsmasq (responsible for DNS and DHCP) starts
View attachment 21575
And indeed I have no YazFi_www.asp in the directory, so when I click on the YazFi tab all I get is a 404 error.
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!