Re: [WISPA] FreeBSD hackers.... Needed for WISP related product...
Does this rely on some unpublished feature of the current Atheros chipset which could disappear in the next evolution making the project obsolete and the effort wasted? Is there a URL for the project? Greg On Dec 1, 2009, at 12:56 AM, MDK wrote: Actually, it's far better than cost-effective. It's flexible, in both hardware and capabilities.Firewall, routing, routing daemons, and other things. Frankly, I find the physical aspects of the Airmax stuff frustratingly limited. I've grown fond of my immense ability to do creative stuff with Star-OS and a wide array of physical forms - especially since much of my network relies on low power consumption. AirMax, deployed as an AP and clients... seems ok.But that's only a small part of a good network. -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:51 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Availability is supposedly resolved. We'll see. Routing... there is a full SDK. You can do anything you want on those things. The new ones have 400+MHz proc's, plenty to do some routing/firewalling. I just can't see a home grown solution like you're proposing being cost-effective. We spent about 2 months on a project just like this, and started to have some pretty awesome performance and results. Then UBNT stuff came out. On Mon, Nov 30, 2009 at 9:39 PM, MDK rea...@muddyfrogwater.us wrote: Given UBNT's record of unavailability of product, and the inability to route via the interface, I vastly prefer this to UBNT's products. Now, mind you, I'm not really putting them down, but this is an excellent infrastructure tool...Routing and other capabilities that vastly exceed some better known... -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:25 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: Travis Johnson t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net -- 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:
Re: [WISPA] FreeBSD hackers.... Needed for WISP related product...
No, I have no url for this. I'm trying to find out and see if there's enough people interested to go through that level of work. -- From: os10ru...@gmail.com Sent: Tuesday, December 01, 2009 12:02 AM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Does this rely on some unpublished feature of the current Atheros chipset which could disappear in the next evolution making the project obsolete and the effort wasted? Is there a URL for the project? Greg On Dec 1, 2009, at 12:56 AM, MDK wrote: Actually, it's far better than cost-effective. It's flexible, in both hardware and capabilities.Firewall, routing, routing daemons, and other things. Frankly, I find the physical aspects of the Airmax stuff frustratingly limited. I've grown fond of my immense ability to do creative stuff with Star-OS and a wide array of physical forms - especially since much of my network relies on low power consumption. AirMax, deployed as an AP and clients... seems ok.But that's only a small part of a good network. -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:51 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Availability is supposedly resolved. We'll see. Routing... there is a full SDK. You can do anything you want on those things. The new ones have 400+MHz proc's, plenty to do some routing/firewalling. I just can't see a home grown solution like you're proposing being cost-effective. We spent about 2 months on a project just like this, and started to have some pretty awesome performance and results. Then UBNT stuff came out. On Mon, Nov 30, 2009 at 9:39 PM, MDK rea...@muddyfrogwater.us wrote: Given UBNT's record of unavailability of product, and the inability to route via the interface, I vastly prefer this to UBNT's products. Now, mind you, I'm not really putting them down, but this is an excellent infrastructure tool...Routing and other capabilities that vastly exceed some better known... -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:25 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: Travis Johnson t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net -- 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] 20 mile link
My calcs show that at 20 miles 30dB antennas and a nice low 20dB radio output will give you a -58 rssi. Should be easy for most any gear out there to run at least 10 megs. I've been REALLY happy with Airaya radios (www.airaya.com). For cheaper stuff I've also had good luck lately with MT gear. marlon - Original Message - From: RickG rgunder...@gmail.com To: WISPA General List wireless@wispa.org Sent: Monday, November 30, 2009 7:22 PM Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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] A Ridiculous Failure of Critical Infrastructure
Mediacomm was having some bad equipment problems in Marshalltown or Des Moines a couple months ago. It was on a hand off to Sprint on some fiber shelf. It bit us twice, each on a Sunday, for most of the day. After the second episode, which apparently happened after scheduled maintenance, I am convinced the big boys decided to mess with a couple little guys. Sunday outages usually affect residential users, which are my bread and butter. Unfortunately, I didn't have enough sense to have my upstream provider supply me with a map of exactly how the traffic was routed, and the outages affected my primary connection AND my backup. Seems both Dynamic Broadband and Mediacomm hand off to Sprint here in this part of Iowa. So, even my back-up as currently configured can be at risk. Needless to say, I have a winter project to engineer something going to the east from here. Matt, I hope they get it figured out for you guys soon. If you're anything like me, all hairs are already gray. Mike At 01:54 AM 12/1/2009, you wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
MAKE news. Matt Larsen - Lists wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/ -- Randy Cosby Vice President InfoWest, Inc 435-674-0165 x 2010 http://www.infowest.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/
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
How far away from Illinois are you? - Scott Piehn - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 7:52 AM Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure Mediacomm was having some bad equipment problems in Marshalltown or Des Moines a couple months ago. It was on a hand off to Sprint on some fiber shelf. It bit us twice, each on a Sunday, for most of the day. After the second episode, which apparently happened after scheduled maintenance, I am convinced the big boys decided to mess with a couple little guys. Sunday outages usually affect residential users, which are my bread and butter. Unfortunately, I didn't have enough sense to have my upstream provider supply me with a map of exactly how the traffic was routed, and the outages affected my primary connection AND my backup. Seems both Dynamic Broadband and Mediacomm hand off to Sprint here in this part of Iowa. So, even my back-up as currently configured can be at risk. Needless to say, I have a winter project to engineer something going to the east from here. Matt, I hope they get it figured out for you guys soon. If you're anything like me, all hairs are already gray. Mike At 01:54 AM 12/1/2009, you wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
Scott, We are a little over 100 miles west of the Quad Cities, close to hwy 30, just east of central Iowa. Your thoughts? Mike At 08:00 AM 12/1/2009, you wrote: How far away from Illinois are you? - Scott Piehn - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 7:52 AM Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure Mediacomm was having some bad equipment problems in Marshalltown or Des Moines a couple months ago. It was on a hand off to Sprint on some fiber shelf. It bit us twice, each on a Sunday, for most of the day. After the second episode, which apparently happened after scheduled maintenance, I am convinced the big boys decided to mess with a couple little guys. Sunday outages usually affect residential users, which are my bread and butter. Unfortunately, I didn't have enough sense to have my upstream provider supply me with a map of exactly how the traffic was routed, and the outages affected my primary connection AND my backup. Seems both Dynamic Broadband and Mediacomm hand off to Sprint here in this part of Iowa. So, even my back-up as currently configured can be at risk. Needless to say, I have a winter project to engineer something going to the east from here. Matt, I hope they get it figured out for you guys soon. If you're anything like me, all hairs are already gray. Mike At 01:54 AM 12/1/2009, you wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/ WISPA Wants You! Join today! http://signup.wispa.org/
[WISPA] Ubiquiti PTMP Antenna Selection
Looking for input on which antennas to use Was mentioned briefly on one of the lists that using a 16-120 instead of a 19-120 would give better coverage, We have 7 or so 19-120's deployed and they just seem to be very particular. seems about 60 degree wide, and 2 mile out sweet spot. Looking based on covering out to 5 miles max (think that is the current limit of NS5M) tower is 200 - 250 on a hill. could be up to 350' above people or tower (antenna) is 100' above people 360 degree around tower Apologies if this is the wrong list, can't keep them straight with what is allowed on which. - Scott Piehn 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] A Ridiculous Failure of Critical Infrastructure
Timing of this Failure of Critical Infrastructure seems suspect to Charter's bankruptcy. All existing outstanding shares have been cancelled. I wonder if Paul Allen somehow left Qwest holding the bag like he did the rest of his shareholders...just a thought. http://finance.yahoo.com/news/Charter-Communications-bw-3756327554.html?x=0; .v=1 Charter hasn't made a profit since 1999...this was inevitable. Best, Brad -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Matt Larsen - Lists Sent: Tuesday, December 01, 2009 1:54 AM To: Telecom Regulation the Internet; WISPA General List; motorola-us...@wispa.org Subject: [WISPA] A Ridiculous Failure of Critical Infrastructure Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
We are tapped into fiber about 10 miles from Iowa on Illinois. Traffic runs to Chicago, not across sprint. Last I knew, Iowa had lots of options, but if they don't pan out, the neighbor between us youSQ might have an option was hoping to offer an option, but 100 miles is probably to far - Scott Piehn - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 8:20 AM Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure Scott, We are a little over 100 miles west of the Quad Cities, close to hwy 30, just east of central Iowa. Your thoughts? Mike At 08:00 AM 12/1/2009, you wrote: How far away from Illinois are you? - Scott Piehn - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 7:52 AM Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure Mediacomm was having some bad equipment problems in Marshalltown or Des Moines a couple months ago. It was on a hand off to Sprint on some fiber shelf. It bit us twice, each on a Sunday, for most of the day. After the second episode, which apparently happened after scheduled maintenance, I am convinced the big boys decided to mess with a couple little guys. Sunday outages usually affect residential users, which are my bread and butter. Unfortunately, I didn't have enough sense to have my upstream provider supply me with a map of exactly how the traffic was routed, and the outages affected my primary connection AND my backup. Seems both Dynamic Broadband and Mediacomm hand off to Sprint here in this part of Iowa. So, even my back-up as currently configured can be at risk. Needless to say, I have a winter project to engineer something going to the east from here. Matt, I hope they get it figured out for you guys soon. If you're anything like me, all hairs are already gray. Mike At 01:54 AM 12/1/2009, you wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] 20 mile link
Rick: You have been getting some good advice here. I am not a networking guru and have never played one on TV, but do know a thing or two about RF. It seems with your physical layout you may have an opportunity for some space diversity. A simple link will probably serve you with 3 nines or so. If infrequent outages will sit OK with the user, then engineer a link with single radios. If you use some of the more inexpensive radio solutions as proffered here, you could put up two links with 20' to 30' of physical separation. Or, one dish on the water tower, and two on the new tower. The single one could be the AP and the other two remote ones stations. You could use an MT router running OSPF with one having a higher cost than the other. If one failed, the other would take over. My fear of a 20 mile link would be those atmospheric events we sometimes see -- tropospheric ducting. I would be curious what you come up with. Mike At 09:22 PM 11/30/2009, you wrote: Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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] A Ridiculous Failure of Critical Infrastructure
I appreciate the gesture. Iowa does have a lot of options; just not in my area which is very rural. Qwest has fiber to the home northwest of me. I am trying to engineer another backhaul from a point there back to my tower. The wheels of progress sometimes turn slowly. Mike At 08:27 AM 12/1/2009, you wrote: We are tapped into fiber about 10 miles from Iowa on Illinois. Traffic runs to Chicago, not across sprint. Last I knew, Iowa had lots of options, but if they don't pan out, the neighbor between us youSQ might have an option was hoping to offer an option, but 100 miles is probably to far - Scott Piehn - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 8:20 AM Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure Scott, We are a little over 100 miles west of the Quad Cities, close to hwy 30, just east of central Iowa. Your thoughts? Mike At 08:00 AM 12/1/2009, you wrote: How far away from Illinois are you? - Scott Piehn - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 7:52 AM Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure Mediacomm was having some bad equipment problems in Marshalltown or Des Moines a couple months ago. It was on a hand off to Sprint on some fiber shelf. It bit us twice, each on a Sunday, for most of the day. After the second episode, which apparently happened after scheduled maintenance, I am convinced the big boys decided to mess with a couple little guys. Sunday outages usually affect residential users, which are my bread and butter. Unfortunately, I didn't have enough sense to have my upstream provider supply me with a map of exactly how the traffic was routed, and the outages affected my primary connection AND my backup. Seems both Dynamic Broadband and Mediacomm hand off to Sprint here in this part of Iowa. So, even my back-up as currently configured can be at risk. Needless to say, I have a winter project to engineer something going to the east from here. Matt, I hope they get it figured out for you guys soon. If you're anything like me, all hairs are already gray. Mike At 01:54 AM 12/1/2009, you wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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] Looking for an iDirect Partner
Is anyone an iDirect Partner? I may have a lead. Contact me off-list. - Cliff 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] Iowa Telecom a.k.a Windstream
My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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] Iowa Telecom a.k.a Windstream
If this is their install truck, I don't think you have to worry about much. [image: ?ui=2view=attth=1254ad61273873f9attid=0.1disp=attdrealattid=ii_1254ad61273873f9zw] LOL On Tue, Dec 1, 2009 at 8:04 AM, Mike m...@aweiowa.com wrote: My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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/ index_r6_c5.jpg 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] 20 mile link
At first I was like huh? but thinking of the now and present, the Rockets are new and the longevity has yet to be tested. I have both UBNT and MT backhauls, love UBNT to no end but it's from the ease of use aspect. My UBNT needs to be taken care of from time to time, the MT is just put up and forgotten about. Sucks but that's how it is. Not sure why that is, maybe Ubiquiti seems to always be pushing the envelope so logically they'll hit snags. I'm a geek, I like the unknown so I put up with the snags but as Travis said in a roundabout way, if you want stability and something you don't want to worry about, go with the MT. I'd go one further with his list though and use the R52N cards. Bob- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Travis Johnson Sent: Tuesday, December 01, 2009 12:44 AM To: WISPA General List Subject: Re: [WISPA] 20 mile link I guess if you don't need a reliable, stable product, this is the answer. However, I have MT backhaul links that have been up solid for over 3 years now. No ethernet issues, no heat issues, no firmware issues. Travis Microserv Jayson Baker wrote: (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson mailto:t...@ida.net t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG mailto:rgunder...@gmail.com rgunder...@gmail.com mailto:rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks mailto:wi...@3-db.net wi...@3-db.net mailto:wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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] FreeBSD hackers.... Needed for WISP related product...
I thought the same thing. UBNT is already trying to work the ACK out of the Airmax, was supposed to be out in the newest firmware but it's still there. So we'll see ACK gone soon already in their airmax line, which is TDMA MIMO. I'm sure someone can put their own twist on it as well for another propriety system but it would have to add a lot to what Ubiquiti is already doing to get much attention from me. Possibly as a third party open source firmware it could have a life. Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 11:25 PM To: WISPA General List Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: Travis Johnson t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net -- 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/ 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] 20 mile link
I think the Rockets are going to be great, but right now today the best software is a beta version of 5.1. That pretty much says it all. We have pulled all our MikroTik N links back out. 4.0beta3 was pretty good, but N wireless performance and stability took a real nosedive with the release version of 4.0-4.2 IMHO. We are back on XR-5s with either 20 or 40MHz channels for backhaul and get a rock-solid 30-60Mbits as a result. I don't see moving to anything else until MT resolves their N driver issues, plus releases the new version of Nstreme that is compatible with N cards, or UBNT completes their M series firmware tuning. Not sure which will happen first, but with the AH series RouterBoards and XR-5s we are sitting pretty in the meantime. PS We think the AH boards are worth the extra money if you have to run Torch or the Bandwidth Tester for troubleshooting. Both tools run much better on the bigger processors, and the cost differential to get this extra performance is minimal for a major backhaul. George -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Robert West Sent: Tuesday, December 01, 2009 10:23 AM To: 'WISPA General List' Subject: Re: [WISPA] 20 mile link At first I was like huh? but thinking of the now and present, the Rockets are new and the longevity has yet to be tested. I have both UBNT and MT backhauls, love UBNT to no end but it's from the ease of use aspect. My UBNT needs to be taken care of from time to time, the MT is just put up and forgotten about. Sucks but that's how it is. Not sure why that is, maybe Ubiquiti seems to always be pushing the envelope so logically they'll hit snags. I'm a geek, I like the unknown so I put up with the snags but as Travis said in a roundabout way, if you want stability and something you don't want to worry about, go with the MT. I'd go one further with his list though and use the R52N cards. Bob- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Travis Johnson Sent: Tuesday, December 01, 2009 12:44 AM To: WISPA General List Subject: Re: [WISPA] 20 mile link I guess if you don't need a reliable, stable product, this is the answer. However, I have MT backhaul links that have been up solid for over 3 years now. No ethernet issues, no heat issues, no firmware issues. Travis Microserv Jayson Baker wrote: (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson mailto:t...@ida.net t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG mailto:rgunder...@gmail.com rgunder...@gmail.com mailto:rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks mailto:wi...@3-db.net wi...@3-db.net mailto:wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG
Re: [WISPA] 20 mile link
George, Glad to see it's not just us. We put in some MT N links when 4 was still beta. It worked awesome. Awesome. Then, somehow, the units have found their way into the upgrade stream, and performance sucks now. After pulling our hair out trying to figure out the problem, we choked it up to firmware. Like I said, glad to see it's not just us. We've already made the decision to more most of those to Rocket M links. We'll see. Jayson On Tue, Dec 1, 2009 at 8:35 AM, George Morris ghmor...@candlelight.cawrote: I think the Rockets are going to be great, but right now today the best software is a beta version of 5.1. That pretty much says it all. We have pulled all our MikroTik N links back out. 4.0beta3 was pretty good, but N wireless performance and stability took a real nosedive with the release version of 4.0-4.2 IMHO. We are back on XR-5s with either 20 or 40MHz channels for backhaul and get a rock-solid 30-60Mbits as a result. I don't see moving to anything else until MT resolves their N driver issues, plus releases the new version of Nstreme that is compatible with N cards, or UBNT completes their M series firmware tuning. Not sure which will happen first, but with the AH series RouterBoards and XR-5s we are sitting pretty in the meantime. PS We think the AH boards are worth the extra money if you have to run Torch or the Bandwidth Tester for troubleshooting. Both tools run much better on the bigger processors, and the cost differential to get this extra performance is minimal for a major backhaul. George -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Robert West Sent: Tuesday, December 01, 2009 10:23 AM To: 'WISPA General List' Subject: Re: [WISPA] 20 mile link At first I was like huh? but thinking of the now and present, the Rockets are new and the longevity has yet to be tested. I have both UBNT and MT backhauls, love UBNT to no end but it's from the ease of use aspect. My UBNT needs to be taken care of from time to time, the MT is just put up and forgotten about. Sucks but that's how it is. Not sure why that is, maybe Ubiquiti seems to always be pushing the envelope so logically they'll hit snags. I'm a geek, I like the unknown so I put up with the snags but as Travis said in a roundabout way, if you want stability and something you don't want to worry about, go with the MT. I'd go one further with his list though and use the R52N cards. Bob- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Travis Johnson Sent: Tuesday, December 01, 2009 12:44 AM To: WISPA General List Subject: Re: [WISPA] 20 mile link I guess if you don't need a reliable, stable product, this is the answer. However, I have MT backhaul links that have been up solid for over 3 years now. No ethernet issues, no heat issues, no firmware issues. Travis Microserv Jayson Baker wrote: (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson mailto:t...@ida.net t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG mailto:rgunder...@gmail.com rgunder...@gmail.com mailto:rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks mailto:wi...@3-db.net wi...@3-db.net mailto:wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on
Re: [WISPA] FreeBSD hackers.... Needed for WISP related product...
Exactly! You had how many people working on your project? What resources did you have available? Then Ubiquiti comes in and trumps it all! With that I'd just do a wait and see for what UBNT comes out with. I'm sure there isn't much they haven't been trying that we couldn't think of ourselves. I'm sure even though you feel those 2 months were wasted that you got a lot of learning from it. That's invaluable no matter how you look at it. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 11:51 PM To: WISPA General List Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Availability is supposedly resolved. We'll see. Routing... there is a full SDK. You can do anything you want on those things. The new ones have 400+MHz proc's, plenty to do some routing/firewalling. I just can't see a home grown solution like you're proposing being cost-effective. We spent about 2 months on a project just like this, and started to have some pretty awesome performance and results. Then UBNT stuff came out. On Mon, Nov 30, 2009 at 9:39 PM, MDK rea...@muddyfrogwater.us wrote: Given UBNT's record of unavailability of product, and the inability to route via the interface, I vastly prefer this to UBNT's products. Now, mind you, I'm not really putting them down, but this is an excellent infrastructure tool...Routing and other capabilities that vastly exceed some better known... -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:25 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: Travis Johnson t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net -- 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/
Re: [WISPA] Iowa Telecom a.k.a Windstream
Jayson, redo the link and send it again; I want to see it. At 09:22 AM 12/1/2009, you wrote: If this is their install truck, I don't think you have to worry about much. [image: ?ui=2view=attth=1254ad61273873f9attid=0.1disp=attdrealattid=ii_1254ad61273873f9zw] LOL On Tue, Dec 1, 2009 at 8:04 AM, Mike m...@aweiowa.com wrote: My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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/ Content-Type: image/jpeg; name=index_r6_c5.jpg Content-ID: ii_1254ad61273873f9 X-Attachment-Id: ii_1254ad61273873f9 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] FreeBSD hackers.... Needed for WISP related product...
Which isn't "true" TDMA as the term has conventionally been used. ;) Travis Microserv Randy Cosby wrote: I think what we're talking about is the TDMA package for Freebsd (which is probably exactly what is being used by UBNT). http://people.freebsd.org/~sam/TDMAPresentation-20090921.pdf Randy Travis Johnson wrote: I think everything you have described can be done now with Mikrotik routing, firewall, routing daemons, scripting, etc. also being able to use $50 boards up to $1,000 X86 based systems moving gigabits of traffic. All with standard parts. So what would this FreeBSD system bring to the table that can't be done already? Travis Microserv MDK wrote: Actually, it's far better than cost-effective. It's flexible, in both hardware and capabilities.Firewall, routing, routing daemons, and other things. Frankly, I find the physical aspects of the Airmax stuff frustratingly limited. I've grown fond of my immense ability to do creative stuff with Star-OS and a wide array of physical forms - especially since much of my network relies on low power consumption. AirMax, deployed as an AP and clients... seems ok.But that's only a small part of a good network. -- From: "Jayson Baker" jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:51 PM To: "WISPA General List" wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Availability is supposedly resolved. We'll see. Routing... there is a full SDK. You can do anything you want on those things. The new ones have 400+MHz proc's, plenty to do some routing/firewalling. I just can't see a home grown solution like you're proposing being cost-effective. We spent about 2 months on a project just like this, and started to have some pretty awesome performance and results. Then UBNT stuff came out. On Mon, Nov 30, 2009 at 9:39 PM, MDK rea...@muddyfrogwater.us wrote: Given UBNT's record of unavailability of product, and the inability to route via the interface, I vastly prefer this to UBNT's products. Now, mind you, I'm not really putting them down, but this is an excellent infrastructure tool...Routing and other capabilities that vastly exceed some better known... -- From: "Jayson Baker" jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:25 PM To: "WISPA General List" wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: "Travis Johnson" t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: "WISPA General List" wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net --
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
This is why we have 3 different providers, with different paths out of our NOC and on different fiber pairs leaving town. Qwest had an outage here about 9 months ago that took two of my competitors completely down for 5 hours... yet we were completely unaffected. :) Travis Microserv Matt Larsen - Lists wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] Iowa Telecom a.k.a Windstream
Windstream. AKA Alltell Wireline. Formed when Alltell spun off their wireline operations from their wireless (cellular). These guys ain't stupid. They know that they cannot offer plain old telephone service anymore, and are very aggressive. Over 1 million high speed internet customers. 3.2 billion annual revenue 3 million access lines Ranked 4th in the top 500 companies according to Business week in 2009. And Brent Whittington is damned smart. He is their CEO. Jeff Gardner their president is no slouch, but Brent pulls it all together. Don't take your organs to heaven, heaven knows we need them down here! Be an organ donor, sign your donor card today. - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 9:04 AM Subject: [WISPA] Iowa Telecom a.k.a Windstream My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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] Iowa Telecom a.k.a Windstream
I don't have dealings with them, but from a financial point of view, I've heard good things about them which probably means they do have 1/2 clue on how to run operations unlike Fairpoint who we compete with. On Tue, 2009-12-01 at 10:11 -0600, Blake Bowers wrote: Windstream. AKA Alltell Wireline. Formed when Alltell spun off their wireline operations from their wireless (cellular). These guys ain't stupid. They know that they cannot offer plain old telephone service anymore, and are very aggressive. Over 1 million high speed internet customers. 3.2 billion annual revenue 3 million access lines Ranked 4th in the top 500 companies according to Business week in 2009. And Brent Whittington is damned smart. He is their CEO. Jeff Gardner their president is no slouch, but Brent pulls it all together. Don't take your organs to heaven, heaven knows we need them down here! Be an organ donor, sign your donor card today. - Original Message - From: Mike m...@aweiowa.com To: WISPA General List wireless@wispa.org Sent: Tuesday, December 01, 2009 9:04 AM Subject: [WISPA] Iowa Telecom a.k.a Windstream My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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] A Ridiculous Failure of Critical Infrastructure
This is where it would be nice if WISPs were friendly enough with each other in their area to interconnect their networks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Matt Larsen - Lists li...@manageisp.com Sent: Tuesday, December 01, 2009 1:54 AM To: Telecom Regulation the Internet cyberteleco...@listserv.aol.com; WISPA General List wireless@wispa.org; motorola-us...@wispa.org Subject: [WISPA] A Ridiculous Failure of Critical Infrastructure Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] FreeBSD hackers.... Needed for WISP related product...
True, but MT has had a lot of issues over the years with N-Streme. Alvarion (AFAIK, just works). - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Butch Evans but...@butchevans.com Sent: Tuesday, December 01, 2009 12:19 AM To: e...@wisp-router.com; WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... On Tue, 2009-12-01 at 04:25 +, e...@wisp-router.com wrote: Tell that to Alvarion. Or Mikrotik for that matter. Nstreme != 802.11 -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] A Ridiculous Failure of Critical Infrastructure
Outages mailing list had one member claim it was resolved at 2:30am. Is this not so? On 12/1/09, Travis Johnson t...@ida.net wrote: This is why we have 3 different providers, with different paths out of our NOC and on different fiber pairs leaving town. Qwest had an outage here about 9 months ago that took two of my competitors completely down for 5 hours... yet we were completely unaffected. :) Travis Microserv Matt Larsen - Lists wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein 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] A Ridiculous Failure of Critical Infrastructure
It was resolved about 1:30am MST. I watched the first pings start passing from my edge router and switched back over within about 10 seconds. Charter didn't call anyone until 5am, so that is the time we are using to figure our credits. I get a $40 credit on next months bill. Whoopideee d!! Matt Larsen vistabeam.com Josh Luthman wrote: Outages mailing list had one member claim it was resolved at 2:30am. Is this not so? On 12/1/09, Travis Johnson t...@ida.net wrote: This is why we have 3 different providers, with different paths out of our NOC and on different fiber pairs leaving town. Qwest had an outage here about 9 months ago that took two of my competitors completely down for 5 hours... yet we were completely unaffected. :) Travis Microserv Matt Larsen - Lists wrote: Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
My neighbor who is also on Charter was able to route through us, and did so during their last outage. He still has a couple of T1s through ATT that are paid through the end of December, so he ended up routing through those during this one. OSPF and properly setup costs/NAT rules is wonderful. Two months ago, power outages struck a line that cut the power to the three towers that provide redundant connections to the far eastern side of my network. The five towers on the other side re-routed out through my neighbor's network for a couple of hours until the connection was restored. I need to find someone to connect with in Casper, WY and Rawlins, WY and then I'll have full survivability out to the edges of my system. Matt Larsen vistabeam.com Mike Hammett wrote: This is where it would be nice if WISPs were friendly enough with each other in their area to interconnect their networks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Matt Larsen - Lists li...@manageisp.com Sent: Tuesday, December 01, 2009 1:54 AM To: Telecom Regulation the Internet cyberteleco...@listserv.aol.com; WISPA General List wireless@wispa.org; motorola-us...@wispa.org Subject: [WISPA] A Ridiculous Failure of Critical Infrastructure Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more.Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/
Re: [WISPA] 20 mile link
I am really, really having a hard time getting my head around using $90 radios for must work links. Maybe I'm being obstinate, I don't know. Just seems wrong somehow. Jerry -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 9:04 PM To: WISPA General List Subject: Re: [WISPA] 20 mile link (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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/ 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/
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
We do that regularly in the Hoosier State! :) -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mike Hammett Sent: Tuesday, December 01, 2009 11:33 AM To: WISPA General List Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure This is where it would be nice if WISPs were friendly enough with each other in their area to interconnect their networks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Matt Larsen - Lists li...@manageisp.com Sent: Tuesday, December 01, 2009 1:54 AM To: Telecom Regulation the Internet CYBERTELECOM- l...@listserv.aol.com; WISPA General List wireless@wispa.org; motorola-us...@wispa.org Subject: [WISPA] A Ridiculous Failure of Critical Infrastructure Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more. Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.88/2538 - Release Date: 12/01/09 07:59:00 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] A Ridiculous Failure of Critical Infrastructure
Well... it's always easier to cooperate if you know who's 'er? Rick Harnish wrote: We do that regularly in the Hoosier State! :) -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mike Hammett Sent: Tuesday, December 01, 2009 11:33 AM To: WISPA General List Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure This is where it would be nice if WISPs were friendly enough with each other in their area to interconnect their networks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... 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] 20 mile link
Price != Quality Windows 7 costs $400 while Linux distros are free Ubnt stuff is ~$100 while Engenius is ~$125 PSTN PBX can be $10k while Asterisk/FreePBX is free (plus $1000 hardware) Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 12:56 PM, Jerry Richardson jrichard...@aircloud.comwrote: I am really, really having a hard time getting my head around using $90 radios for must work links. Maybe I'm being obstinate, I don't know. Just seems wrong somehow. Jerry -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 9:04 PM To: WISPA General List Subject: Re: [WISPA] 20 mile link (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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:
Re: [WISPA] A Ridiculous Failure of Critical Infrastructure
I have a backup with another WISP as well, but I don't quite have enough to offer much in return. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Rick Harnish rharn...@wispa.org Sent: Tuesday, December 01, 2009 12:01 PM To: 'WISPA General List' wireless@wispa.org Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure We do that regularly in the Hoosier State! :) -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mike Hammett Sent: Tuesday, December 01, 2009 11:33 AM To: WISPA General List Subject: Re: [WISPA] A Ridiculous Failure of Critical Infrastructure This is where it would be nice if WISPs were friendly enough with each other in their area to interconnect their networks. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Matt Larsen - Lists li...@manageisp.com Sent: Tuesday, December 01, 2009 1:54 AM To: Telecom Regulation the Internet CYBERTELECOM- l...@listserv.aol.com; WISPA General List wireless@wispa.org; motorola-us...@wispa.org Subject: [WISPA] A Ridiculous Failure of Critical Infrastructure Some kind of combination of failure between Charter and Qwest has left tens of thousands of people in Nebraska without Internet and has disrupted the Internet and phone services for thousands more. Right now, the outage is going on 12 hours and there is no ETA for repair in sight. The word coming down is that the outage is on a Qwest fiber, but it looks to me like both parties should be on the hot seat for not having the ability to route around the problem.There was a four hour outage on Charter a week ago that was caused by a fiber cut in Gothenburg, Nebraska. That one killed everything west of the cut, but it was small potatoes compared to this one. Is this truly the level of performance that we can expect from our major Internet backbone providers? It took me about 10 seconds to re-route my traffic to a backup provider - you would think that a couple of multimillion dollar companies would be able to sort out a problem of this nature in a reasonable amount of time. The small CLEC that I use for my backup connection had enough capacity to route around the problem and was even able to lend me a little bit after 5pm when the traffic on their network (mostly businesses) dropped off. It isn't rocket science to figure out how to route around an outage. Almost as frustrating is that there was NO news about the outages anywhere except on the social networking sites (Facebook, Twitter). One TV station in Hastings, NE put up a short story on their website, but I got more news from the tweets and FB posts that people where posting from their cell phones than I did from anywhere else. None of the network outage sites have any news about this. Could this be a harbinger of things to come? I am feeling pretty thankful right now that I have a choice in backbone providers and that I kept a second one. Diversity is a good thing, and this is a great example of why we need competition and multiple options for Internet. Matt Larsen vistabeam.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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.88/2538 - Release Date: 12/01/09 07:59:00 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
Re: [WISPA] FreeBSD hackers.... Needed for WISP related product...
On Tue, 2009-12-01 at 10:27 -0600, Mike Hammett wrote: True, but MT has had a lot of issues over the years with N-Streme. Alvarion (AFAIK, just works). I'm not aware of anyone wanting to go back in time. What used to be true isn't now, and I prefer living in the here and now. BTW, nstreme is the correct spelling. ;-) Either way, I was specifically addressing the question of what is (and isn't) 802.11 running on Atheros. -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] FreeBSD hackers.... Needed for WISP related product...
I dunno about that, Butch. I had a lot more fun in my late teens\early 20s... before I came down with the WISP illness. Sometimes I wish I could go back in time. :-p - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Butch Evans but...@butchevans.com Sent: Tuesday, December 01, 2009 12:43 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... On Tue, 2009-12-01 at 10:27 -0600, Mike Hammett wrote: True, but MT has had a lot of issues over the years with N-Streme. Alvarion (AFAIK, just works). I'm not aware of anyone wanting to go back in time. What used to be true isn't now, and I prefer living in the here and now. BTW, nstreme is the correct spelling. ;-) Either way, I was specifically addressing the question of what is (and isn't) 802.11 running on Atheros. -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] FreeBSD hackers.... Needed for WISP related product...
On Tue, 2009-12-01 at 12:52 -0600, Mike Hammett wrote: I dunno about that, Butch. I had a lot more fun in my late teens\early 20s... before I came down with the WISP illness. Sometimes I wish I could go back in time. :-p Yeah...there's no cure for that disease, either. SIGH. You'd think I'd have formed an immunity by now. :-) -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] FreeBSD hackers.... Needed for WISP related product...
Oh heck no! I'd NEVER live through it the second time! At 12:52 PM 12/1/2009, you wrote: I dunno about that, Butch. I had a lot more fun in my late teens\early 20s... before I came down with the WISP illness. Sometimes I wish I could go back in time. :-p - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Butch Evans but...@butchevans.com Sent: Tuesday, December 01, 2009 12:43 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... On Tue, 2009-12-01 at 10:27 -0600, Mike Hammett wrote: True, but MT has had a lot of issues over the years with N-Streme. Alvarion (AFAIK, just works). I'm not aware of anyone wanting to go back in time. What used to be true isn't now, and I prefer living in the here and now. BTW, nstreme is the correct spelling. ;-) Either way, I was specifically addressing the question of what is (and isn't) 802.11 running on Atheros. -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] FreeBSD hackers.... Needed for WISP related product...
Perhaps he's now just a carrier... ;-) Regards, Jeff Jeff Broadwick ImageStream 800-813-5123 x106 (US/Can) +1 574-935-8484 x106 (Int'l) -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Butch Evans Sent: Tuesday, December 01, 2009 2:59 PM To: WISPA General List Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... On Tue, 2009-12-01 at 12:52 -0600, Mike Hammett wrote: I dunno about that, Butch. I had a lot more fun in my late teens\early 20s... before I came down with the WISP illness. Sometimes I wish I could go back in time. :-p Yeah...there's no cure for that disease, either. SIGH. You'd think I'd have formed an immunity by now. :-) -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] suggestions for dual wan dhcp auto fail over
I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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] suggestions for dual wan dhcp auto fail over
Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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] suggestions for dual wan dhcp auto fail over
Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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] suggestions for dual wan dhcp auto fail over
This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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] suggestions for dual wan dhcp auto fail over
Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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] suggestions for dual wan dhcp auto fail over
First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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] FreeBSD hackers.... Needed for WISP related product...
So does page 16 imply that a GPS system could be used? It sounds like these new Atheros chipsets have TDMA hardware on them. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Randy Cosby dco...@infowest.com Sent: Tuesday, December 01, 2009 12:19 AM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... I think what we're talking about is the TDMA package for Freebsd (which is probably exactly what is being used by UBNT). http://people.freebsd.org/~sam/TDMAPresentation-20090921.pdf Randy Travis Johnson wrote: I think everything you have described can be done now with Mikrotik routing, firewall, routing daemons, scripting, etc. also being able to use $50 boards up to $1,000 X86 based systems moving gigabits of traffic. All with standard parts. So what would this FreeBSD system bring to the table that can't be done already? Travis Microserv MDK wrote: Actually, it's far better than cost-effective. It's flexible, in both hardware and capabilities.Firewall, routing, routing daemons, and other things. Frankly, I find the physical aspects of the Airmax stuff frustratingly limited. I've grown fond of my immense ability to do creative stuff with Star-OS and a wide array of physical forms - especially since much of my network relies on low power consumption. AirMax, deployed as an AP and clients... seems ok.But that's only a small part of a good network. -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:51 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Availability is supposedly resolved. We'll see. Routing... there is a full SDK. You can do anything you want on those things. The new ones have 400+MHz proc's, plenty to do some routing/firewalling. I just can't see a home grown solution like you're proposing being cost-effective. We spent about 2 months on a project just like this, and started to have some pretty awesome performance and results. Then UBNT stuff came out. On Mon, Nov 30, 2009 at 9:39 PM, MDK rea...@muddyfrogwater.us wrote: Given UBNT's record of unavailability of product, and the inability to route via the interface, I vastly prefer this to UBNT's products. Now, mind you, I'm not really putting them down, but this is an excellent infrastructure tool...Routing and other capabilities that vastly exceed some better known... -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:25 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: Travis Johnson t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net -- 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] suggestions for dual wan dhcp auto fail over
Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean.
Re: [WISPA] suggestions for dual wan dhcp auto fail over
Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile 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/ -- This message has been scanned for viruses and dangerous content by the Data Technology MailScanner, and is believed to be clean. WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe:
Re: [WISPA] FreeBSD hackers.... Needed for WISP related product...
I think it's a fairly big project, although a lot of the fine work has been done. I started drooling when reading the paper a few weeks ago. It would be a kicker to have an open-source multi-platform TDMA implementation. UBNT has encouraged open source firmware on their platforms for a long time, and a RouterBoard implementation would be sweet. Getting synch on backhaul links would be killer for example. Unfortunately I wouldn't recognize FreeBSD if I tripped over it, so can't be much help there. George -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mike Hammett Sent: Tuesday, December 01, 2009 4:51 PM To: WISPA General List Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... So does page 16 imply that a GPS system could be used? It sounds like these new Atheros chipsets have TDMA hardware on them. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Randy Cosby dco...@infowest.com Sent: Tuesday, December 01, 2009 12:19 AM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... I think what we're talking about is the TDMA package for Freebsd (which is probably exactly what is being used by UBNT). http://people.freebsd.org/~sam/TDMAPresentation-20090921.pdf Randywireless/ 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] FreeBSD hackers.... Needed for WISP related product...
I don't think so. Page 17 contrasts the FreeBSD implementation with most implementations on page 16. Mike Hammett wrote: So does page 16 imply that a GPS system could be used? It sounds like these new Atheros chipsets have TDMA hardware on them. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Randy Cosby dco...@infowest.com Sent: Tuesday, December 01, 2009 12:19 AM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... I think what we're talking about is the TDMA package for Freebsd (which is probably exactly what is being used by UBNT). http://people.freebsd.org/~sam/TDMAPresentation-20090921.pdf Randy Travis Johnson wrote: I think everything you have described can be done now with Mikrotik routing, firewall, routing daemons, scripting, etc. also being able to use $50 boards up to $1,000 X86 based systems moving gigabits of traffic. All with standard parts. So what would this FreeBSD system bring to the table that can't be done already? Travis Microserv MDK wrote: Actually, it's far better than cost-effective. It's flexible, in both hardware and capabilities.Firewall, routing, routing daemons, and other things. Frankly, I find the physical aspects of the Airmax stuff frustratingly limited. I've grown fond of my immense ability to do creative stuff with Star-OS and a wide array of physical forms - especially since much of my network relies on low power consumption. AirMax, deployed as an AP and clients... seems ok.But that's only a small part of a good network. -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:51 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Availability is supposedly resolved. We'll see. Routing... there is a full SDK. You can do anything you want on those things. The new ones have 400+MHz proc's, plenty to do some routing/firewalling. I just can't see a home grown solution like you're proposing being cost-effective. We spent about 2 months on a project just like this, and started to have some pretty awesome performance and results. Then UBNT stuff came out. On Mon, Nov 30, 2009 at 9:39 PM, MDK rea...@muddyfrogwater.us wrote: Given UBNT's record of unavailability of product, and the inability to route via the interface, I vastly prefer this to UBNT's products. Now, mind you, I'm not really putting them down, but this is an excellent infrastructure tool...Routing and other capabilities that vastly exceed some better known... -- From: Jayson Baker jay...@spectrasurf.com Sent: Monday, November 30, 2009 8:25 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... Is there really much need for this, given the new AirMax product line? I'm just saying... On Mon, Nov 30, 2009 at 9:19 PM, MDK rea...@muddyfrogwater.us wrote: What would you call a totally proprietary, TDMA based protocol, without ACK or CSMA? Doesn't look a whole lot like 802.11x, but if you wish to say it is, then, for you it is :) -- From: Travis Johnson t...@ida.net Sent: Monday, November 30, 2009 7:36 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] FreeBSD hackers Needed for WISP related product... If you are using Atheros based hardware, it's still 802.11... regardless of what software you put on top of it. Travis Microserv MDK wrote: If you're a WISP and have interest in using commodity - off the shelf - Atheros based hardware to achieve higher than ethernet speeds over wireless... This is not a tweak of 802.11, it is a completely different mode... There is currently an opportunity to do so, where most of the work has been done by various others in the FreeBSd community, but it is not integrated or packaged as a useful WISP product, and that's what needs to be done. This does not need to result in an open source release, due to the relaxed BSD license. Or, it can. But I'm looking for some people who have experience with freebsd, and have an interest in integrating what could be an awesome performing product using inexpensive commodity hardware. email me at pda at neofast dot net or mark at neofast dot net --
Re: [WISPA] suggestions for dual wan dhcp auto fail over
There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from
Re: [WISPA] suggestions for dual wan dhcp auto fail over
Well I have always used the command line for most things I learned to configure hp-ux systems back in the 80's when the command line was the only way. I still configure my linux servers via the command line and laugh at anyone that wants to us a GUI. But MT has made configuring via the GUI so easy that is hard for me to use the command line except when I am testing scripts. Guess maybe I am a wimp? Josh Luthman wrote: Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List:
Re: [WISPA] suggestions for dual wan dhcp auto fail over
No one that works on HPUX is a wimp... Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:29 PM, Data Technology w...@dtisp.com wrote: Well I have always used the command line for most things I learned to configure hp-ux systems back in the 80's when the command line was the only way. I still configure my linux servers via the command line and laugh at anyone that wants to us a GUI. But MT has made configuring via the GUI so easy that is hard for me to use the command line except when I am testing scripts. Guess maybe I am a wimp? Josh Luthman wrote: Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could just change the distance on the route but I found out it will not let you change the distance if the default route is set by the dhcp-client. I have looked at some of the examples on the wiki but they all use static ip address and I am wanting to use dhcp. Anyone have any pointers? Thanks LaRoy McCann Data Technology 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/ Sent via BlackBerry from T-Mobile
Re: [WISPA] suggestions for dual wan dhcp auto fail over
Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I will need to use netwatch to check the servcie availability so I can check all the way thru the providers service and not just the local physical connection. The question is what do I need to do when the primary goes down? I thought I could
Re: [WISPA] suggestions for dual wan dhcp auto fail over
I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) That is how static routing works - it picks the lowest distance. If you have two routes identical except the distance, then the lower distance is used. Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) I have always had one interface a static IP/route so this was easy. Not sure how to force a certain destination when it is using dhcp-client. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:45 PM, Data Technology w...@dtisp.com wrote: Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to.
Re: [WISPA] suggestions for dual wan dhcp auto fail over
just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA General List ReplyTo: WISPA General List Subject: [WISPA] suggestions for dual wan dhcp auto fail over Sent: Dec 1, 2009 15:30 I am trying to configure an rb450 v4.3 to connect to 2 different providers with dhcp using 1 as the primary and the other as a backup. I would like it to switch over to the backup if the primary service is down. I want to nat local users to either service. I assume I
[WISPA] Tranzeo TR-902 Firmware
Has anyone had problems with the new Firmware TR6-5.0.2Rt? If so what and what is the fix? 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] suggestions for dual wan dhcp auto fail over
That's a good idea - find an IP only responsive on that network. I think DNS servers will respond to pings (but not DNS queries) off network. Test it with dig/ping. I can tell you if it works from my network if you share the IP. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson jrichard...@aircloud.comwrote: just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote: Sounds too easy :) I'll give it a try. Thanks LaRoy e...@wisp-router.com wrote: Just change the nat to use the other public ip since your already masquerading just change that rule to src-nat and set the public ip to src-nat to. /Eje --Original Message-- From: Data Technology Sender: wireless-boun...@wispa.org To: WISPA
Re: [WISPA] suggestions for dual wan dhcp auto fail over
Josh Luthman wrote: I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) That is how static routing works - it picks the lowest distance. If you have two routes identical except the distance, then the lower distance is used. Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) I have always had one interface a static IP/route so this was easy. Not sure how to force a certain destination when it is using dhcp-client. I know the netwatch will not work for this but I saw a script (inproved netwatch) that will use the ping command to check an ip address. Ping has an option (that was broke until 3.28) to use source-address. I figure if it is using a source address of the dsl interface that went down it should try to ping out that interface instead of the one with the lowest distance. This is my thinking of how this might work. Hopefully it will work this way. I will know soon. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:45 PM, Data Technology w...@dtisp.com wrote: Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me.
Re: [WISPA] suggestions for dual wan dhcp auto fail over
If you can specify source address for ping then do a policy route. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 6:02 PM, Data Technology w...@dtisp.com wrote: Josh Luthman wrote: I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) That is how static routing works - it picks the lowest distance. If you have two routes identical except the distance, then the lower distance is used. Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) I have always had one interface a static IP/route so this was easy. Not sure how to force a certain destination when it is using dhcp-client. I know the netwatch will not work for this but I saw a script (inproved netwatch) that will use the ping command to check an ip address. Ping has an option (that was broke until 3.28) to use source-address. I figure if it is using a source address of the dsl interface that went down it should try to ping out that interface instead of the one with the lowest distance. This is my thinking of how this might work. Hopefully it will work this way. I will know soon. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:45 PM, Data Technology w...@dtisp.com wrote: Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That
Re: [WISPA] suggestions for dual wan dhcp auto fail over
It's also likely the gateway doesn't change, just the IP address. Ping the gateway on WAN1 and if it stops responding activate WAN2 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 3:01 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over That's a good idea - find an IP only responsive on that network. I think DNS servers will respond to pings (but not DNS queries) off network. Test it with dig/ping. I can tell you if it works from my network if you share the IP. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson jrichard...@aircloud.comwrote: just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:01 PM, Data Technology w...@dtisp.com wrote:
Re: [WISPA] Tranzeo TR-902 Firmware
Can you be more specific? ryan On Dec 1, 2009, at 3:00 PM, NGL n...@ngl.net wrote: Has anyone had problems with the new Firmware TR6-5.0.2Rt? If so what and what is the fix? --- --- --- --- 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] 20 mile link
I would not concern yourself with this option because you can't buy one if you wanted to right now. Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jerry Richardson jrichard...@aircloud.com Sent: Tuesday, December 01, 2009 12:57 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] 20 mile link I am really, really having a hard time getting my head around using $90 radios for must work links. Maybe I'm being obstinate, I don't know. Just seems wrong somehow. Jerry -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 9:04 PM To: WISPA General List Subject: Re: [WISPA] 20 mile link (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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/ WISPA Wants You! Join today! http://signup.wispa.org/
Re: [WISPA] suggestions for dual wan dhcp auto fail over
This won't work because if the dsl provider is down somewhere within their network the dsl modem will still answer ping requests on the local interface. Jerry Richardson wrote: It's also likely the gateway doesn't change, just the IP address. Ping the gateway on WAN1 and if it stops responding activate WAN2 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 3:01 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over That's a good idea - find an IP only responsive on that network. I think DNS servers will respond to pings (but not DNS queries) off network. Test it with dig/ping. I can tell you if it works from my network if you share the IP. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson jrichard...@aircloud.comwrote: just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks LaRoy Josh Luthman wrote: This might help you http://stfunoo.be/?p=268 I like using route distance since 3.11 DHCP can do it. It has worked very well for me. Josh Luthman Office: 937-552-2340 Direct:
Re: [WISPA] 20 mile link
I've got an extra set, I don't need right now, never deployed will sell for my cost. Regards Michael Baird I would not concern yourself with this option because you can't buy one if you wanted to right now. Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jerry Richardson jrichard...@aircloud.com Sent: Tuesday, December 01, 2009 12:57 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] 20 mile link I am really, really having a hard time getting my head around using $90 radios for must work links. Maybe I'm being obstinate, I don't know. Just seems wrong somehow. Jerry -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 9:04 PM To: WISPA General List Subject: Re: [WISPA] 20 mile link (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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:
Re: [WISPA] Tranzeo TR-902 Firmware
I upgraded 50 TR-902 client and 2 AP's now they are erratic, and have to be reboot from the client side. Also I am having problem accessing some clients via the web. The AP have to be rebooted at their location. NGL -- From: D. Ryan Spott rsp...@cspott.com Sent: Tuesday, December 01, 2009 3:13 PM To: WISPA General List wireless@wispa.org Cc: wireless@wispa.org Subject: Re: [WISPA] Tranzeo TR-902 Firmware Can you be more specific? ryan On Dec 1, 2009, at 3:00 PM, NGL n...@ngl.net wrote: Has anyone had problems with the new Firmware TR6-5.0.2Rt? If so what and what is the fix? --- --- --- --- 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] 5.6 GHZ?
Anyone know of a way to find out what freq a weather radar is operating on? I know of several local ones and would like to know what freq they operate on for safety sake. Any ideas? I've looked everywhere and found nothing? Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jack Unger jun...@ask-wi.com Sent: Saturday, November 21, 2009 1:16 PM To: WISPA General List wireless@wispa.org, memb...@wispa.org memb...@wispa.org Subject: Re: [WISPA] 5.6 GHZ? IMO, it is iffy for the reason you mentioned. The FCC (at the request of the FAA and the NTIA) appears ready to deny use of the 5.6 spectrum in areas where interference with airport weather radar takes place. I doubt that any WISP would ague that their use of that spectrum is more important than safe operation of commercial aircraft. I expect that newly certified 5 GHz equipment will soon (within the next year) include a updated DFS algorithm that looks for the presence of 5.6 GHz radar and switches away from 5.6 when radar is detected. Your existing equipment may remain technically legal but you do run the risk of possibly being blamed for aircraft crashes assuming you are unlucky enough to be using 5.6 near airports where you could cause actual interference to Terminal Doppler Weather Radar systems. See http://tiny.cc/LIlqB for more information. jack Travis Johnson wrote: It's iffy because the FCC allowed the specific band, and now they are trying to take it back away... two years later. If I never upgrade my radios, does that mean I'm legal to run in that specific band forever? I just don't understand how they can allow it for 2 years, and then try and take it away and think they are going to clean up the airways. Travis Microserv 3-dB Networks wrote: Motorola Canopy 5.4GHz radios updated with the latest firmware cannot transmit in the 5600-5650 part of the band. I don't understand what is iffy about the band... Canopy operators have been using it for two years or so now legally, and while DFS still has issues in its current implementation, the FCC is working to make the DFS detection better on the radio side and in turn make it harder to radio manufacturers to allow clients to avoid using DFS Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jack Unger Sent: Friday, November 20, 2009 11:02 PM To: WISPA General List Subject: Re: [WISPA] 5.6 GHZ? 5470 - 5725 is a legitimate band but DFS2 must be used on the radios. There is currently FCC activity to modify the DFS profiles for all newly-certified radios to avoid aircraft radar system in the 5.6 GHz part of the 5470-5725 band. The bottom line is - it's pretty iffy.jack Forbes Mercy wrote: My new MIMO radios have 5.6 GHZ on them, I don't recall that frequency being available in the US. Is it? Forbes 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... 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] suggestions for dual wan dhcp auto fail over
It will work, but there is other work to be done. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 5:03 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Josh Luthman wrote: I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) That is how static routing works - it picks the lowest distance. If you have two routes identical except the distance, then the lower distance is used. Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) I have always had one interface a static IP/route so this was easy. Not sure how to force a certain destination when it is using dhcp-client. I know the netwatch will not work for this but I saw a script (inproved netwatch) that will use the ping command to check an ip address. Ping has an option (that was broke until 3.28) to use source-address. I figure if it is using a source address of the dsl interface that went down it should try to ping out that interface instead of the one with the lowest distance. This is my thinking of how this might work. Hopefully it will work this way. I will know soon. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:45 PM, Data Technology w...@dtisp.com wrote: Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman
Re: [WISPA] suggestions for dual wan dhcp auto fail over
Unless it's a Modem/router it's not the gateway - it's just converting DSL to Ethernet. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 3:17 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over This won't work because if the dsl provider is down somewhere within their network the dsl modem will still answer ping requests on the local interface. Jerry Richardson wrote: It's also likely the gateway doesn't change, just the IP address. Ping the gateway on WAN1 and if it stops responding activate WAN2 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 3:01 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over That's a good idea - find an IP only responsive on that network. I think DNS servers will respond to pings (but not DNS queries) off network. Test it with dig/ping. I can tell you if it works from my network if you share the IP. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson jrichard...@aircloud.comwrote: just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data Technology w...@dtisp.com wrote: Josh, That is what I was trying to do but I was trying to use /ip route set ether1 distance=3 instead of /ip dhcp-client set ether1 default-route-distance=3. Thanks
Re: [WISPA] suggestions for dual wan dhcp auto fail over
can't do that if the gateway is on the DSL modem 3 foot from the MT. Does you no good. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jerry Richardson Sent: Tuesday, December 01, 2009 5:06 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over It's also likely the gateway doesn't change, just the IP address. Ping the gateway on WAN1 and if it stops responding activate WAN2 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 3:01 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over That's a good idea - find an IP only responsive on that network. I think DNS servers will respond to pings (but not DNS queries) off network. Test it with dig/ping. I can tell you if it works from my network if you share the IP. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson jrichard...@aircloud.comwrote: just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do keep in mind you need 3.11+. If you're new to Mikrotik there is little reason to be concerned, but some users such as myself still have 2.9.50 or 51 stuff! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 4:29 PM, Data
Re: [WISPA] suggestions for dual wan dhcp auto fail over
lol. I beat ya to it! hahaha --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jerry Richardson Sent: Tuesday, December 01, 2009 5:22 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Unless it's a Modem/router it's not the gateway - it's just converting DSL to Ethernet. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 3:17 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over This won't work because if the dsl provider is down somewhere within their network the dsl modem will still answer ping requests on the local interface. Jerry Richardson wrote: It's also likely the gateway doesn't change, just the IP address. Ping the gateway on WAN1 and if it stops responding activate WAN2 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 3:01 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over That's a good idea - find an IP only responsive on that network. I think DNS servers will respond to pings (but not DNS queries) off network. Test it with dig/ping. I can tell you if it works from my network if you share the IP. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson jrichard...@aircloud.comwrote: just ping the DSL provider's DNS server. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 2:46 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version 4.3 so that should not be a problem. I've been using MT for several years but I have gotten past the 2.9.x. I think oldest is 3.25. Josh Luthman wrote: First one is definitely not going to work. Second one is what you need =) Do
Re: [WISPA] suggestions for dual wan dhcp auto fail over
Ok, Thanks. I have enough to get started. Will cross the next problem when I get to it. Well I guess I am going home. I'll play around a little with this tonight. Dennis Burgess wrote: It will work, but there is other work to be done. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Data Technology Sent: Tuesday, December 01, 2009 5:03 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Josh Luthman wrote: I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) That is how static routing works - it picks the lowest distance. If you have two routes identical except the distance, then the lower distance is used. Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) I have always had one interface a static IP/route so this was easy. Not sure how to force a certain destination when it is using dhcp-client. I know the netwatch will not work for this but I saw a script (inproved netwatch) that will use the ping command to check an ip address. Ping has an option (that was broke until 3.28) to use source-address. I figure if it is using a source address of the dsl interface that went down it should try to ping out that interface instead of the one with the lowest distance. This is my thinking of how this might work. Hopefully it will work this way. I will know soon. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:45 PM, Data Technology w...@dtisp.com wrote: Yes the dsl modem is handing out a dhcp address. I figure I will have to ping way back upstream to check the connection vs just pinging the dhcp modem. I was thinking that if I just change the distance value to a higher value then I could leave the interface up and nat should use the route with the lowest distance value. (not tested yet) Then I could ping with a source address of the dsl interface and it should go out the dsl line even though the distance is set higher than the backup. (not tested yet) Dennis Burgess wrote: There are other things to also keep in mind when dealing with DHCP, i.e. is your DHCP being handed out locally. sSo if you have a DSL line is the DSL modem handing this out? if so, then watching that connection is useless, you will have to do some policy based routing and checks to verify that it is up and bring it down if it is not up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org Link Technologies, Inc -- Mikrotik WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training Author of Learn RouterOS -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 4:21 PM To: WISPA General List Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over Lucky you, glad you could have 3.x everywhere! I could be wrong as it may just be my experience, but the command line for custom things is necessary as the GUI doesn't show everything. I started with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's simply a personal preference! There are places like wireless where the GUI is almost required as the CLI is difficult to navigate and may not even have some values. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Dec 1, 2009 at 5:17 PM, Data Technology w...@dtisp.com wrote: Yeah, when I looked at the article you listed it clicked. I don't use the command line except when I have to so I was a little off on the command to change the distance setting. I have version
Re: [WISPA] suggestions for dual wan dhcp auto fail over
On Tue, 2009-12-01 at 17:16 -0600, Data Technology wrote: This won't work because if the dsl provider is down somewhere within their network the dsl modem will still answer ping requests on the local interface. I have not read all of this thread. Here is the approach I use and it works well, with only 1 problem: 1. Create a static route to something (I use 4.2.2.2) via DSL1 2. Create a static route to something else (4.2.2.3) via DSL2 What you have now, are 2 IP addresses (4.2.2.2 and 4.2.2.3) that will ignore any default route you may or may not have installed. 3. Create a netwatch that will test to host 4.2.2.2 (for example). 3a. down script will change default gateway for DSL1 to point to DSL2, fix policy routes, enable dhcp client options or whatever. 3b. up script will undo all the changes made by 3a 4. You can do a netwatch for 4.2.2.3 as well, though it is only necessary if you are using DSL2 as a load sharing interface/route. This is all easier done than said and easier said than typed. :-) -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://www.wispa.org/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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] Tranzeo TR-902 Firmware
Noise? Any stats? I have 30 or so updated and no issues so far. ryan On Tue, Dec 1, 2009 at 3:20 PM, NGL n...@ngl.net wrote: I upgraded 50 TR-902 client and 2 AP's now they are erratic, and have to be reboot from the client side. Also I am having problem accessing some clients via the web. The AP have to be rebooted at their location. NGL -- From: D. Ryan Spott rsp...@cspott.com Sent: Tuesday, December 01, 2009 3:13 PM To: WISPA General List wireless@wispa.org Cc: wireless@wispa.org Subject: Re: [WISPA] Tranzeo TR-902 Firmware Can you be more specific? ryan On Dec 1, 2009, at 3:00 PM, NGL n...@ngl.net wrote: Has anyone had problems with the new Firmware TR6-5.0.2Rt? If so what and what is the fix? --- --- --- --- 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] Tranzeo TR-902 Firmware
Here are a few 17 001970057AF7 36/36 -68/-68 -90 0 21 8 4592 18. 0060B33BC71E 48/48 -64/-67 -93 0 4 15 9479 19. 0060B3453746 48/48 -65/-67 -93 0 1 26 454 20. 0060B38F0706 48/48 -66/-67 -91 0 21 2 83727602 21. 0060B33F7AE6 48/48 -60/-59 -92 0 4 3 3597 22. 0060B33F80DD 48/48 -57/-58 -94 0 6 2 2312 23. 0060B3393C3B 48/48 -55/-56 -92 0 3 8 5443 24. 001970057AA6 48/48 -62/-66 -91 0 10 27 2319 25. 0019700D47F9 48/36 -62/-67 -93 0 3 9 6298 26. 0019700585A7 36/48 -68/-71 -93 0 189 17 3871 27. 001970057AFE 36/48 -70/-70 -92 0 239 8 4714 28. 001970057A5B 48/48 -61/-62 -91 0 1 0 4438 29. 0060B38F0672 48/48 -67/-67 -91 0 1 37 8438 30. 001970057A6A 48/48 -62/-64 -92 0 1 6 9003 31. 001970057A79 48/48 -61/-62 -91 0 1 0 5054 32. 0060B33C9E23 48/48 -56/-59 -93 0 5 6 -- From: Ryan Spott rsp...@cspott.com Sent: Tuesday, December 01, 2009 3:27 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] Tranzeo TR-902 Firmware Noise? Any stats? I have 30 or so updated and no issues so far. ryan On Tue, Dec 1, 2009 at 3:20 PM, NGL n...@ngl.net wrote: I upgraded 50 TR-902 client and 2 AP's now they are erratic, and have to be reboot from the client side. Also I am having problem accessing some clients via the web. The AP have to be rebooted at their location. NGL -- From: D. Ryan Spott rsp...@cspott.com Sent: Tuesday, December 01, 2009 3:13 PM To: WISPA General List wireless@wispa.org Cc: wireless@wispa.org Subject: Re: [WISPA] Tranzeo TR-902 Firmware Can you be more specific? ryan On Dec 1, 2009, at 3:00 PM, NGL n...@ngl.net wrote: Has anyone had problems with the new Firmware TR6-5.0.2Rt? If so what and what is the fix? --- --- --- --- 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/ 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] Times Microwave EZ connectors
LOL, and I have permanent black marks on my office carpet, my home, my truck, my clothes, my harness etc etc... When coax seal gets HOT it doesn't melt but it gets real soft and sticky and will not ever come off anything. Its been such a mess here in FL that I have actually stopped using it. I use this other stuff now that is thinner and cleaner I prefer, sorry forget what its called. If I must use coax seal I put this under it so I can actually remove the junk when I take it apart and end up with a clean cable when done. Scott Carullo Brevard Wireless 321-205-1100 x102 From: Travis Johnson t...@ida.net Sent: Tuesday, November 24, 2009 1:57 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] Times Microwave EZ connectors I second this. We have used this for 5+ years now and haven't had a single water issue since we started using it. And it's cheap, and easy to work with in the summer heat and the winter cold. Travis Josh Luthman wrote: Best. Stuff. Ever. http://www.amazon.com/gp/product/B0002ZPINC/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=48 6539851pf_rd_s=lpo-top-stripe-1pf_rd_t=201pf_rd_i=B00075J4J6pf_rd_m=ATVP DKIKX0DERpf_rd_r=0YKHJM87AJ2TBD52DRE2 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Nov 24, 2009 at 1:13 PM, Robert West robert.w...@just-micro.comwrote: Rubber tape rules on this end. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Marlon K. Schafer Sent: Tuesday, November 24, 2009 12:50 PM To: WISPA General List Subject: Re: [WISPA] Times Microwave EZ connectors Heat shrink doesn't work in the cold. It will get hard (the glue) and as things move in the wind etc. it'll allow water in. Been there done that. NOTHING works better than self vulcanizing rubber tape. If what you use is easy to get off it's not a good tight seal. sigh It sure can't be that hard to build a connector that seals without the tape! sigh marlon - Original Message - From: RickG rgunder...@gmail.com To: WISPA General List wireless@wispa.org Sent: Thursday, November 19, 2009 6:15 PM Subject: Re: [WISPA] Times Microwave EZ connectors Yes - hate the mess but seals the best! On Thu, Nov 19, 2009 at 6:43 PM, os10ru...@gmail.com wrote: Coax-seal On Nov 19, 2009, at 6:42 PM, AJ wrote: CANUSA adhesive shrink tubing is your friend :) On Thu, Nov 19, 2009 at 4:41 PM, lakel...@gbcx.net wrote: No 400 connector from any of the manufacturers is weatherproof by itself. You need to weatherproof all of your connections. If they are not getting wet you are lucky. Plain and simple. Bob Sent from my Verizon Wireless BlackBerry -Original Message- From: MDK rea...@muddyfrogwater.us Date: Thu, 19 Nov 2009 10:20:52 To: WISPA General Listwireless@wispa.org Subject: [WISPA] Times Microwave EZ connectors I've run out of these, and none of the vendors I use commonly carry them. Anyone out west have these? Yeah, I know, it costs more to buy two of these than a whole pre-built 10 foot cable, but every danged pre-built I buy has water issues. We have never had to seal any of the cables we built ourselves, and none of them have ever leaked (except when someone who'll forever remain nameless forgot to tighten the cable...), but I have no luck at all with the pre-made I've bought from multiple places. Our temporary site needed to go up in a real hurry, so I bought a whole pile of parts and cables, and most of them have had issues. 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!
Re: [WISPA] 20 mile link
Why can't you? We've got a bunch of them recently, and have more on the way from distro right now. On Tue, Dec 1, 2009 at 4:13 PM, Scott Carullo sc...@brevardwireless.comwrote: I would not concern yourself with this option because you can't buy one if you wanted to right now. Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jerry Richardson jrichard...@aircloud.com Sent: Tuesday, December 01, 2009 12:57 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] 20 mile link I am really, really having a hard time getting my head around using $90 radios for must work links. Maybe I'm being obstinate, I don't know. Just seems wrong somehow. Jerry -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jayson Baker Sent: Monday, November 30, 2009 9:04 PM To: WISPA General List Subject: Re: [WISPA] 20 mile link (2) Rocket5M @ $90/ea (2) RocketDish @ $145/ea $470 On Mon, Nov 30, 2009 at 10:00 PM, Travis Johnson t...@ida.net wrote: I would agree. Except the 411ah is overkill in my testing, the regular 411 shows as much throughput as the 411ah. So, here's the list: 2 x RB411 2 x PacWireless 2ft dishes with radomes 2 x PacWireless enclosures 2 x wireless cards (XR5 would be my choice) 2 x pigtails 2 x LMR jumpers 2 x 18v PoE Total cost would be less than $900 and would do 30Mbps in a 20mhz channel (or 15Mbps in a 10mhz channel). Travis Microserv Josh Luthman wrote: If spectrum is available you can use a 411ah pair and get 30 megs in 20mhz. Like 500 bucks in gear... On 11/30/09, RickG rgunder...@gmail.com rgunder...@gmail.com wrote: Daniel, great questions! Throughput: As fast as possible :) Seriously, a couple of megs minimum. 10Mbps would be plenty. Dishes: As big as necessary. Naturally, on the tower I'll be limited by wind loading. The other end is a solid water tank but I imagine the water company wont like a 10' dish :) Budget: $10k including tower. Licensed or unlicensed. I'm open to either but my budget probably wont allow licensed. POE or?: No preference. Noise floor: On 2.4GHz, -97. On 5GHz, -94. Currently deploying: Ubiquiti CPE on Mikrotik AP's. Was Tranzeo's on WRAP/StarOS. Comfort level: I've got experience with almost everything mainstream. Thanks! -RickG On Mon, Nov 30, 2009 at 10:42 PM, 3-dB Networks wi...@3-db.net wi...@3-db.net wrote: Depends... What type of throughput do you need? What size dishes can you use? What is the budget? Licensed or Unlicensed? PoE or some other configuration? What does the noise floor look like? What type of equipment do you already primarily use (i.e. what will you be the most comfortable deploying). My recommendation would be based on the answer to all of those questions. Daniel White 3-dB Networkshttp://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org wireless-boun...@wispa.org] On Behalf Of RickG Sent: Monday, November 30, 2009 8:23 PM To: WISPA General List Subject: [WISPA] 20 mile link Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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:
Re: [WISPA] 5.6 GHZ?
I found one in the ULS once. I haven't looked latey. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: Scott Carullo sc...@brevardwireless.com Sent: Tuesday, December 01, 2009 5:21 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] 5.6 GHZ? Anyone know of a way to find out what freq a weather radar is operating on? I know of several local ones and would like to know what freq they operate on for safety sake. Any ideas? I've looked everywhere and found nothing? Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jack Unger jun...@ask-wi.com Sent: Saturday, November 21, 2009 1:16 PM To: WISPA General List wireless@wispa.org, memb...@wispa.org memb...@wispa.org Subject: Re: [WISPA] 5.6 GHZ? IMO, it is iffy for the reason you mentioned. The FCC (at the request of the FAA and the NTIA) appears ready to deny use of the 5.6 spectrum in areas where interference with airport weather radar takes place. I doubt that any WISP would ague that their use of that spectrum is more important than safe operation of commercial aircraft. I expect that newly certified 5 GHz equipment will soon (within the next year) include a updated DFS algorithm that looks for the presence of 5.6 GHz radar and switches away from 5.6 when radar is detected. Your existing equipment may remain technically legal but you do run the risk of possibly being blamed for aircraft crashes assuming you are unlucky enough to be using 5.6 near airports where you could cause actual interference to Terminal Doppler Weather Radar systems. See http://tiny.cc/LIlqB for more information. jack Travis Johnson wrote: It's iffy because the FCC allowed the specific band, and now they are trying to take it back away... two years later. If I never upgrade my radios, does that mean I'm legal to run in that specific band forever? I just don't understand how they can allow it for 2 years, and then try and take it away and think they are going to clean up the airways. Travis Microserv 3-dB Networks wrote: Motorola Canopy 5.4GHz radios updated with the latest firmware cannot transmit in the 5600-5650 part of the band. I don't understand what is iffy about the band... Canopy operators have been using it for two years or so now legally, and while DFS still has issues in its current implementation, the FCC is working to make the DFS detection better on the radio side and in turn make it harder to radio manufacturers to allow clients to avoid using DFS Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jack Unger Sent: Friday, November 20, 2009 11:02 PM To: WISPA General List Subject: Re: [WISPA] 5.6 GHZ? 5470 - 5725 is a legitimate band but DFS2 must be used on the radios. There is currently FCC activity to modify the DFS profiles for all newly-certified radios to avoid aircraft radar system in the 5.6 GHz part of the 5470-5725 band. The bottom line is - it's pretty iffy.jack Forbes Mercy wrote: My new MIMO radios have 5.6 GHZ on them, I don't recall that frequency being available in the US. Is it? Forbes 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... 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/
Re: [WISPA] Times Microwave EZ connectors
Never made a mess except on threads like N female connectors. On 12/1/09, Scott Carullo sc...@brevardwireless.com wrote: LOL, and I have permanent black marks on my office carpet, my home, my truck, my clothes, my harness etc etc... When coax seal gets HOT it doesn't melt but it gets real soft and sticky and will not ever come off anything. Its been such a mess here in FL that I have actually stopped using it. I use this other stuff now that is thinner and cleaner I prefer, sorry forget what its called. If I must use coax seal I put this under it so I can actually remove the junk when I take it apart and end up with a clean cable when done. Scott Carullo Brevard Wireless 321-205-1100 x102 From: Travis Johnson t...@ida.net Sent: Tuesday, November 24, 2009 1:57 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] Times Microwave EZ connectors I second this. We have used this for 5+ years now and haven't had a single water issue since we started using it. And it's cheap, and easy to work with in the summer heat and the winter cold. Travis Josh Luthman wrote: Best. Stuff. Ever. http://www.amazon.com/gp/product/B0002ZPINC/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=48 6539851pf_rd_s=lpo-top-stripe-1pf_rd_t=201pf_rd_i=B00075J4J6pf_rd_m=ATVP DKIKX0DERpf_rd_r=0YKHJM87AJ2TBD52DRE2 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Nov 24, 2009 at 1:13 PM, Robert West robert.w...@just-micro.comwrote: Rubber tape rules on this end. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Marlon K. Schafer Sent: Tuesday, November 24, 2009 12:50 PM To: WISPA General List Subject: Re: [WISPA] Times Microwave EZ connectors Heat shrink doesn't work in the cold. It will get hard (the glue) and as things move in the wind etc. it'll allow water in. Been there done that. NOTHING works better than self vulcanizing rubber tape. If what you use is easy to get off it's not a good tight seal. sigh It sure can't be that hard to build a connector that seals without the tape! sigh marlon - Original Message - From: RickG rgunder...@gmail.com To: WISPA General List wireless@wispa.org Sent: Thursday, November 19, 2009 6:15 PM Subject: Re: [WISPA] Times Microwave EZ connectors Yes - hate the mess but seals the best! On Thu, Nov 19, 2009 at 6:43 PM, os10ru...@gmail.com wrote: Coax-seal On Nov 19, 2009, at 6:42 PM, AJ wrote: CANUSA adhesive shrink tubing is your friend :) On Thu, Nov 19, 2009 at 4:41 PM, lakel...@gbcx.net wrote: No 400 connector from any of the manufacturers is weatherproof by itself. You need to weatherproof all of your connections. If they are not getting wet you are lucky. Plain and simple. Bob Sent from my Verizon Wireless BlackBerry -Original Message- From: MDK rea...@muddyfrogwater.us Date: Thu, 19 Nov 2009 10:20:52 To: WISPA General Listwireless@wispa.org Subject: [WISPA] Times Microwave EZ connectors I've run out of these, and none of the vendors I use commonly carry them. Anyone out west have these? Yeah, I know, it costs more to buy two of these than a whole pre-built 10 foot cable, but every danged pre-built I buy has water issues. We have never had to seal any of the cables we built ourselves, and none of them have ever leaked (except when someone who'll forever remain nameless forgot to tighten the cable...), but I have no luck at all with the pre-made I've bought from multiple places. Our temporary site needed to go up in a real hurry, so I bought a whole pile of parts and cables, and most of them have had issues. 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:
[WISPA] Sectors
I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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] Sectors
That is the general suggestion - two 120s. That one guy that does antenna design said so :) You will get some less coverage then three 120s but at the cost of the extra radio/antenna it isn't cost efficient. On 12/1/09, Mark McElvy mmce...@accubak.com wrote: I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein 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] Sectors
What size omni are you using? -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 7:59 PM To: WISPA General List Subject: Re: [WISPA] Sectors That is the general suggestion - two 120s. That one guy that does antenna design said so :) You will get some less coverage then three 120s but at the cost of the extra radio/antenna it isn't cost efficient. On 12/1/09, Mark McElvy mmce...@accubak.com wrote: I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark - --- 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein --- - 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.89/2539 - Release Date: 12/01/09 19:32:00 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] 5.6 GHZ?
S P E C T R U M A N A L Y Z E R Scott Carullo wrote: Anyone know of a way to find out what freq a weather radar is operating on? I know of several local ones and would like to know what freq they operate on for safety sake. Any ideas? I've looked everywhere and found nothing? Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jack Unger jun...@ask-wi.com Sent: Saturday, November 21, 2009 1:16 PM To: WISPA General List wireless@wispa.org, memb...@wispa.org memb...@wispa.org Subject: Re: [WISPA] 5.6 GHZ? IMO, it is iffy for the reason you mentioned. The FCC (at the request of the FAA and the NTIA) appears ready to deny use of the 5.6 spectrum in areas where interference with airport weather radar takes place. I doubt that any WISP would ague that their use of that spectrum is more important than safe operation of commercial aircraft. I expect that newly certified 5 GHz equipment will soon (within the next year) include a updated DFS algorithm that looks for the presence of 5.6 GHz radar and switches away from 5.6 when radar is detected. Your existing equipment may remain technically legal but you do run the risk of possibly being blamed for aircraft crashes assuming you are unlucky enough to be using 5.6 near airports where you could cause actual interference to Terminal Doppler Weather Radar systems. See http://tiny.cc/LIlqB for more information. jack Travis Johnson wrote: It's iffy because the FCC allowed the specific band, and now they are trying to take it back away... two years later. If I never upgrade my radios, does that mean I'm legal to run in that specific band forever? I just don't understand how they can allow it for 2 years, and then try and take it away and think they are going to clean up the airways. Travis Microserv 3-dB Networks wrote: Motorola Canopy 5.4GHz radios updated with the latest firmware cannot transmit in the 5600-5650 part of the band. I don't understand what is iffy about the band... Canopy operators have been using it for two years or so now legally, and while DFS still has issues in its current implementation, the FCC is working to make the DFS detection better on the radio side and in turn make it harder to radio manufacturers to allow clients to avoid using DFS Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jack Unger Sent: Friday, November 20, 2009 11:02 PM To: WISPA General List Subject: Re: [WISPA] 5.6 GHZ? 5470 - 5725 is a legitimate band but DFS2 must be used on the radios. There is currently FCC activity to modify the DFS profiles for all newly-certified radios to avoid aircraft radar system in the 5.6 GHz part of the 5470-5725 band. The bottom line is - it's pretty iffy.jack Forbes Mercy wrote: My new MIMO radios have 5.6 GHZ on them, I don't recall that frequency being available in the US. Is it? Forbes 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... WISPA Wants You! Join today! http://signup.wispa.org/
Re: [WISPA] Sectors
4 90's would be better... but you could make 2 120's work probably. Check the patterns, and try to align the sectors where the bulk of the customers are. MTI does have some 900MHz 180's in H-pol... Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mark McElvy Sent: Tuesday, December 01, 2009 5:38 PM To: WISPA General List Subject: [WISPA] Sectors I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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] Sectors
From an omni two 120s will get you more coverage, doesn't it? On 12/1/09, 3-dB Networks wi...@3-db.net wrote: 4 90's would be better... but you could make 2 120's work probably. Check the patterns, and try to align the sectors where the bulk of the customers are. MTI does have some 900MHz 180's in H-pol... Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mark McElvy Sent: Tuesday, December 01, 2009 5:38 PM To: WISPA General List Subject: [WISPA] Sectors I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein 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] Sectors
I have looked at several 120 patterns and it looks to me like there would be a HUGE gap on the far sides of each antenna? The one pattern I am looking at shows -20db down at 90 degrees on each side. I'm just not sure how well it would actually work? Travis Microserv Josh Luthman wrote: That is the general suggestion - two 120s. That one guy that does antenna design said so :) You will get some less coverage then three 120s but at the cost of the extra radio/antenna it isn't cost efficient. On 12/1/09, Mark McElvy mmce...@accubak.com wrote: I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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] Sectors
Honestly, I doubt the quality of a 120 degree sector that will give you 180 degree coverage. I would hope your at -6dB or -8dB at that point. For instance... check out this sector... its -6dB off at 180 degrees http://www.mtiwe.com/uploads/product/127.pdf So your 12dBi sector is now a 6dBi sector... Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 7:36 PM To: WISPA General List Subject: Re: [WISPA] Sectors From an omni two 120s will get you more coverage, doesn't it? On 12/1/09, 3-dB Networks wi...@3-db.net wrote: 4 90's would be better... but you could make 2 120's work probably. Check the patterns, and try to align the sectors where the bulk of the customers are. MTI does have some 900MHz 180's in H-pol... Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mark McElvy Sent: Tuesday, December 01, 2009 5:38 PM To: WISPA General List Subject: [WISPA] Sectors I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein 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] Sectors
9db -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Rick Harnish Sent: Tuesday, December 01, 2009 7:42 PM To: 'WISPA General List' Subject: Re: [WISPA] Sectors What size omni are you using? -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 7:59 PM To: WISPA General List Subject: Re: [WISPA] Sectors That is the general suggestion - two 120s. That one guy that does antenna design said so :) You will get some less coverage then three 120s but at the cost of the extra radio/antenna it isn't cost efficient. On 12/1/09, Mark McElvy mmce...@accubak.com wrote: I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark - --- 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein --- - 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.89/2539 - Release Date: 12/01/09 19:32:00 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.72/2511 - Release Date: 12/01/09 01:59:00 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] Iowa Telecom a.k.a Windstream
They are in the next county over. Their reputation here (Central Kentucky) is not very good. Their customers call begging me to come there saying they are down more than up. With that said, if you want a phone line, they have a fair deal. But, as you know, most people have cut the cord. -RickG On Tue, Dec 1, 2009 at 10:04 AM, Mike m...@aweiowa.com wrote: My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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] Iowa Telecom a.k.a Windstream
I hate it too! On Tue, Dec 1, 2009 at 10:22 AM, Jayson Baker jay...@spectrasurf.comwrote: If this is their install truck, I don't think you have to worry about much. [image: ?ui=2view=attth=1254ad61273873f9attid=0.1disp=attdrealattid=ii_1254ad61273873f9zw] LOL On Tue, Dec 1, 2009 at 8:04 AM, Mike m...@aweiowa.com wrote: My primary competition for the past few years has been Iowa Telecom. They have been purchased by Windstream. I knew what to expect from Iowa Telecom, but don't now. Have any of you had experience with Windstream? Should I be bracing for some real competition? Iowa Telecom decisions, in my analysis are based mostly on use of their wired facilities. DSL, phone service are primary, and their wireless offerings, with phone and Dish, have been secondary. Should I expect the same from Winstream? Mike 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] Sectors
What frequency band and polarization? I would also strongly consider your reasoning for moving from the Omni to the sectors. If it is because your AP is overloaded so you need to offload some, 3 AP's might be attractive for future proofing sakes. Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mark McElvy Sent: Tuesday, December 01, 2009 8:29 PM To: WISPA General List Subject: Re: [WISPA] Sectors 9db -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Rick Harnish Sent: Tuesday, December 01, 2009 7:42 PM To: 'WISPA General List' Subject: Re: [WISPA] Sectors What size omni are you using? -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 7:59 PM To: WISPA General List Subject: Re: [WISPA] Sectors That is the general suggestion - two 120s. That one guy that does antenna design said so :) You will get some less coverage then three 120s but at the cost of the extra radio/antenna it isn't cost efficient. On 12/1/09, Mark McElvy mmce...@accubak.com wrote: I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark - --- 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein --- - 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.89/2539 - Release Date: 12/01/09 19:32:00 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.72/2511 - Release Date: 12/01/09 01:59:00 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] Sectors
I am running 2.4 HPOL It has taken about 1.5 yrs to grow this AP to 32 subs. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of 3-dB Networks Sent: Tuesday, December 01, 2009 9:37 PM To: 'WISPA General List' Subject: Re: [WISPA] Sectors What frequency band and polarization? I would also strongly consider your reasoning for moving from the Omni to the sectors. If it is because your AP is overloaded so you need to offload some, 3 AP's might be attractive for future proofing sakes. Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mark McElvy Sent: Tuesday, December 01, 2009 8:29 PM To: WISPA General List Subject: Re: [WISPA] Sectors 9db -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Rick Harnish Sent: Tuesday, December 01, 2009 7:42 PM To: 'WISPA General List' Subject: Re: [WISPA] Sectors What size omni are you using? -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 7:59 PM To: WISPA General List Subject: Re: [WISPA] Sectors That is the general suggestion - two 120s. That one guy that does antenna design said so :) You will get some less coverage then three 120s but at the cost of the extra radio/antenna it isn't cost efficient. On 12/1/09, Mark McElvy mmce...@accubak.com wrote: I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark - --- 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein --- - 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.89/2539 - Release Date: 12/01/09 19:32:00 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.72/2511 - Release Date: 12/01/09 01:59:00 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/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.72/2511 - Release Date: 12/01/09 01:59:00 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] 20 mile link
THANKS to EVERYONE for their input. I'll let you know what I decide. Another question: Normally I do my path analysis with Delorme but I'm not feeling that is good enough considering the cost of the project and some trees I see in the distance. Is anyone out there offering path analysis for a fair rate? -RickG On Tue, Dec 1, 2009 at 9:36 AM, Mike m...@aweiowa.com wrote: Rick: You have been getting some good advice here. I am not a networking guru and have never played one on TV, but do know a thing or two about RF. It seems with your physical layout you may have an opportunity for some space diversity. A simple link will probably serve you with 3 nines or so. If infrequent outages will sit OK with the user, then engineer a link with single radios. If you use some of the more inexpensive radio solutions as proffered here, you could put up two links with 20' to 30' of physical separation. Or, one dish on the water tower, and two on the new tower. The single one could be the AP and the other two remote ones stations. You could use an MT router running OSPF with one having a higher cost than the other. If one failed, the other would take over. My fear of a 20 mile link would be those atmospheric events we sometimes see -- tropospheric ducting. I would be curious what you come up with. Mike At 09:22 PM 11/30/2009, you wrote: Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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] Times Microwave EZ connectors
Use a double-layer of high grade electrical tape with the coax seal in between. -RickG On Tue, Dec 1, 2009 at 6:44 PM, Josh Luthman j...@imaginenetworksllc.comwrote: Never made a mess except on threads like N female connectors. On 12/1/09, Scott Carullo sc...@brevardwireless.com wrote: LOL, and I have permanent black marks on my office carpet, my home, my truck, my clothes, my harness etc etc... When coax seal gets HOT it doesn't melt but it gets real soft and sticky and will not ever come off anything. Its been such a mess here in FL that I have actually stopped using it. I use this other stuff now that is thinner and cleaner I prefer, sorry forget what its called. If I must use coax seal I put this under it so I can actually remove the junk when I take it apart and end up with a clean cable when done. Scott Carullo Brevard Wireless 321-205-1100 x102 From: Travis Johnson t...@ida.net Sent: Tuesday, November 24, 2009 1:57 PM To: WISPA General List wireless@wispa.org Subject: Re: [WISPA] Times Microwave EZ connectors I second this. We have used this for 5+ years now and haven't had a single water issue since we started using it. And it's cheap, and easy to work with in the summer heat and the winter cold. Travis Josh Luthman wrote: Best. Stuff. Ever. http://www.amazon.com/gp/product/B0002ZPINC/ref=pd_lpo_k2_dp_sr_1?pf_rd_p=48 6539851pf_rd_s=lpo-top-stripe-1pf_rd_t=201pf_rd_i=B00075J4J6pf_rd_m=ATVP DKIKX0DERpf_rd_r=0YKHJM87AJ2TBD52DRE2 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein On Tue, Nov 24, 2009 at 1:13 PM, Robert West robert.w...@just-micro.comwrote: Rubber tape rules on this end. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Marlon K. Schafer Sent: Tuesday, November 24, 2009 12:50 PM To: WISPA General List Subject: Re: [WISPA] Times Microwave EZ connectors Heat shrink doesn't work in the cold. It will get hard (the glue) and as things move in the wind etc. it'll allow water in. Been there done that. NOTHING works better than self vulcanizing rubber tape. If what you use is easy to get off it's not a good tight seal. sigh It sure can't be that hard to build a connector that seals without the tape! sigh marlon - Original Message - From: RickG rgunder...@gmail.com To: WISPA General List wireless@wispa.org Sent: Thursday, November 19, 2009 6:15 PM Subject: Re: [WISPA] Times Microwave EZ connectors Yes - hate the mess but seals the best! On Thu, Nov 19, 2009 at 6:43 PM, os10ru...@gmail.com wrote: Coax-seal On Nov 19, 2009, at 6:42 PM, AJ wrote: CANUSA adhesive shrink tubing is your friend :) On Thu, Nov 19, 2009 at 4:41 PM, lakel...@gbcx.net wrote: No 400 connector from any of the manufacturers is weatherproof by itself. You need to weatherproof all of your connections. If they are not getting wet you are lucky. Plain and simple. Bob Sent from my Verizon Wireless BlackBerry -Original Message- From: MDK rea...@muddyfrogwater.us Date: Thu, 19 Nov 2009 10:20:52 To: WISPA General Listwireless@wispa.org Subject: [WISPA] Times Microwave EZ connectors I've run out of these, and none of the vendors I use commonly carry them. Anyone out west have these? Yeah, I know, it costs more to buy two of these than a whole pre-built 10 foot cable, but every danged pre-built I buy has water issues. We have never had to seal any of the cables we built ourselves, and none of them have ever leaked (except when someone who'll forever remain nameless forgot to tighten the cable...), but I have no luck at all with the pre-made I've bought from multiple places. Our temporary site needed to go up in a real hurry, so I bought a whole pile of parts and cables, and most of them have had issues. 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
Re: [WISPA] 20 mile link
$75 using 10 meter terrain data and 30 meter resolution tree clutter. Thank You, Brian Webster 214 Eggleston Hill Rd. Cooperstown, NY 13326 www.wirelessmapping.com 607-643-4055 Voice 607-435-3988 Mobile 208-692-1898 Fax On Tue, Dec 1, 2009 at 10:59 PM, RickG rgunder...@gmail.com wrote: THANKS to EVERYONE for their input. I'll let you know what I decide. Another question: Normally I do my path analysis with Delorme but I'm not feeling that is good enough considering the cost of the project and some trees I see in the distance. Is anyone out there offering path analysis for a fair rate? -RickG On Tue, Dec 1, 2009 at 9:36 AM, Mike m...@aweiowa.com wrote: Rick: You have been getting some good advice here. I am not a networking guru and have never played one on TV, but do know a thing or two about RF. It seems with your physical layout you may have an opportunity for some space diversity. A simple link will probably serve you with 3 nines or so. If infrequent outages will sit OK with the user, then engineer a link with single radios. If you use some of the more inexpensive radio solutions as proffered here, you could put up two links with 20' to 30' of physical separation. Or, one dish on the water tower, and two on the new tower. The single one could be the AP and the other two remote ones stations. You could use an MT router running OSPF with one having a higher cost than the other. If one failed, the other would take over. My fear of a 20 mile link would be those atmospheric events we sometimes see -- tropospheric ducting. I would be curious what you come up with. Mike At 09:22 PM 11/30/2009, you wrote: Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG 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] 5.6 GHZ?
HA! Someone had to say it. I know we were all thinking it. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jack Unger Sent: Tuesday, December 01, 2009 9:11 PM To: sc...@brevardwireless.com; WISPA General List Subject: Re: [WISPA] 5.6 GHZ? S P E C T R U M A N A L Y Z E R Scott Carullo wrote: Anyone know of a way to find out what freq a weather radar is operating on? I know of several local ones and would like to know what freq they operate on for safety sake. Any ideas? I've looked everywhere and found nothing? Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jack Unger jun...@ask-wi.com Sent: Saturday, November 21, 2009 1:16 PM To: WISPA General List wireless@wispa.org, memb...@wispa.org memb...@wispa.org Subject: Re: [WISPA] 5.6 GHZ? IMO, it is iffy for the reason you mentioned. The FCC (at the request of the FAA and the NTIA) appears ready to deny use of the 5.6 spectrum in areas where interference with airport weather radar takes place. I doubt that any WISP would ague that their use of that spectrum is more important than safe operation of commercial aircraft. I expect that newly certified 5 GHz equipment will soon (within the next year) include a updated DFS algorithm that looks for the presence of 5.6 GHz radar and switches away from 5.6 when radar is detected. Your existing equipment may remain technically legal but you do run the risk of possibly being blamed for aircraft crashes assuming you are unlucky enough to be using 5.6 near airports where you could cause actual interference to Terminal Doppler Weather Radar systems. See http://tiny.cc/LIlqB for more information. jack Travis Johnson wrote: It's iffy because the FCC allowed the specific band, and now they are trying to take it back away... two years later. If I never upgrade my radios, does that mean I'm legal to run in that specific band forever? I just don't understand how they can allow it for 2 years, and then try and take it away and think they are going to clean up the airways. Travis Microserv 3-dB Networks wrote: Motorola Canopy 5.4GHz radios updated with the latest firmware cannot transmit in the 5600-5650 part of the band. I don't understand what is iffy about the band... Canopy operators have been using it for two years or so now legally, and while DFS still has issues in its current implementation, the FCC is working to make the DFS detection better on the radio side and in turn make it harder to radio manufacturers to allow clients to avoid using DFS Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jack Unger Sent: Friday, November 20, 2009 11:02 PM To: WISPA General List Subject: Re: [WISPA] 5.6 GHZ? 5470 - 5725 is a legitimate band but DFS2 must be used on the radios. There is currently FCC activity to modify the DFS profiles for all newly-certified radios to avoid aircraft radar system in the 5.6 GHz part of the 5470-5725 band. The bottom line is - it's pretty iffy.jack Forbes Mercy wrote: My new MIMO radios have 5.6 GHZ on them, I don't recall that frequency being available in the US. Is it? Forbes 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying
Re: [WISPA] Sectors
Depending on the cost of whatever sector you are looking at, I think the extra cash for the third antenna and radio would offset the amount of aggravation. Take it from someone who is cheap, just spend the extra cash. Been there, done that, have less hair over it. (That's why I wear a hat) Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of 3-dB Networks Sent: Tuesday, December 01, 2009 10:22 PM To: 'WISPA General List' Subject: Re: [WISPA] Sectors Honestly, I doubt the quality of a 120 degree sector that will give you 180 degree coverage. I would hope your at -6dB or -8dB at that point. For instance... check out this sector... its -6dB off at 180 degrees http://www.mtiwe.com/uploads/product/127.pdf So your 12dBi sector is now a 6dBi sector... Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Tuesday, December 01, 2009 7:36 PM To: WISPA General List Subject: Re: [WISPA] Sectors From an omni two 120s will get you more coverage, doesn't it? On 12/1/09, 3-dB Networks wi...@3-db.net wrote: 4 90's would be better... but you could make 2 120's work probably. Check the patterns, and try to align the sectors where the bulk of the customers are. MTI does have some 900MHz 180's in H-pol... Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mark McElvy Sent: Tuesday, December 01, 2009 5:38 PM To: WISPA General List Subject: [WISPA] Sectors I need to sector a tower that currently is an omni. I don't really want to go to 3x 120's but find it hard to find 180's and have heard they don't tend to work great. I have also heard 2x 120's will work, any comments? Mark 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 The secret to creativity is knowing how to hide your sources. --- Albert Einstein 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] 20 mile link
A relatively nifty new monitoring service out there also has a great path profile tool built-in. The person that is developing the product is a long time wireless operator, so he has a very good feel for what our industry needs. www.wispmon.com I've been a RadioMobile user for years now, but have found myself using the path profiler in wispmon more often than RadioMobile. Best, Brad -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Brian Webster Sent: Tuesday, December 01, 2009 10:21 PM To: WISPA General List Subject: Re: [WISPA] 20 mile link $75 using 10 meter terrain data and 30 meter resolution tree clutter. Thank You, Brian Webster 214 Eggleston Hill Rd. Cooperstown, NY 13326 www.wirelessmapping.com 607-643-4055 Voice 607-435-3988 Mobile 208-692-1898 Fax On Tue, Dec 1, 2009 at 10:59 PM, RickG rgunder...@gmail.com wrote: THANKS to EVERYONE for their input. I'll let you know what I decide. Another question: Normally I do my path analysis with Delorme but I'm not feeling that is good enough considering the cost of the project and some trees I see in the distance. Is anyone out there offering path analysis for a fair rate? -RickG On Tue, Dec 1, 2009 at 9:36 AM, Mike m...@aweiowa.com wrote: Rick: You have been getting some good advice here. I am not a networking guru and have never played one on TV, but do know a thing or two about RF. It seems with your physical layout you may have an opportunity for some space diversity. A simple link will probably serve you with 3 nines or so. If infrequent outages will sit OK with the user, then engineer a link with single radios. If you use some of the more inexpensive radio solutions as proffered here, you could put up two links with 20' to 30' of physical separation. Or, one dish on the water tower, and two on the new tower. The single one could be the AP and the other two remote ones stations. You could use an MT router running OSPF with one having a higher cost than the other. If one failed, the other would take over. My fear of a 20 mile link would be those atmospheric events we sometimes see -- tropospheric ducting. I would be curious what you come up with. Mike At 09:22 PM 11/30/2009, you wrote: Planning my first 20 mile PTP link. Path analysis shows clear. Customer is building a 100' tower just for this therefore the equipment I choose must work. I'm free to use whatever I want. Suggestions? -RickG --- - 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/ 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] 5.6 GHZ?
Ouija board. Just document your findings in case the FCC gives you any guff. You need to be able to back yourself up. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Scott Carullo Sent: Tuesday, December 01, 2009 6:22 PM To: WISPA General List Subject: Re: [WISPA] 5.6 GHZ? Anyone know of a way to find out what freq a weather radar is operating on? I know of several local ones and would like to know what freq they operate on for safety sake. Any ideas? I've looked everywhere and found nothing? Scott Carullo Brevard Wireless 321-205-1100 x102 From: Jack Unger jun...@ask-wi.com Sent: Saturday, November 21, 2009 1:16 PM To: WISPA General List wireless@wispa.org, memb...@wispa.org memb...@wispa.org Subject: Re: [WISPA] 5.6 GHZ? IMO, it is iffy for the reason you mentioned. The FCC (at the request of the FAA and the NTIA) appears ready to deny use of the 5.6 spectrum in areas where interference with airport weather radar takes place. I doubt that any WISP would ague that their use of that spectrum is more important than safe operation of commercial aircraft. I expect that newly certified 5 GHz equipment will soon (within the next year) include a updated DFS algorithm that looks for the presence of 5.6 GHz radar and switches away from 5.6 when radar is detected. Your existing equipment may remain technically legal but you do run the risk of possibly being blamed for aircraft crashes assuming you are unlucky enough to be using 5.6 near airports where you could cause actual interference to Terminal Doppler Weather Radar systems. See http://tiny.cc/LIlqB for more information. jack Travis Johnson wrote: It's iffy because the FCC allowed the specific band, and now they are trying to take it back away... two years later. If I never upgrade my radios, does that mean I'm legal to run in that specific band forever? I just don't understand how they can allow it for 2 years, and then try and take it away and think they are going to clean up the airways. Travis Microserv 3-dB Networks wrote: Motorola Canopy 5.4GHz radios updated with the latest firmware cannot transmit in the 5600-5650 part of the band. I don't understand what is iffy about the band... Canopy operators have been using it for two years or so now legally, and while DFS still has issues in its current implementation, the FCC is working to make the DFS detection better on the radio side and in turn make it harder to radio manufacturers to allow clients to avoid using DFS Daniel White 3-dB Networks http://www.3dbnetworks.com -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Jack Unger Sent: Friday, November 20, 2009 11:02 PM To: WISPA General List Subject: Re: [WISPA] 5.6 GHZ? 5470 - 5725 is a legitimate band but DFS2 must be used on the radios. There is currently FCC activity to modify the DFS profiles for all newly-certified radios to avoid aircraft radar system in the 5.6 GHz part of the 5470-5725 band. The bottom line is - it's pretty iffy.jack Forbes Mercy wrote: My new MIMO radios have 5.6 GHZ on them, I don't recall that frequency being available in the US. Is it? Forbes 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/ -- Jack Unger - President, Ask-Wi.Com, Inc. Author - Deploying License-Free Wireless WANs Serving the Broadband Wireless Industry Since 1993 www.ask-wi.com 818-227-4220 jun...@ask-wi.com Sent from my Pizzicato PluckString... 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/
