This is also the case on the Atheros routers.
After adding a new DHCP server you have to restart the router otherwise the clients of the VAP can't get an IP address somehow.
I assume that something is not started via the "apply" button.
Just tested it again with build r47822.
My statement seems to be no longer currently true.
Either fixed or that was related to a specific configuration (I would have to search the thread in which I had found that).
Joined: 18 Mar 2014 Posts: 12904 Location: Netherlands
Posted: Tue Dec 21, 2021 12:02 Post subject:
First of all you do not need the VAP workaround any more (in recent builds, currently 47900).
Second yes the scripts will run (if executable etc.) but only if available.
It can take longer (10-30 seconds) before /jffs is online.
So either increase the sleep time or use the built in is-mounted utility to wait until the directory is online
(is-mounted.sh /jffs)
I have just installed r48646 on my R7000 and was pleased to see the VAP issue has been resolved (I was still using the command workaround, coming from r47608)..
I have removed the commands from my startup script, but the VAPs are not showing on the sys-info screen (they do on my R7800 (Atheros chipset, no startup command required):
R7000:
R7800:
Is this a chipset thing? Should VAPs be showing?
For what it is worth, my AC68U (Broadcom, still running r47608 and startup commands) is not showing the VAPs on the sys-info screen either.