Re: [WISPA] star os config help
Hi Marlon- I learned the hard way- Upgrade your firmware immediately! I bought 5 2000's plus one of the ones with the panel antenna built on the front because I had kept hearing about how good StarOS was and I wanted to do a couple of things with them: 1. Try out the OLSR meshing because, as you know, I do a lot of mesh and I am looking for a lower end solution than Tropos or Cisco for the small projects. 2. Use them as transparent bridges to feed docks at a marina. The Lucaya product was attractive to me: reasonably priced, it seemed that a lot of people used it, they were FCC type accepted systems (a big thing for me, as I have several licenses at stake personally), and they were supposedly good at making a dual-radio mesh. The striking thing about these is the almost near total lack of documentation. There is a decent piece on StarOS itself, but nothing is available about the product we bought- hardware wise. There is not a tech support number, and no way I can see to communicate with Valemount other than the forum, which Lonnie does seen to monitor often. I made the mistake of asking what you did: How do you make a bridge? I finally got an answer, but prior to that was lectured endlessly about how I should be using routing instead of bridging and why would I possibly want to use a bridge- EVER. Remember- all I wanted to do was make them act like a simple pair of Canopys, Tranzeos, Trangos, or Ligos, all of which have a simple bridge function and are used in many systems by some of the biggest players as such. I made the bridge, but made the mistake of using the same subnet on all interfaces (normal practice with Ligo, Canopy, Tranzeo, etc.) Well DON'T DO THIS ON STAROS! You end up with an internal bridge loop. Simple, I thought, I'll just factory default it and not do that again. WRONG. After many more forum messages back and forth and no really straight answers, I finally learned that the button does nothing but reboot the radio. Turns out that the button only works as a defaulter in the latest firmware. I get to send them all back to be reflashed. Sure you can do it with the serial port, IF you have the proper header plug and IF you happen to have a TTL to Serial converter laying around. I am going to make an adapter cable so I can use my Motorola RIB (a box used for programming Motorola 2 way radios) to talk to these, but in the meantime I had to deinstall all of the Lucayas and replace them with something else (Ligowave 1a23 bridges) because I had screaming customers and this marina is a 3 hour round trip for me. Now don't get the idea that I am totally dissing this product. I really like the way it programs and that settings can be applied without a time consuming reboot. I only wish the SSH terminal allowed other terminal options. All of these are behind MT routers that we use as captive hotspot portals, and we normally make pass-through's in the routers to allow us to remotely administer. Doesn't work. I have also been unsuccessful in talking to the Lucayas through the SSH terminal on the MT router itself. It seems to be a terminal emulation incompatibility issue. The only command you can get to work is F2. I can't find how to change the emulation on either the MT or the Lucaya. Since there's no GUI, I can't use a browser either. I want to continue using them and playing with the mesh, once the units work again! The packaging is also intriguing. The shielding looks excellent! Also- in mesh design, we sometimes have to mount on strand, and this package looks similar to a cable TV amp and may blend nicely in this application, if I can find a professional way to clamp it on. The supplied bracket is kind of goofy. I am going to have to be creative to figure out how to mount this on a power pole or street light arm and not create a hazard that will make us lose our bond. I did note that after only three weeks outside (fresh water marina) the cases looked like they were 2 years old and the brand label on the outside was so sun-faded that it could hardly be read. So- to sum up- 1. Upgrade immediately- even if the units were just received new and just produced. Otherwise its back to Mama for defaulting. 2. Don't ask dumb questions like how do I make a transparent bridge g -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marlon K. Schafer Sent: Wednesday, June 11, 2008 12:46 AM To: WISPA General List Subject: Re: [WISPA] star os config help Where is that? I'm not seeing it at all. marlon - Original Message - From: Mark Nash [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 5:23 PM Subject: Re: [WISPA] star os config help It's on the Interface, under IP addresses. Change the bridge group number from 0 to something else. All interfaces with the same number (other than Zero) will be bridged. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401
Re: [WISPA] star os config help- clarifying my message
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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] star os config help- clarifying my message
I don't think that StarOS will let you put addresses from the same subnet on all interfaces. If you try this AND not notice, it will add the address but disable it (this is shown by the easy to miss * by it). This will result in the same thing though and that is not able to get into the unit. It is best when configuring these units to apply changes but do not save until you are sure of the change. This way to restore all you need to do is power cycle it. - Original Message - From: ralph [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Wednesday, June 11, 2008 5:28 AM Subject: Re: [WISPA] star os config help- clarifying my message 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] easy voip
I live in Missouri and I have one. I have been using it for about two months and the calls work great, but it occasional crashes my computer. I also got one for my sister that lives in California and it is constantly dropping calls. So their network might be a little hinky yet. When I first got mine the ads did not show up, now they are showing up with more frequency. Even being ad driven I still don't understand how these folks are going to make it. Just my .02 On Tue, Jun 10, 2008 at 8:56 PM, Mike Hammett [EMAIL PROTECTED] wrote: http://www.localcallingguide.com/lca_telco.php?ocn_name=YMAXnpa=ocn= That's where they have numbers available. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Chuck McCown - 2 [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 5:25 PM Subject: Re: [WISPA] easy voip I dunno, we are rural and they have numbers out here... - Original Message - From: Frank Muto [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 4:20 PM Subject: Re: [WISPA] easy voip Yes they do, and we all know how well that has worked for the industry. Secondly, they have limited coverage applying mostly to the metro areas. A sister company I work with offers the service, but has greater sales with ATA based providers offering expanded coverage. Frank Muto President FSM Marketing Group, Inc. www.SecureEmailPlus.com - Original Message - From: Wes James [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 5:25 PM Subject: Re: [WISPA] easy voip If you look at the TOS, it is ad-supported. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck McCown - 2 Sent: Tuesday, June 10, 2008 5:15 PM To: WISPA General List Subject: Re: [WISPA] easy voip They seem to work fine. Not sure what the business plan is or how they can do this, but they are working. - Original Message - From: Patrick Shoemaker [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 2:32 PM Subject: Re: [WISPA] easy voip There are at least two VoIP providers here that are WISPA vendor members. I am using one for my customers and would be happy to relate my experiences offlist. I'd encourage you to stay away from any software or PC based VoIP solutions and stick with ATAs. Patrick Shoemaker President, Vector Data Systems LLC [EMAIL PROTECTED] office: (301) 358-1690 x36 mobile: (410) 991-5791 http://www.vectordatasystems.com WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- Victoria Proffer CEO St. Louis Broadband Visit us @ www.StLBroadband.com 314-974-5600 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] star os config help- clarifying my message
Yes- I did look all through the forums first, and Tog's Wiki is really helpful too. We need the experts to continue populating some of the sparse areas and I will try to help as I become more familiar- 'specially if I get these working as mesh radios. I have considerable Tropos and Cisco outdoor mesh experience and am really hoping to find a poor man's mesh. I want to try some of the Ligo mesh too, but can't afford to buy it right now. Ralph -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of George Rogato Sent: Wednesday, June 11, 2008 9:56 AM To: WISPA General List 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: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] mesh throughput?
Good info. Also good to know about the web interface. That's really been my only negative on the Ligo gear. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Hardy Sent: Tuesday, June 10, 2008 8:54 PM To: WISPA General List Subject: Re: [WISPA] mesh throughput? Here are some tests we have run with Full/Half/Quarter channel sizes with Atheros super features (WMM/Fast Frames/ Packet Bursting) on and off: Full: Super Off: 24Mbps Super On: 33Mbps Super On / Turbo: 53Mbps Half: Super Off: 11Mbps Super On: 15Mbps Quarter: Super Off: 6Mbps Super On: 7Mbps * Note that these are with LigoWave 802.11 standard products, and not with LigoPTP :) One note is that compression is not on in these tests, and we have found it will improve throughput a bit. However, you have to be careful because you can get somewhat inflated results when using compression because some throughput test utilities use pretty compressible data. The throughput test tool built into LigoWave (nepim - network pipemeter) can be set to use random data patterns by using the -P random switch in shell. I agree with you Tom; we usually recommend a hard set modulation rate for stable links. You're also correct that half size channels max datarate is 27 (54/2). One more thing to add regarding Tom's post... we are designing a new architecture for the web interface so that it will be much, much faster. More to come later! :) -Matt On Tue, 2008-06-10 at 20:21 -0500, Tom DeReggi wrote: I guess the answer is in what the definition is of Real World :-) For the record my conservative comment was not meant to be against Ligowave, but specific to Atheros Mini PCi Cards in general, regardless of the software platform. I agree if you can get a peak modulation consistently w/ compression, sure you can get the speed. The Ligo MB hardware has the processing power to do the speed, with multiple cards. However, in my real world, we are lucky to get 18 mbps modulations, allthough when doing 20Mhz channels we always try for 36mbps mod if we can. I'm not possitive, but I think the 10Mhz channel may max out at 27mbps modulation as an option, with Atheros. (Although That should be verified with Ligo, as I may be mistaken). The problem with commercial grade services is that they generally don't respond well to frequent modulation changes. If a modulation is bouncing back and forth from 36 to 18 to 24 to 36, etc, it will have very undesirable effects on the End Users' TCP session throughput. We have found it much more advantageous to hard set the Max modulation to a lower number that would result in the least frequent amount of automatic modulation changes. It doesn't matter how fast the radio can test in peak situations, it matters how fast the end user can push their data consistently. Usually the best we can count on consistently is usually closer to 15mbps, in our environment. We bit ourselves in the Back-side to often quoting 10mbps Full Duplex, and only getting 5 mb on way and 10 mbps the other, and having our customers Claim we didn't deliver our SLA, and having to requote/redefine the job. I'm not saying that people can't get 20mbps, some people here, have just clearly stated that it was possible for them. I just suggest planning for the worst, and being conservative in expectation. With that said my comment is not a complaint. I can get qty 4- 15 mbps links out of that one 533 Ligo Box, with 10mhz channels, which is pretty darn amazing. What I liked about Ligo though is their support. They try hard to please. There software is also very easy to navigate and intuitive. Its a bit slow to navigate (compared to StarOS or MikroTik), due to web interface redraw time between screens, but that's not really a big deal. My units have shown to pretty much be install and leave it units, with very little trouble. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Jason Hensley [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Tuesday, June 10, 2008 9:42 AM Subject: Re: [WISPA] mesh throughput? For the record as well, this is with Fast Frames, Packet Bursting, and Compression all turned on. We bounce anywhere from 18-20 meg. Very excited about it and EXTREMELY pleased with the results we've had from the Ligowave gear. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Hensley Sent: Tuesday, June 10, 2008 7:52 AM To: 'WISPA General List' Subject: Re: [WISPA] mesh throughput? Nope, actually getting 20meg off a 10mhz channel in real world high noise environment. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom DeReggi Sent: Tuesday, June 10, 2008 1:44 AM To: WISPA General List Subject: Re: [WISPA] mesh
Re: [WISPA] easy voip
Are you serious? They're going to take off just like metro wifi... they'll be everywhere and everyone will love them. oh, wait... Metro wifi is dead? heh, I guess they will end up the same. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Victoria Proffer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 9:51 AM Subject: Re: [WISPA] easy voip I live in Missouri and I have one. I have been using it for about two months and the calls work great, but it occasional crashes my computer. I also got one for my sister that lives in California and it is constantly dropping calls. So their network might be a little hinky yet. When I first got mine the ads did not show up, now they are showing up with more frequency. Even being ad driven I still don't understand how these folks are going to make it. Just my .02 On Tue, Jun 10, 2008 at 8:56 PM, Mike Hammett [EMAIL PROTECTED] wrote: http://www.localcallingguide.com/lca_telco.php?ocn_name=YMAXnpa=ocn= That's where they have numbers available. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Chuck McCown - 2 [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 5:25 PM Subject: Re: [WISPA] easy voip I dunno, we are rural and they have numbers out here... - Original Message - From: Frank Muto [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 4:20 PM Subject: Re: [WISPA] easy voip Yes they do, and we all know how well that has worked for the industry. Secondly, they have limited coverage applying mostly to the metro areas. A sister company I work with offers the service, but has greater sales with ATA based providers offering expanded coverage. Frank Muto President FSM Marketing Group, Inc. www.SecureEmailPlus.com - Original Message - From: Wes James [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 5:25 PM Subject: Re: [WISPA] easy voip If you look at the TOS, it is ad-supported. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck McCown - 2 Sent: Tuesday, June 10, 2008 5:15 PM To: WISPA General List Subject: Re: [WISPA] easy voip They seem to work fine. Not sure what the business plan is or how they can do this, but they are working. - Original Message - From: Patrick Shoemaker [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Tuesday, June 10, 2008 2:32 PM Subject: Re: [WISPA] easy voip There are at least two VoIP providers here that are WISPA vendor members. I am using one for my customers and would be happy to relate my experiences offlist. I'd encourage you to stay away from any software or PC based VoIP solutions and stick with ATAs. Patrick Shoemaker President, Vector Data Systems LLC [EMAIL PROTECTED] office: (301) 358-1690 x36 mobile: (410) 991-5791 http://www.vectordatasystems.com WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- Victoria Proffer CEO St. Louis Broadband Visit us @ www.StLBroadband.com 314-974-5600 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] star os config help- clarifying my message
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 wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] star os config help- clarifying my message
I agree with you, Marlon on the documentation/ease-of-use. I gave up using Tranzeos for StarOS because of its flexibility and powerful boards and the atheros driver available creating an environment with extremely low latency. Tranzeos were/are super-easy. With StarOS, I've gotten over alot of the learning curve, but there is still more to learn. It's for geeks...but once you're there, you're in pretty good shape. My biggest issue as of late is that I have a problem remembering which power supply goes to which board, and remembering which of two ethernet ports is the PoE port on each different type of board. Documentation for StarOS and the equipment it supports is lacking. Just last week I told our engineer that we MUST put PRINTED information in the hands of our installers on the equipment that we use (what power supply to use, which is the PoE ports, which boards can handle the high-powered cards and how many, etc). The equipment and software is very very good, but you have to be at least a semi-geek to understand it. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 8:31 AM Subject: Re: [WISPA] star os config help- clarifying my message 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 wireless@wispa.org 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!
Re: [WISPA] star os config help- clarifying my message
Just a thought. There is some concerted effort from the folks who work with StarOS to create/compile documentation. Here is a very decent effort from Travis TOG http://staros.tog.net/wiki/Main_Page Maybe if more of the folks working with Staros, contribute to the wiki, there will be complete documention set ver quickly. Faisal Imtiaz SnappyDSL.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Nash Sent: Wednesday, June 11, 2008 11:43 AM To: WISPA General List Subject: Re: [WISPA] star os config help- clarifying my message I agree with you, Marlon on the documentation/ease-of-use. I gave up using Tranzeos for StarOS because of its flexibility and powerful boards and the atheros driver available creating an environment with extremely low latency. Tranzeos were/are super-easy. With StarOS, I've gotten over alot of the learning curve, but there is still more to learn. It's for geeks...but once you're there, you're in pretty good shape. My biggest issue as of late is that I have a problem remembering which power supply goes to which board, and remembering which of two ethernet ports is the PoE port on each different type of board. Documentation for StarOS and the equipment it supports is lacking. Just last week I told our engineer that we MUST put PRINTED information in the hands of our installers on the equipment that we use (what power supply to use, which is the PoE ports, which boards can handle the high-powered cards and how many, etc). The equipment and software is very very good, but you have to be at least a semi-geek to understand it. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 8:31 AM Subject: Re: [WISPA] star os config help- clarifying my message 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 wireless@wispa.org 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
Re: [WISPA] star os config help- clarifying my message
Yes, but Marlon's point should not be passed by... It shouldn't be so difficult. It's been around long enough. This hardware and software has made life more difficult for our installers to deal with. I do believe in fairness where appropriate, though... Once installed, it's highly-capable and manageable. I actually don't like the ssh interface vs. the Mikrotik Winbox. However...I do appreciate the ability to run the ssh interface from any computer anywhere and once I get through our firewall, I have access to our entire infrastructure and clients. And since it's not web-based management, it's very responsive and fast. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Faisal Imtiaz [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Wednesday, June 11, 2008 8:52 AM Subject: Re: [WISPA] star os config help- clarifying my message Just a thought. There is some concerted effort from the folks who work with StarOS to create/compile documentation. Here is a very decent effort from Travis TOG http://staros.tog.net/wiki/Main_Page Maybe if more of the folks working with Staros, contribute to the wiki, there will be complete documention set ver quickly. Faisal Imtiaz SnappyDSL.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Nash Sent: Wednesday, June 11, 2008 11:43 AM To: WISPA General List Subject: Re: [WISPA] star os config help- clarifying my message I agree with you, Marlon on the documentation/ease-of-use. I gave up using Tranzeos for StarOS because of its flexibility and powerful boards and the atheros driver available creating an environment with extremely low latency. Tranzeos were/are super-easy. With StarOS, I've gotten over alot of the learning curve, but there is still more to learn. It's for geeks...but once you're there, you're in pretty good shape. My biggest issue as of late is that I have a problem remembering which power supply goes to which board, and remembering which of two ethernet ports is the PoE port on each different type of board. Documentation for StarOS and the equipment it supports is lacking. Just last week I told our engineer that we MUST put PRINTED information in the hands of our installers on the equipment that we use (what power supply to use, which is the PoE ports, which boards can handle the high-powered cards and how many, etc). The equipment and software is very very good, but you have to be at least a semi-geek to understand it. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 8:31 AM Subject: Re: [WISPA] star os config help- clarifying my message 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
Re: [WISPA] star os config help- clarifying my message
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 wireless@wispa.org 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
Re: [WISPA] star os config help- clarifying my message
We started using OLSR a few months ago. Not for the redundant mesh back hauls, but rather the dynamic routing aspect of it. Friday I had to move a sub from one end of our network to an entirely different ap and segmant. All I had to do to make sure his ethernet port handed out the same public IP to him, was change the ip address and essid on his wan port and he was done. No having to add routes through to him. No removing old routes. Just worked when I turned on his radio. Eventually I will start playing connect the ap's for wireless redundancy. ralph wrote: Yes- I did look all through the forums first, and Tog's Wiki is really helpful too. We need the experts to continue populating some of the sparse areas and I will try to help as I become more familiar- 'specially if I get these working as mesh radios. I have considerable Tropos and Cisco outdoor mesh experience and am really hoping to find a poor man's mesh. I want to try some of the Ligo mesh too, but can't afford to buy it right now. Ralph -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of George Rogato Sent: Wednesday, June 11, 2008 9:56 AM To: WISPA General List 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: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] star os config help- clarifying my message
It would be nice if they came more configured, so all we had to do is give a radio an ip addy and set the essid. Mark Nash wrote: Yes, but Marlon's point should not be passed by... It shouldn't be so difficult. It's been around long enough. This hardware and software has made life more difficult for our installers to deal with. I do believe in fairness where appropriate, though... Once installed, it's highly-capable and manageable. I actually don't like the ssh interface vs. the Mikrotik Winbox. However...I do appreciate the ability to run the ssh interface from any computer anywhere and once I get through our firewall, I have access to our entire infrastructure and clients. And since it's not web-based management, it's very responsive and fast. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Faisal Imtiaz [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Wednesday, June 11, 2008 8:52 AM Subject: Re: [WISPA] star os config help- clarifying my message Just a thought. There is some concerted effort from the folks who work with StarOS to create/compile documentation. Here is a very decent effort from Travis TOG http://staros.tog.net/wiki/Main_Page Maybe if more of the folks working with Staros, contribute to the wiki, there will be complete documention set ver quickly. Faisal Imtiaz SnappyDSL.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Nash Sent: Wednesday, June 11, 2008 11:43 AM To: WISPA General List Subject: Re: [WISPA] star os config help- clarifying my message I agree with you, Marlon on the documentation/ease-of-use. I gave up using Tranzeos for StarOS because of its flexibility and powerful boards and the atheros driver available creating an environment with extremely low latency. Tranzeos were/are super-easy. With StarOS, I've gotten over alot of the learning curve, but there is still more to learn. It's for geeks...but once you're there, you're in pretty good shape. My biggest issue as of late is that I have a problem remembering which power supply goes to which board, and remembering which of two ethernet ports is the PoE port on each different type of board. Documentation for StarOS and the equipment it supports is lacking. Just last week I told our engineer that we MUST put PRINTED information in the hands of our installers on the equipment that we use (what power supply to use, which is the PoE ports, which boards can handle the high-powered cards and how many, etc). The equipment and software is very very good, but you have to be at least a semi-geek to understand it. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 8:31 AM Subject: Re: [WISPA] star os config help- clarifying my message 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
Re: [WISPA] star os config help- clarifying my message
Marlon, I have been using Star-OS since the beginning here. Means four years of using it. It is the fastest, easiest, and best performing of anything I've tried. They're so right about not bridging, but if you need any assistance, give me a shout. It's not even that far if you want a hands on demo on how to set things up, and I don't mind making the trip. Mark insert witty tagline here - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 8:31 AM Subject: Re: [WISPA] star os config help- clarifying my message 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 wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
[WISPA] Voip over Wireless
We are a small wisp and have been asked about VOIP and I am just starting to research it. Vonage has not worked on our network. What service is recommended by all of you that does not eat your networks alive with large packets and Keep alive. FYI, I am looking for a service not to build my own. Steve Barnes Executive Manager PCS-WIN RCWiFi Wireless Internet Service (765)584-2288 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] star os config help- clarifying my message
Yes, but only the clients I think. The APs/backhauls/distros should need to be configured. I'd say that 99.99% of the WAR1's are configured as a NAT router. Then there are those who use them as bridges... ;) Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: George Rogato [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 9:35 AM Subject: Re: [WISPA] star os config help- clarifying my message It would be nice if they came more configured, so all we had to do is give a radio an ip addy and set the essid. Mark Nash wrote: Yes, but Marlon's point should not be passed by... It shouldn't be so difficult. It's been around long enough. This hardware and software has made life more difficult for our installers to deal with. I do believe in fairness where appropriate, though... Once installed, it's highly-capable and manageable. I actually don't like the ssh interface vs. the Mikrotik Winbox. However...I do appreciate the ability to run the ssh interface from any computer anywhere and once I get through our firewall, I have access to our entire infrastructure and clients. And since it's not web-based management, it's very responsive and fast. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Faisal Imtiaz [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Wednesday, June 11, 2008 8:52 AM Subject: Re: [WISPA] star os config help- clarifying my message Just a thought. There is some concerted effort from the folks who work with StarOS to create/compile documentation. Here is a very decent effort from Travis TOG http://staros.tog.net/wiki/Main_Page Maybe if more of the folks working with Staros, contribute to the wiki, there will be complete documention set ver quickly. Faisal Imtiaz SnappyDSL.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Nash Sent: Wednesday, June 11, 2008 11:43 AM To: WISPA General List Subject: Re: [WISPA] star os config help- clarifying my message I agree with you, Marlon on the documentation/ease-of-use. I gave up using Tranzeos for StarOS because of its flexibility and powerful boards and the atheros driver available creating an environment with extremely low latency. Tranzeos were/are super-easy. With StarOS, I've gotten over alot of the learning curve, but there is still more to learn. It's for geeks...but once you're there, you're in pretty good shape. My biggest issue as of late is that I have a problem remembering which power supply goes to which board, and remembering which of two ethernet ports is the PoE port on each different type of board. Documentation for StarOS and the equipment it supports is lacking. Just last week I told our engineer that we MUST put PRINTED information in the hands of our installers on the equipment that we use (what power supply to use, which is the PoE ports, which boards can handle the high-powered cards and how many, etc). The equipment and software is very very good, but you have to be at least a semi-geek to understand it. Mark Nash UnwiredWest 78 Centennial Loop Suite E Eugene, OR 97401 541-998- 541-998-5599 fax http://www.unwiredwest.com - Original Message - From: Marlon K. Schafer [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Wednesday, June 11, 2008 8:31 AM Subject: Re: [WISPA] star os config help- clarifying my message 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
Re: [WISPA] Voip over Wireless
Hi Steve, VoIP generally uses very small packets...and those are the ones that tax a network. What you most likely need is QoS set up further out in your network. Regards, Jeff ImageStream -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Barnes Sent: Wednesday, June 11, 2008 12:49 PM To: 'WISPA General List' Subject: [WISPA] Voip over Wireless We are a small wisp and have been asked about VOIP and I am just starting to research it. Vonage has not worked on our network. What service is recommended by all of you that does not eat your networks alive with large packets and Keep alive. FYI, I am looking for a service not to build my own. Steve Barnes Executive Manager PCS-WIN RCWiFi Wireless Internet Service (765)584-2288 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Voip over Wireless
Large packets are your friend, the small ones are not. All VoIP is small packets. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Steve Barnes [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Wednesday, June 11, 2008 11:48 AM Subject: [WISPA] Voip over Wireless We are a small wisp and have been asked about VOIP and I am just starting to research it. Vonage has not worked on our network. What service is recommended by all of you that does not eat your networks alive with large packets and Keep alive. FYI, I am looking for a service not to build my own. Steve Barnes Executive Manager PCS-WIN RCWiFi Wireless Internet Service (765)584-2288 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Voip over Wireless
If you're looking at implementing VoIP with a system that's standards based, I'd try to find something that utilizes the Atheros Super G capabilities (WMM, Packet Bursting, Compression, Fast Frames). These can really help with VoiP in two main ways: WMM - A subset of 802.11e (QoS). Prioritizes data traffic based on 4 categories (Voice, Video, Best Effort, and Background)... VoIP automatically gets prioritized. and Fast Frames - Packet aggregation which helps with the small packets issue :) For reference: http://www.atheros.com/pt/whitepapers/atheros_superg_whitepaper.pdf -Matt On Wed, 2008-06-11 at 16:40 -0500, Mike Hammett wrote: Large packets are your friend, the small ones are not. All VoIP is small packets. -- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com - Original Message - From: Steve Barnes [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Wednesday, June 11, 2008 11:48 AM Subject: [WISPA] Voip over Wireless We are a small wisp and have been asked about VOIP and I am just starting to research it. Vonage has not worked on our network. What service is recommended by all of you that does not eat your networks alive with large packets and Keep alive. FYI, I am looking for a service not to build my own. Steve Barnes Executive Manager PCS-WIN RCWiFi Wireless Internet Service (765)584-2288 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org 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: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
[WISPA] Rapid Link Improves Working Capital Position by Over $1, 000, 000
- Long-Standing Texas State Tax Liability Settled - OMAHA, NE - June 11, 2008 - Rapid Link, Incorporated (OTCBB: RPID), a leading provider of WiMax and Communication Services, announced today the final settlement, and release from any ongoing liability, of a long-standing sales tax dispute in the State of Texas. A result of the settlement was the elimination of a $1,062,000 current liability. The original liability was due to an assessment by the State of Texas for past due sales tax. This assessment stemmed from an alleged underpayment of sales taxes by a now dissolved subsidiary of Rapid Link Incorporated. At no time was there a judgment against Rapid Link Incorporated; however the potential for a future judgment necessitated the accrual of this potential liability. John Jenkins, Chief Executive Officer of Rapid Link states, Though it was a long time coming, we are very pleased to settle this issue once and for all, and again show our shareholders that we are serious about our goal to attain a net positive working capital position. This is just one of many steps we are taking to do just that. Chris Canfield, Chief Financial Officer of Rapid Link states, Extinguishing this liability has improved our balance sheet significantly. In the past year Rapid Link has seen its Chief Executive convert $900,000 of debt into equity at above market prices, announced the extensions of virtually all short-term notes into long-term notes due in 2011, and raised significant capital, all of which has dramatically improved our working capital position. We are confident we can now aggressively grow our business without the need to seek additional capital. About Rapid Link, Incorporated. Rapid Link, Incorporated is a Diversified Communication Services company, supplying bundled internet and voice services to Business and Residential customers. Rapid Link offers broadband access via its own facilities to ensure fast and reliable delivery of its content. As a leading licensed WiMAX carrier, Rapid Link is on the cutting edge of this exciting new technology. We are one of the only carriers that can offer an end-to-end solution for our customers without a dependency on any other company's resources. For more information about Rapid Link, visit www.rapidlink.com. Safe Harbor Statement under the Private Securities Litigation Reform Act of 1995: With the exception of historical information, the statements set forth above include forward-looking statements that involve risk and uncertainties. The Company wishes to caution readers that a number of important factors could cause actual results to differ materially from those in the forward-looking statements. Those factors include, but are not limited to, risks and uncertainties such as the failure to satisfy contractually agreed upon closing conditions that may delay or prevent the closings of subsequent debt financings contemplated by the applicable agreements; the risk factors noted in the Company's filings with the United States Securities and Exchange Commission, such as the trading price of the Company's common stock reaching levels that would cause funding to occur; the rapidly changing nature of technology, evolving industry standards and frequent introductions of new products, services and enhancements by competitors; the competitive nature of the markets for the Company's products and services; the Company's ability to gain market acceptance for its products and services; the Company's ability to fund its operational growth; the Company's ability to attract and retain skilled personnel; the Company's ability to diversify its revenue streams and customer concentrations; and the Company's reliance on third-party suppliers. For more information: Rapid Link, Incorporated Investor Relations 402-392-7561 Or: DME Capital Investor Relations David Elias 516-967-0205 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Voip over Wireless
Steve What doesn't work with Vonage? Is it the quality of the call or the service itself? Maybe I can help abit. George Steve Barnes wrote: We are a small wisp and have been asked about VOIP and I am just starting to research it. Vonage has not worked on our network. What service is recommended by all of you that does not eat your networks alive with large packets and Keep alive. FYI, I am looking for a service not to build my own. Steve Barnes Executive Manager PCS-WIN RCWiFi Wireless Internet Service (765)584-2288 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
