You'll forget that you weren't familiar with it after you get used to them. It's just like getting a cisco router for your first time and then trying to figure out where to start. Sort of like walking in a dark room blindfolded for the first time, where am I?
One thing about having to learn the system is when you are forced to look through all the various settings you start getting real familiar real fast of all the variations of settings. Usually thats enough to challenge a thinker type and they soon expose themselves as very versatile products and easy to mess with. And it touches on lots of things nothing to do with star. OLSR DHCP L7 are not anything special that star has done, they are the same as you would find in any linux router. They are just inluded as an additional features. Star is really about the wireless driver. Rest of the stuff is common place. As for the cards coming disabled, you now know, you can log into the unit to turn off a port. Nice feature to have. And to get there to the place where you disable or enable the device, you have to go there anyways to configure that port. What seasoned star guys probably do, at least I do this, is when I first turn a board on, I upload the newest firware that I intend on using. Then I upload a default configuration for that particular board in that particular situation. If it's a 2 port, a 4 port a 1 port etc, I have default configs. Actually those default configs are just a config off another board thats already configured. We download and back up the configs off every board on our network. Then we go through and make those changes that are unique to that deploymment, essid 1p addy, etc. It's then fast and easy. Utilistar, star util, and now Star gaze will help you. You can download the configs and save them and if a board dies on you, you just upload the current config to the new board and it works, no config changes needed. Just save and activate changes and reboot. Presto. The best thing about Stars forums style support, there is a lot of people that are very smart that are willing to help. And a lot of those guys also use MT, Alvarion, Moto, Trango and anything else, so it's not as much of a closed minded group to get help or opinions from. Marlon K. Schafer wrote: > I have more and more trouble justifying the cost of any product with a > "steep learning curve". There's just no reason for gear to not have a > simple and advanced mode these days. > > And there's no reason for documentation that doesn't cover simple questions. > > There's no reason to NOT have a quick start guide. > > There's no reason to have a box that doesn't do something right out of the > box (this one shipped with all wireless ports disabled!). > > There's no reason to not have the option of picking up the phone and getting > some help to get started. Now I'm DAYS into a project that should have > taken just a few minutes. There was no documentation in the box. Not even > the web site address, had to Google for it. There is no tech support number > on the web site. > > I guess if a company wants to stay small, have a small user base etc. this > is all good. You only get really tech savvy customers. Something that I'm > not when it comes to routing and command line. I've got a very lean fast > growing company. I have over a dozen brands of hardware deployed. They all > do things differently. I have long ago given up on trying to memorize all > of this crap. If it's not completely self explanatory (like 802.1d bridging > actually turning on bridging!!!!) I don't have time to play with the gear. > It doesn't really matter how good it is. > > For the record I've got the same bitch with MT. I can do a little bit more > with them because they at least have a decent gui. But most of what I do > with them is due to Butch's help. He's great but having to hire him all of > the time raises the cost of the gear by a lot. All because I don't have the > option of a Linksys simple setup option!!!! Dumb. Very dumb. > > Alvarion has work to do too. They use strange names for functions. Don't > give "typical" levels as examples right in the software. I mean really, how > am I supposed to know if 10, 1000 or -50 is a good number to try for > interference mitigation? And which settings would I tweak for which things? > Who the heck has time to read yet another 150+++ page manual? Put the > basics right in the software! > > sigh > marlon > > ----- Original Message ----- > From: "George Rogato" <[EMAIL PROTECTED]> > To: "WISPA General List" <[email protected]> > Sent: Wednesday, June 11, 2008 6:56 AM > Subject: Re: [WISPA] star os config help- clarifying my message > > >> Not really trying to defend star. The documentation issue has been >> around since Adam met Eve. >> >> The learning curve appears to be steep, but in fact, there is pretty >> good documentation. >> If you search the forums, you will pretty much find anything you need to >> know. Trick is first searching the forums. >> Then there is Tog's WiKi that is pretty good. >> Tog has put a lot of time into the WiKi and helping others with their >> star stuff. >> >> One thing I might add, one reason it's hard to document star, it's >> always changing, and how do you document l7 filtering or isc dhcp easily? >> >> Fortunately Tog and a few other smart guys hang out there and try to >> offer their help when they can. >> >> Good luck Ralph. >> >> George >> >> ralph wrote: >>> I just re-read it and need to clarify. >>> I put addresses from the same subnet on all interfaces because it seemed >>> that an address was required per the blanks to fill in. It was never >>> documented to only put an address on one interface. >>> With other products, you don't really program the other interfaces, so >>> you >>> aren't inclined to make that mistake. >>> >>> >>> >>> -------------------------------------------------------------------------------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> -------------------------------------------------------------------------------- >>> >>> WISPA Wireless List: [email protected] >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: [email protected] >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
