Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Proposed road map
Time to let you guys know of the progress and plans for StarOS.

I will be doing one last update to the various firmwares to add a few driver changes and to get the kernels to a newer version.

After that, I have decided I HAVE to switch to OpenWRT in order to be able to do this with one guy. Of course that will mean that the GUI becomes web based, which will please some and and anger others.

This will give me a way newer kernel than even the updates I am planning. For instance the x86 and the Ventana move to a 4.x kernel and I can compile for 64 bit. The web GUI is slow compared to our SSH interface but it is very usable. My intention is to begin the process of adding our driver to the core, as an option. I will also be doing a dedicated GUI system to augment the web GUI . My work on the Stargaze and MyInfo organizers has evolved a very useful and powerful technique to handle almost any control data anywhere that you can have a SSH interface. I have been using it for all of my StarOS development, controlling the Linux virtual under VmWare from from a Windows 10 program. That work has shown me how to use it all for the setup GUI. I have tested with OpnWRT and it will work as expected.

I will be making the optional enhanced driver and the GUI a licensed item. This means that if you are content with the OpenWRT GUI and drivers, then it is for all intents and purposes a FREE firmware. Once I have support for our active platform bases I intend to start to add support for the active OpnWRT platforms, which will give you a much larger hardware base to choose from.

I have a Ventana core running quite nicely. I used it to test whether the OpenWRT drivers was worth porting to StarOS. I can easily add several VPN system, website support and a NAS that can be used for "whatever" you might find useful at a tower site, such as a collection of firmware to avoid downloading many times over your bandwidth. This can save a lot of bandwidth, but more importantly will be way faster since it is closer to the units being updated.

Initially I will be generating a stock OpenWRT but once it is stable and well received I will be open to adding different features that people might be requesting. My best guess is not to expect this phase for at least 6 months, so early 2018.
Any updates to this?
I have an OpenWRT menuconfig script I can share. It has support for wifi and SSD for a nice compact NAS unit.

The problem is that it is OpenWRT and thus almost everything you are used to is changed. It comes at routing from a bridging standpoint, which is crazy. It can be configured to be a router, but it takes a lot of config. It also does not have the ## or 5/10 MHz channels. Association stats and other info we are used to seeing is also incomplete or simply not there. I have looked at the web interface and my brain simply wants to do something else. A web interface is not meant for realtime displays, so I'm afraid it is what it is.

I can recommend this for a home system, but then a 6 radio unit is way over kill.

Ryan Wrote:Any updates to this?
I keep a unit online and use it to do all of my pings, starutil and general network testing. I direct all my private subnet traffic to it, from windows 10, and then just let OLSR figure it out from there. This makes for a very easy way to change an AP and not have to reconfigure it, which I need to do whenever I make a new version.

I have a 480 GB SSD in it so it is a very handy NAS that is outside my windows machine and connects via the network. It is just another layer of backup safety for me.

The web interface is kind of "OK", once you get the hang of it, but, as I said, it is not suitable for realtime stats.

Forum Jump:

Users browsing this thread: 1 Guest(s)