I am having to use Barrier Breaker for a project as OpenWrt Chaos Calmer for Ubiquiti AirRouter is broken - at least is is just now.
After installing 0.9_beta9.9.9-5 you will have to replace the installed init.d script with the version in
0.9_beta9.9.8 as in the attached file here otherwise Nodogsplash fails to start up. nodogsplash.init.d.txt
Works perfectly after this. I have not had time to investigate what is causing the problem, but this fix works.
@bluewavenet is to set enabled to 1 the only issue here; in this case I would close the ticket. As this is the safe default (afaik, NDS will lock you out using the default options and enabled set to 1).
我不确定。我有一个工作. 部署所需的, 并使它的工作, 恢复到原来的 inet. d 脚本, 并没有时间回顾更详细。 我们需要这个吗？它是一个不必要的复杂性, 还是它有我没有时间考虑的潜力？它似乎是一个反复出现的问题-人安装, 它无法启动。 顺便一道-在混沌平静的电流 Openwrt 释放是岩石固体 CC 和 BB。我们有一个酒店/餐馆/酒吧, 平均每天超过第300客户端 (在 PC 引擎 Alix 2d2 喂养到9接入点)。
I'm not sure. I had a working .conf needed for a rollout and made it work by reverting to the original inet.d script and have not had time to look back in more detail.
Do we need this? Is it an unnecessary complexity or does it have potential I have not had time to think about? It seems to be a recurring question - people install and it fails to start.
By the way - the current Openwrt release in Chaos calmer is rock solid on CC and BB. We have a hotel/restaurant/bar running with an average of over 300 NDS clients per day (on a PC Engines Alix 2d2 feeding into 9 access points).
I experimented with 0.9_beta9.9.9 as was using this on CC for a rollout. Changing the init.d script to include START=198 seemed to do the trick.
Problem is caused by the interface used by NDS not being UP when NDS starts. NDS then unloads.
START=198 makes init.d wait longer before starting NDS.
I have not had time to investigate further.