RE: [WISPA] Intro/Karlnet/YDI/Terabeam/Proxim/Turbocell
Yeah, I still can imagine why there are some wips still homebrewing gear that ends up more expensive that wisp-engineered products on the market like canopy, trango ect... We were in a same spot with some 11b gear deployed in some areas... last august we decided to just cough up some cash and change all those subs (100+) to Canopy best money spent, never looked back Gino A. Villarini, Aeronet Wireless Broadband Corp. [EMAIL PROTECTED] www.aeronetpr.com 787.767.7466 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Huppenthal Sent: Saturday, December 10, 2005 1:44 AM To: WISPA General List Subject: Re: [WISPA] Intro/Karlnet/YDI/Terabeam/Proxim/Turbocell Go get some Canopy client radios for $260 each, complete - check the performance, ease to install and setup. We did homebrew for quite a while and it has its downside as we're seeing. Just my opinion. You get a nice spectrum analyzer built-in, 2 minute setup, 2 minute test once its placed. Audible signal strength - no pc needed on the ladder. There are lots of solutions. 5.2 / 5.7 ghz Moto stuff runs thousands of subscribers. I'm not affliated with Moto/Canopy and don't ask me to sell you anything. Best wishes. Mark Nash wrote: Thanks Rick.. I've heard alot about these WRAP boards. Is this something we would put together ourselves or are there products available. What are the costs like? I guess I'd really be interested in what I should be doing for CPE going on, assuming we can still get the Turbocell licenses (see post from Blair Davis re: Winncomm continuing to be able to sell Turbocell licenses). Mark Nash Network Engineer UnwiredOnline.Net 325 Holly Street Junction City, OR 97448 541-998- 541-998-5599 fax http://www.uwol.net - Original Message - From: Rick Harnish [EMAIL PROTECTED] To: 'WISPA General List' wireless@wispa.org Sent: Thursday, December 08, 2005 9:25 AM Subject: RE: [WISPA] Intro/Karlnet/YDI/Terabeam/Proxim/Turbocell Mark, Contact me offlist as we are successfully deploying WRAP boards with Compact Flash loaded with Turbocell. My pains are compounded about 4 times as I had about 24 Turbocell POPs when this all started. Rick Harnish President OnlyInternet Broadband Wireless, Inc. 260-827-2482 Office 260-307-4000 Cell 260-918-4340 VoIP www.oibw.net [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Nash Sent: Thursday, December 08, 2005 12:01 PM To: WISPA General List Subject: [WISPA] Intro/Karlnet/YDI/Terabeam/Proxim/Turbocell Hello to the list... My name is Mark Nash and I own operate a little WISP of about 300 customers in Oregon. For CPE, I started out using Breezecom 2.4GHz FH radios then switched to Karlnet RSU's loaded w/Turbocell. Then the YDI/Terabeam/Proxim series of mergers acquisitions happened and I've got products from all companies but they are all Turbocell CPE. We have 6 WiPops surrounding our customer base (rural southern Willamette Valley). We're using Trango backhauls...I started out using them simply because of their low cost and advertised bandwidth. I still have two in use from when the company was called Sunstream (I think it was 2002). I remain happy about that decision. We started out with a bridged network then ARP changed my tune and we went to a routed design. OK, so...there it is. For those of you who know what's going on with Turbocell from the new Proxim, you probably know that I'm not happy as they have set out to discontinue the Turbocell client software. So I will soon have to purchase new AP's and shift some customers around because I won't be able to purchase Turbocell-based devices. That's the word from Proxim. So...anyone heard any differently? I've also asked Proxim if we can 'downgrade' our Turbocell products to 802.11b and they are saying 'no'. It's a you-know-what sandwich from which I'd rather not take a bite. Does anyone feel my pain? Any way around these issues aside from replacing CPE? Regards, Mark Nash Network Engineer UnwiredOnline.Net 325 Holly Street Junction City, OR 97448 http://www.uwol.net 541-998- 541-998-5599 fax -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] P2P Worm Monitoring/Alerting/Control
We were doing quite a bit with our 3640 but from my experience the box did not hold up well under load. Be cautious when considering doing traffic shaping with your 3640. Watch the memory and CPU load closely. Scriv John Thomas wrote: Mark, go over to http://www.mikrotik.com/download.html#dude See if it does some/all of what you need. As for limiting/shaping, your 3640 may do what you need. John Mark Nash wrote: I'm at the point on my network now that I really need to control unnecessary bandwidth usage. The biggest problem is the p2p users with their excessive upload, and worms come in a close second. My network is comprised of a Cisco 3640, Cisco C4840G L3 switch for segmenting, and Dell 3324 managed switches. I have run ntop in the past but I believe it only reports interactively through the web interface. I wouldn't consider myself too far off from obtaining an SNMP station/software like SNMPc. I'm needing to implement a solution that will monitor, alert on, and control this type of traffic. Either not pass it or rate-limit it. I'm interested in solutions that have been implemented, home-grown, tested, failed, etc. Thanks in advance... Mark Nash Network Engineer UnwiredOnline.Net 325 Holly Street Junction City, OR 97448 http://www.uwol.net 541-998- 541-998-5599 fax -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
[WISPA] Re: [wisp] Another reason to love the Barracuda...
Matt Larsen - Lists wrote: Our mail server locked up on Wednesday afternoon with some hard drive weirdness. snip snip except for the 26 hours that the mail server was not accepting email. However, our Barracuda box was accepting the messages and storing them. After a phone call to Barracuda Networks, their tech support logged into the box and it is spending the next six hours resending all 30,000+ messages. Oh yeah! For anyone who is on the fence, jump over to the Barracuda side. My Barracuda box has been a genuine lifesaver, beyond just stopping spam. I'm really glad this worked out for you. However, this particular incident could have been avoided by using backup MX boxes. Further, 26 hours isn't a long outage. It's a big inconvient outage, and no doubt would upset folks pretty badly. But no email server worth it's salt should dump it's spool and put out an undeliverable bounce in that amount of time. I am strongly of the opinion that nearly all of the woes we currently associate with email stem from having poorly administered email servers and email systems. (No, I am not implying this is the case with you, quite the opposite, you obviously care about your service, to take the time, money and effort to use such a service). Adding yet still another blind layer of bureaucratic 'not my faults' to the chain does little in the long run other than just add another patch (and expensive one) to a very leaky infrastructure. I'm glad you are happy with your solution. But personally, I see this kinda fix as much more part of the problem Oh? No, we use some *-insert outsourced plausible deniability clause here- service, so it isn't our problem rather than part of a solution. Note *= usual suspect, postini, symantic email gateway, -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] P2P Worm Monitoring/Alerting/Control
We use bandwidth shaping on *nix. works fine. currently the profile for one site manages 500+ IP based up and downstream. Its one of our few home-brew items. Of course, its all open source, so I don't need to worry about support on this particular item. John Thomas wrote: Mark, go over to http://www.mikrotik.com/download.html#dude See if it does some/all of what you need. As for limiting/shaping, your 3640 may do what you need. John Mark Nash wrote: I'm at the point on my network now that I really need to control unnecessary bandwidth usage. The biggest problem is the p2p users with their excessive upload, and worms come in a close second. My network is comprised of a Cisco 3640, Cisco C4840G L3 switch for segmenting, and Dell 3324 managed switches. I have run ntop in the past but I believe it only reports interactively through the web interface. I wouldn't consider myself too far off from obtaining an SNMP station/software like SNMPc. I'm needing to implement a solution that will monitor, alert on, and control this type of traffic. Either not pass it or rate-limit it. I'm interested in solutions that have been implemented, home-grown, tested, failed, etc. Thanks in advance... Mark Nash Network Engineer UnwiredOnline.Net 325 Holly Street Junction City, OR 97448 http://www.uwol.net 541-998- 541-998-5599 fax -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
