- Sat Aug 05, 2017 2:27 am
#68849
Thank you for your feedback.
About your issues:
- You are right: the standalone branch misses some of the latestst changes. Think, I will merge them and make the master branch "standalone". Will do that next week, when I am back from summer vacation.
- Will think about the security model. Currently the assumption is, that the owner of the uplink WiFi is the good guy and that this WiFi has to be protected from the clients of the SoftAp side. Probably it is a good idea to be able to restrict admin access either to the uplink side or to the SoftAP side only.
- It would be easy to include "reset [factory]" in the list of "locked" commands, however then you have to reflash the config, once you have forgotten the lock pw. Perhaps it would be a compromise to allow it at the serial console even in locked state.
- If the uplink side has no password, you can still set one to use it as lock password. But optionally saparating these two passwords might still be a good idea. The ratio behind the current logic is a) the security model and b) that it is easier to remember one PW for WiFi.
- My experience is, that running the CPU at 160 MHz is a good idea. The additional power consumption is marginal (had about 5% less battery time), stability and heat are not an issue, and actual computations are about 50% faster. Think, this is the case as the router CPU idles most of the time anyway.
About your issues:
- You are right: the standalone branch misses some of the latestst changes. Think, I will merge them and make the master branch "standalone". Will do that next week, when I am back from summer vacation.
- Will think about the security model. Currently the assumption is, that the owner of the uplink WiFi is the good guy and that this WiFi has to be protected from the clients of the SoftAp side. Probably it is a good idea to be able to restrict admin access either to the uplink side or to the SoftAP side only.
- It would be easy to include "reset [factory]" in the list of "locked" commands, however then you have to reflash the config, once you have forgotten the lock pw. Perhaps it would be a compromise to allow it at the serial console even in locked state.
- If the uplink side has no password, you can still set one to use it as lock password. But optionally saparating these two passwords might still be a good idea. The ratio behind the current logic is a) the security model and b) that it is easier to remember one PW for WiFi.
- My experience is, that running the CPU at 160 MHz is a good idea. The additional power consumption is marginal (had about 5% less battery time), stability and heat are not an issue, and actual computations are about 50% faster. Think, this is the case as the router CPU idles most of the time anyway.
