I have been successful at getting one of the new pieces of hardware running StarOS. It is the unit with external antennas and is fine except for the wifi driver, which does not load.
It is booting, saving configs, etc so the bulk of the work is done. Cleanup remains and it will be an item that Ken will be able ship.
Because it is StarOS it will mean that the ## channels will be available as well as the 5 & 10 MHz channels (in licensed mode).
[
attachment=1]
Ignore the funny name in the license. That was a quick and dirty license and will be part of the cleaning process. The key is that it is running.
Here's hoping.
We have a few of them waiting to test and hopefully deploy in short order.
(10-22-2019, 10:22 PM)lonnie Wrote: [ -> ]Ignore the funny name in the license. That was a quick and dirty license and will be part of the cleaning process. The key is that it is running.
Any update on how things are coming along?
The news is not great. I have the driver recognizing the wifi devices but it simply will not use them. I am missing something quite simple, but it eludes me.
Since the second time you do something, it is better than the first, I have made a backup of the driver at this point in time and will begin the process again. Hopefully a step by step re-do will catch something I missed the first time.
For those of you with some of the new hardware running OpenWrt, it has been communicated to me that they do not save settings.
This is because of a "Nanny" feature that needs to establish contact with the unit from the browser after an apply. If it does not communicate it reverts the settings and gives a message to allow it to forcefully apply them. This works.
I have actually asked the Openwrt guys to add another button to do the "forceful" method in addition to the "safe" method. They told it would be added and a future update would have it.
(11-12-2019, 05:14 PM)lonnie Wrote: [ -> ]For those of you with some of the new hardware running OpenWrt, it has been communicated to me that they do not save settings.
This is because of a "Nanny" feature that needs to establish contact with the unit from the browser after an apply. If it does not communicate it reverts the settings and gives a message to allow it to forcefully apply them. This works.
I have actually asked the Openwrt guys to add another button to do the "forceful" method in addition to the "safe" method. They told it would be added and a future update would have it.
Any ETA on the update? I am pretty sure I've reloaded the page and navigated around after saving an update but will need to play with it some more.
Can you tell me what changes you were making?
BTW, the update is in the Master branch of the Openwrt sources and now needs to filter down to the existing lower levels. No idea when that will happen, but I will keep checking.
Settings new IP's, SSID's Firewall rules ect, Pretty basic stuff. Everything works able to log back in check stats see whats moving for traffic and the client device associates correctly ect. Says it saves yet after a reboot seems to go down.
Hows the Star Os side coming along running out of the old War1b units?
(10-22-2019, 10:22 PM)lonnie Wrote: [ -> ]Ignore the funny name in the license. That was a quick and dirty license and will be part of the cleaning process. The key is that it is running.
Any more update on this lonnie?