Re: [WISPA] Leasing Companies
I have had good experiences with Landmark Financial in Denver.Good folks. Matt Larsen vistabeam.com On 6/4/2010 11:52 PM, David wrote: Both CTI and Boun at doubleradius can help get you with honest leasing companies. David -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Kevin Sullivan Sent: Friday, June 04, 2010 6:11 PM To: WISPA General List Subject: Re: [WISPA] Leasing Companies I've applied to several leasing companies, mostly for licensed links. All of them gave me an appox. rate for a five year term of under 10% per year. Then, after they ran credit, they came back with a monthly payment but wouldn't tell me the rate. I calculated it to be over 25% annually in all of the cases. When I talked to them about it, they all said that they don't actually do rates, they just give a monthly amount, since that's easier for people to understand. In all of the cases, if we had signed up, we would have paid more than three times what the equipment cost by the time the lease was done. One of them even tried that old Rule of 78 method for calulating interest. I didn't even think that was still legal in the US! Two of them verbally told us the lease was for a $1 buyout, but then in the fine print it said we would have to pay, fair market value, whatever that means. If I ever find a honest leasing company, it'll make my business easier and more profitable. Until then, we'll continue to grow slowly. Cheers, Kevin 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] Leasing Companies
If you have a good business plan your probably better off dealing with a local bank IMO. If you cant convince the bank your business plan is good then something might be wrong with your business plan. We do out of pocket now but several years ago after showing the bank our business plan they gave me whatever I wanted as long as I showed them my MRC. Joe Laura - Original Message - From: David ad...@speedyquick.net To: 'WISPA General List' wireless@wispa.org Sent: Saturday, June 05, 2010 12:52 AM Subject: Re: [WISPA] Leasing Companies Both CTI and Boun at doubleradius can help get you with honest leasing companies. David 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] Leasing Companies
While leasing is a viable option, I would seriously take a look at the programs the SBA has to offer I'm in the process of finalizing an SBA 504 loan for $400k You need to put down 10%, but if that's not a problem, it's perfect for this space as it specifically deals with hard asset acquisition With the stimulus bill waiving the standard 2% SBA processing fee, it's a pretty good deal All in, I'm looking at 1% for closing costs and a 10 year note at 4.43% Details here: http://www.sba.gov/financialassistance/borrowers/guaranteed/CDC504lp/index.html -Charles -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Joe Laura Sent: Saturday, June 05, 2010 1:06 AM To: WISPA General List Subject: Re: [WISPA] Leasing Companies If you have a good business plan your probably better off dealing with a local bank IMO. If you cant convince the bank your business plan is good then something might be wrong with your business plan. We do out of pocket now but several years ago after showing the bank our business plan they gave me whatever I wanted as long as I showed them my MRC. Joe Laura - Original Message - From: David ad...@speedyquick.net To: 'WISPA General List' wireless@wispa.org Sent: Saturday, June 05, 2010 12:52 AM Subject: Re: [WISPA] Leasing Companies Both CTI and Boun at doubleradius can help get you with honest leasing companies. David 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] sprint 4g reviews?
I know they call it 4G, but it's not 4G. See http://www.wirelessweek.com/Archives/2007/10/WiMAX-is-3G/ Even LTE (when deployed) won't be 4G, only LTE Advanced will, but LTE will be much closer to 4G than WiMAX 802.16e, see http://www.radio-electronics.com/info/cellulartelecomms/4g/3gpp-imt-lte-advanced-tutorial.php. May be 802.16m can achieve 4G goals, if WiMAX still lives by then. Rubens On Fri, Jun 4, 2010 at 9:25 PM, Robert Kim Wireless Internet Advisor evdo.hs...@gmail.com wrote: hi guys... it's been a while! So since the whole 3g thing went mega corporate and independents like me got pushed out, i havent paid much attention to the wireless space ... but has anyone here used sprint's 4g network? -- Robert Q Kim 2611 S Coast Highway San Diego, CA 92007 310 598 1606 http://disastearth.com Natural and Man Made Disasters http://bioprin.posterous.com Health Myths You Still Believe 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] sprint 4g reviews?
I've seen articles saying that (I haven't read any of them), but I don't buy it. Just a few bloggers trying to make a stink. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com On 6/5/2010 9:30 AM, Rubens Kuhl wrote: I know they call it 4G, but it's not 4G. See http://www.wirelessweek.com/Archives/2007/10/WiMAX-is-3G/ Even LTE (when deployed) won't be 4G, only LTE Advanced will, but LTE will be much closer to 4G than WiMAX 802.16e, see http://www.radio-electronics.com/info/cellulartelecomms/4g/3gpp-imt-lte-advanced-tutorial.php. May be 802.16m can achieve 4G goals, if WiMAX still lives by then. Rubens On Fri, Jun 4, 2010 at 9:25 PM, Robert Kim Wireless Internet Advisor evdo.hs...@gmail.com wrote: hi guys... it's been a while! So since the whole 3g thing went mega corporate and independents like me got pushed out, i havent paid much attention to the wireless space ... but has anyone here used sprint's 4g network? -- Robert Q Kim 2611 S Coast Highway San Diego, CA 92007 310 598 1606 http://disastearth.com Natural and Man Made Disasters http://bioprin.posterous.com Health Myths You Still Believe 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] sprint 4g reviews?
If you are willing to spend a few dollars on an ITU-R document, it's this one that describes 4G: http://www.itu.int/rec/R-REC-M.1645-0-200306-I/en (Framework and overall objectives of the future development of IMT-2000 and systems beyond IMT-2000) The most famous quote from this document is the data rates - 1 Gbps for fixed service, 100 Mbps for mobile service. I'm pretty sure Sprint's Clear service doesn't have such data rates. Rubens On Sat, Jun 5, 2010 at 11:50 AM, Mike Hammett wispawirel...@ics-il.net wrote: I've seen articles saying that (I haven't read any of them), but I don't buy it. Just a few bloggers trying to make a stink. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com On 6/5/2010 9:30 AM, Rubens Kuhl wrote: I know they call it 4G, but it's not 4G. See http://www.wirelessweek.com/Archives/2007/10/WiMAX-is-3G/ Even LTE (when deployed) won't be 4G, only LTE Advanced will, but LTE will be much closer to 4G than WiMAX 802.16e, see http://www.radio-electronics.com/info/cellulartelecomms/4g/3gpp-imt-lte-advanced-tutorial.php. May be 802.16m can achieve 4G goals, if WiMAX still lives by then. Rubens On Fri, Jun 4, 2010 at 9:25 PM, Robert Kim Wireless Internet Advisor evdo.hs...@gmail.com wrote: hi guys... it's been a while! So since the whole 3g thing went mega corporate and independents like me got pushed out, i havent paid much attention to the wireless space ... but has anyone here used sprint's 4g network? -- Robert Q Kim 2611 S Coast Highway San Diego, CA 92007 310 598 1606 http://disastearth.com Natural and Man Made Disasters http://bioprin.posterous.com Health Myths You Still Believe 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
They are linux based. Use ethtool interface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Just guessing, but could they require a crossover cable when both are forced? According to Wikipedia Auto-MDIX requires the speed and duplex setting to be set to auto. http://en.wikipedia.org/wiki/Auto-MDIX On Sat, Jun 5, 2010 at 12:58 PM, Greg Ihnen os10ru...@gmail.com wrote: I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Thanks! I'll check it. Greg On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtool interface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Great idea. I'll try that. Greg On Jun 5, 2010, at 1:53 PM, Philip Dorr wrote: Just guessing, but could they require a crossover cable when both are forced? According to Wikipedia Auto-MDIX requires the speed and duplex setting to be set to auto. http://en.wikipedia.org/wiki/Auto-MDIX On Sat, Jun 5, 2010 at 12:58 PM, Greg Ihnen os10ru...@gmail.com wrote: I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtool interface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Thanks! That worked. ifconfig got me: XM.v5.2# ifconfig ath0 Link encap:Ethernet HWaddr 00:15:6D:F0:1C:0E UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:252008 errors:0 dropped:0 overruns:0 frame:0 TX packets:249081 errors:0 dropped:98 overruns:0 carrier:0 collisions:0 txqueuelen:200 RX bytes:19897078 (18.9 MiB) TX bytes:184902979 (176.3 MiB) br0 Link encap:Ethernet HWaddr 00:15:6D:F0:1C:0E inet addr:192.168.7.251 Bcast:192.168.7.255 Mask:255.255.255.0 UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:38025 errors:0 dropped:0 overruns:0 frame:0 TX packets:1183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1035633 (1011.3 KiB) TX bytes:146294 (142.8 KiB) eth0_real Link encap:Ethernet HWaddr 00:15:6D:F1:1C:0E UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:237409 errors:0 dropped:0 overruns:0 frame:0 TX packets:213782 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:183602172 (175.0 MiB) TX bytes:18361329 (17.5 MiB) eth1_real Link encap:Ethernet HWaddr 02:15:6D:F1:1C:0E UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wifi0 Link encap:Ethernet HWaddr 00:15:6D:F0:1C:0E UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:1264 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:511 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:48 Memory:b000-b001 and ethtool eth0_real got me: XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: yes XM.v5.2# Greg On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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
Re: [WISPA] Leasing Companies
Try a calculated interest of 35% to 45%. :-((No, I did not accept) What frustrates me is that most lease companies wont give a rate or payment before they pull a credit report, even if prospect sends them a copy of theirs that was pulled a week earlier. After they pull the credit report, you then have an enquiry against you, and you are stuck. If you turn it down and go to the next leasor, you start with 20 points lower on your Credit report because of the additional inquirey that last leasor made. Obviously, just 1 inquirey on a report wont make much of a difference, But if you already had one or two the last two years (maybe you applied for a circuit city or Target credit card, or a lease the year before), that 1 additional inquirey could infact lower your score 20 points. Its a racket. I just cant stand any lender that make a lending decission based primarilly on a credit score. That 1 inquirely makes absolutely no difference to the applicants credit worthiness. It is a racket. Its funny, one time, I had $50k cash in the bank, $10k on credit cards (with agreegate line up to $12k), and STILL got turned down by 2 leasing companies for a $10k lease app. I had a 650 score, and They replied my Score was to low. The reasons I had a 650 score was that I had more than 50% of my revolving credit used up. (It meant nothing that I paid off and recharded $5k a month on those cards for cash flow, it wasn;t really debt). So, since I had $50k in the bank, I paid the credit cards off. So I wait a month for it to show on my report, my score raises to around 700. Now I go back and apply again for the $10k lease at a third leasing company. I get a reply that I'm turned down again, but this time because I have to many inquiries on my Credit report. They say, try again in a years when the inquiries are gone. Go figure, cant win for loosen.Its much easier for an Employee who take a paycheck every month, to get a lease to buy a Cadilac, that is a luxury and expense, than it is for a small business owner to get a $10k lease, that if granted would generate 10x the revenue than the lease payment. I guess that leasing companies think its just to easy for a small business owner to take the money and run, if they want to. Its to hard to collect on, if the business owner is unscrupulous. Compared to a Employee where wages could be garneshed easilly, or a car repossesed. Self employed is simply looked at as a high risk profile to them. Leasing tends to work better for those that are either really wealthy, (who can easilly prove high networth via assets non-related to their business and high income), or have scaled their businesses large enough that they are no longer looked at as self employed, but instead as just one stockholder of a large successful business entity. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Kevin Sullivan kevin.sulli...@alyrica.net To: WISPA General List wireless@wispa.org Sent: Friday, June 04, 2010 8:11 PM Subject: Re: [WISPA] Leasing Companies I've applied to several leasing companies, mostly for licensed links. All of them gave me an appox. rate for a five year term of under 10% per year. Then, after they ran credit, they came back with a monthly payment but wouldn't tell me the rate. I calculated it to be over 25% annually in all of the cases. When I talked to them about it, they all said that they don't actually do rates, they just give a monthly amount, since that's easier for people to understand. In all of the cases, if we had signed up, we would have paid more than three times what the equipment cost by the time the lease was done. One of them even tried that old Rule of 78 method for calulating interest. I didn't even think that was still legal in the US! Two of them verbally told us the lease was for a $1 buyout, but then in the fine print it said we would have to pay, fair market value, whatever that means. If I ever find a honest leasing company, it'll make my business easier and more profitable. Until then, we'll continue to grow slowly. Cheers, Kevin - Original Message - From: Tom DeReggi wirelessn...@rapiddsl.net To: WISPA General List wireless@wispa.org Sent: Friday, June 04, 2010 11:08 AM Subject: Re: [WISPA] Leasing Companies I would recommend Peer to Peer lending options. (Google peer to peer lending). They will end up being personal loans, and likely lower credit lines, but there is a much higher chance of walking away with a loan, at a reasonable rate. If you meet the financial profile for leasing, Lease Corp of America has some of the lowest rates. They do a lot of the Moto 1yr type leases. With LCA it wont be an issue that you are leasing wireless gear, because they do that all the time. A couple tips on leasing If you do less than 5 mil a year in revenue, or have less than 10 employee, chances
Re: [WISPA] Leasing Companies
Charles, Thanks for the Info/Link. In 2009, SBA had a great program based on a ARRA program, for a basic small business loan for any purpose. They were increasing the SBA guarantee to 90% of loan value (instead of I think it used to be 80% or less). That made it way easy to obtain a bank loan, with only 10% down, because it was 100% risk-free for the bank. But lke any government program lots of paperwork was required. Unforunteately, I did not learn about it until last few weeks of December 2009, and I was not able to compelte all teh requirements in time to submit an application. In 2010, that program expired. :-( The CDC program link you attached, inferred it could be 100% guaranteed by SBA. Wow. But trying to find the catch, of what would disqualify someone? For example. The CDC/504 loan program is a long-term financing tool for economic development within a community. So what qualifies as Economic development? Does this mean that a plan need to be pre defined for loan proceeds to apply to equipment to be used only in the one specific Area/Community, that meets an specific economic profile? For example, If I cover 10 cities, that are of average national economic middle class or higher, and just need money to expand where ever orders may come in, would that be disqualified from this type loan program? The 504 Program provides small businesses requiring brick and mortar financing with long-term, fixed-rate financing to acquire major fixed assets for expansion So it would cover Radios, but not Spectrum leases? A Certified Development Company (CDC) is a private, nonprofit corporation set up to contribute to the economic development of its community. CDCs work with SBA and private sector lenders to provide financing to small businesses The maximum SBA debenture is $2.0 million when meeting a public policy goal. Does that mean you must get an indorsement from the local government for them to say that you are meeting a specific need? a business must create or retain one job for every $65,000 Doesn't sound to hard to justify, for people already with a large number of employees. But that could be a problem for a 2 man company. They'd have to match the equipment loan 30-50% with payroll, likely money they dont have in advance of increasingsales after equipment was deployed. Wondering if they'd except forcasted Jobs. Although, Loans cannot be made to businesses engaged in speculation does not support that. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Charles Wu c...@cticonnect.com To: WISPA General List wireless@wispa.org Sent: Saturday, June 05, 2010 9:36 AM Subject: Re: [WISPA] Leasing Companies While leasing is a viable option, I would seriously take a look at the programs the SBA has to offer I'm in the process of finalizing an SBA 504 loan for $400k You need to put down 10%, but if that's not a problem, it's perfect for this space as it specifically deals with hard asset acquisition With the stimulus bill waiving the standard 2% SBA processing fee, it's a pretty good deal All in, I'm looking at 1% for closing costs and a 10 year note at 4.43% Details here: http://www.sba.gov/financialassistance/borrowers/guaranteed/CDC504lp/index.html -Charles -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Joe Laura Sent: Saturday, June 05, 2010 1:06 AM To: WISPA General List Subject: Re: [WISPA] Leasing Companies If you have a good business plan your probably better off dealing with a local bank IMO. If you cant convince the bank your business plan is good then something might be wrong with your business plan. We do out of pocket now but several years ago after showing the bank our business plan they gave me whatever I wanted as long as I showed them my MRC. Joe Laura - Original Message - From: David ad...@speedyquick.net To: 'WISPA General List' wireless@wispa.org Sent: Saturday, June 05, 2010 12:52 AM Subject: Re: [WISPA] Leasing Companies Both CTI and Boun at doubleradius can help get you with honest leasing companies. David 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Yeah. Thanks! Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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:
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Interesting - My NSM5 shows connected @ 100Mbps/Full but my DLink router shows it @ 100Mbps/Half. It is set for Full/Auto. Running 5.2. Thoughts? On Sat, Jun 5, 2010 at 4:30 PM, Michael Baird m...@tc3net.com wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg 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:
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both directions simultaneously. Is there any way through SSH or scripting to get the UBNT gear to report what speed has been negotiated on the ethernet port using auto negociate? Could this be a bug in the firmware? Thanks! Greg WISPA Wants You! Join
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
I just did some tests with my setup (radio, router, laptop). It ONLY likes the port set to AUTO. Anything else causes it to disconnect or act flaky. You might still need the crossover though as I didnt test between 2 radios. Of course you could use a switch if no crossover is available. On Sat, Jun 5, 2010 at 7:22 PM, Greg Ihnen os10ru...@gmail.com wrote: I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a combined speed of double that so it seems like things are running very well in both
Re: [WISPA] FCC Seeks Volunteers to Test Broadband Speed
What???! I can't get MY DEDICATED T1 for 50 bucks?! I'm outraged and totally ripped off! B-b -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of RickG Sent: Friday, June 04, 2010 10:59 PM To: WISPA General List Subject: Re: [WISPA] FCC Seeks Volunteers to Test Broadband Speed I think the FCC just wants to get people in a frenzy thinking they're getting ripped off so they'll support them more. Now people are going to whine because they dont get what they pay for. Too bad most arent educated enough to know the difference between on net and off net and shared bandwidth versus dedicated bandwidth. They think they get a T1 for $50/month! On Fri, Jun 4, 2010 at 5:13 PM, Robert West robert.w...@just-micro.com wrote: Interesting. Ya know, around here Time Warner directs everyone with a speed issue to test on their nice and conveniently linked on their webpage, speed test server. You can bet it will show your full contracted speeds every time. But... Try hitting something outside of their network. With that logic I could advertise 100mbps speeds Within Network Anyhow, found it funny that the FCC has to get people to do actual speed checks for them. Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Marco Coelho Sent: Friday, June 04, 2010 4:55 PM To: WISPA General List Subject: [WISPA] FCC Seeks Volunteers to Test Broadband Speed http://news.yahoo.com/s/pcworld/20100602/tc_pcworld/fccseeksvolunteers totest broadbandspeed;_ylt=Arhu..hHz12SV_hi0p6UUMD6VbIF;_ylu=X3oDMTNpdjc4NThz BGFzc2 V0A3Bjd29ybGQvMjAxMDA2MDIvZmNjc2Vla3N2b2x1bnRlZXJzdG90ZXN0YnJvYWRiYW5k c3BlZW QEcG9zAzExBHNlYwN5bl9wYWdpbmF0ZV9zdW1tYXJ5X2xpc3QEc2xrA2ZjY3NlZWtzdm9s dQ-- -- Marco C. Coelho Argon Technologies Inc. POB 875 Greenville, TX 75403-0875 903-455-5036 -- -- 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] sprint 4g reviews?
:( Sounds like a lot of my customers out in the sticks who fell for the 3g pitch. -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Mike Hammett Sent: Friday, June 04, 2010 11:22 PM To: WISPA General List Subject: Re: [WISPA] sprint 4g reviews? Today, I have it in my hands, but I'm not under 4G coverage. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com On 6/4/2010 9:53 PM, Jeromie Reeves wrote: Yes it is, Sprint owns Clear and they are releasing a phone (HTC 4G) some time soon. The times I used it, it was not very good at all. High ping, low bandwidth, but these were all the 'pro' install cabled to a indoor AP. On Fri, Jun 4, 2010 at 5:34 PM, Josh Luthman j...@imaginenetworksllc.com wrote: Isn't it Clear's wimax service? On 6/4/10, Robert Kim Wireless Internet Advisorevdo.hs...@gmail.com wrote: hi guys... it's been a while! So since the whole 3g thing went mega corporate and independents like me got pushed out, i havent paid much attention to the wireless space ... but has anyone here used sprint's 4g network? -- Robert Q Kim 2611 S Coast Highway San Diego, CA 92007 310 598 1606 http://disastearth.com Natural and Man Made Disasters http://bioprin.posterous.com Health Myths You Still Believe 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 Success is not final, failure is not fatal: it is the courage to continue that counts. --- Winston Churchill - --- 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] FCC Seeks Volunteers to Test Broadband Speed
And if it's ever down someone is there in 15 minutes. Up and running in 5. And can apply unlimited coupons from the paper 4 years ago. On 6/5/10, Robert West robert.w...@just-micro.com wrote: What???! I can't get MY DEDICATED T1 for 50 bucks?! I'm outraged and totally ripped off! B-b -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of RickG Sent: Friday, June 04, 2010 10:59 PM To: WISPA General List Subject: Re: [WISPA] FCC Seeks Volunteers to Test Broadband Speed I think the FCC just wants to get people in a frenzy thinking they're getting ripped off so they'll support them more. Now people are going to whine because they dont get what they pay for. Too bad most arent educated enough to know the difference between on net and off net and shared bandwidth versus dedicated bandwidth. They think they get a T1 for $50/month! On Fri, Jun 4, 2010 at 5:13 PM, Robert West robert.w...@just-micro.com wrote: Interesting. Ya know, around here Time Warner directs everyone with a speed issue to test on their nice and conveniently linked on their webpage, speed test server. You can bet it will show your full contracted speeds every time. But... Try hitting something outside of their network. With that logic I could advertise 100mbps speeds Within Network Anyhow, found it funny that the FCC has to get people to do actual speed checks for them. Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Marco Coelho Sent: Friday, June 04, 2010 4:55 PM To: WISPA General List Subject: [WISPA] FCC Seeks Volunteers to Test Broadband Speed http://news.yahoo.com/s/pcworld/20100602/tc_pcworld/fccseeksvolunteers totest broadbandspeed;_ylt=Arhu..hHz12SV_hi0p6UUMD6VbIF;_ylu=X3oDMTNpdjc4NThz BGFzc2 V0A3Bjd29ybGQvMjAxMDA2MDIvZmNjc2Vla3N2b2x1bnRlZXJzdG90ZXN0YnJvYWRiYW5k c3BlZW QEcG9zAzExBHNlYwN5bl9wYWdpbmF0ZV9zdW1tYXJ5X2xpc3QEc2xrA2ZjY3NlZWtzdm9s dQ-- -- Marco C. Coelho Argon Technologies Inc. POB 875 Greenville, TX 75403-0875 903-455-5036 -- -- 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/ -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill 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] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
If need be, since you have low supply of connectors, if you have any bad patch cables, cut, cross the tx/rx and splice it just to test. Any true wire geek never throws bad patch away. :) Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Greg Ihnen Sent: Saturday, June 05, 2010 7:22 PM To: WISPA General List Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the BulletM2 through the ethernet cable to the close NanostationM5, then across the wireless connection (AirMax, no ptp ack) to the far NanostationM5) I'm seeing speeds of 95Mbps both directions with a
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernetwhen forced to 100Mbps full duplex
Actually, I've been running into a very similar issue. We have a customer who has a Nanobridge M5 plugged into a Cisco router. It mostly doesn't work with auto negotiation, (90+% packet loss), and it doesn't work at all on 100mbps full forced. It workes great at 10full forced on both ends, but obviously at lower speeds. We just hooked up a temp customer who also had a Cisco router, and had exactly the same deal, except they were into a Rocket M5. We wound up putting a switch between the Cisco and the Rocket to be able to talk at 100mbps. I'm starting to wonder if the forced 100full setting is broken. Kevin - Original Message - From: Robert West robert.w...@just-micro.com To: 'WISPA General List' wireless@wispa.org Sent: Saturday, June 05, 2010 5:04 PM Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernetwhen forced to 100Mbps full duplex If need be, since you have low supply of connectors, if you have any bad patch cables, cut, cross the tx/rx and splice it just to test. Any true wire geek never throws bad patch away. :) Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Greg Ihnen Sent: Saturday, June 05, 2010 7:22 PM To: WISPA General List Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernetwhen forced to 100Mbps full duplex
Here I have two NanostationM5s as a backhaul. On one end (the router end of the link) the NSM5 is wired to a PS2 via their secondary ethernet ports. If I put that NS5M in 100Mbps full dup it works fine, but the PS2 it's connected to doesn't offer (via the GUI) the option of forcing the ethernet port speed/duplex so I'm assuming that the PS2 is doing auto-mdx effectively crossing over the TX/RX. On the other end I have the other NSM5 wired (via it's secondary ethernet port) to a BulletM2. If I put both of those into 100Mbps full dup it dies. If only one or the other is forced 100Mbps full dup while the other is auto-negotiate it's fine. With UBNT to UBNT I think it's just the auto-mdx cross over issue. Greg On Jun 5, 2010, at 9:19 PM, Kevin Sullivan wrote: Actually, I've been running into a very similar issue. We have a customer who has a Nanobridge M5 plugged into a Cisco router. It mostly doesn't work with auto negotiation, (90+% packet loss), and it doesn't work at all on 100mbps full forced. It workes great at 10full forced on both ends, but obviously at lower speeds. We just hooked up a temp customer who also had a Cisco router, and had exactly the same deal, except they were into a Rocket M5. We wound up putting a switch between the Cisco and the Rocket to be able to talk at 100mbps. I'm starting to wonder if the forced 100full setting is broken. Kevin - Original Message - From: Robert West robert.w...@just-micro.com To: 'WISPA General List' wireless@wispa.org Sent: Saturday, June 05, 2010 5:04 PM Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernetwhen forced to 100Mbps full duplex If need be, since you have low supply of connectors, if you have any bad patch cables, cut, cross the tx/rx and splice it just to test. Any true wire geek never throws bad patch away. :) Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Greg Ihnen Sent: Saturday, June 05, 2010 7:22 PM To: WISPA General List Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex
Good idea! I have some cables with the connector tab broken. I'll hack one tomorrow and see what happens. Greg On Jun 5, 2010, at 7:34 PM, Robert West wrote: If need be, since you have low supply of connectors, if you have any bad patch cables, cut, cross the tx/rx and splice it just to test. Any true wire geek never throws bad patch away. :) Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Greg Ihnen Sent: Saturday, June 05, 2010 7:22 PM To: WISPA General List Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnen os10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth1 Settings for eth1: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available XM.v5.2# ethtool eth2 Settings for eth2: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link status: No such device No data available On Jun 5, 2010, at 1:50 PM, Michael Baird wrote: They are linux based. Use ethtoolinterface Regards Michael Baird I have a BulletM2 and a NanostationM5 back to back (the bullet's ethernet port is connected to the NanostationM5's secondary port. The NanostationM5 is doing POE pass through and powering the BulletM2. The NanostationM5 the BulletM2 is connected to is the far end of a pair of NanostationM5's acting as a backhaul. I've had some intermittent problems on the network and I wanted to rule out a flaky ethernet cable or connection so I decided to disable auto negotiate on the ethernet port and to force 100Mbps full duplex to see if the problem could be exacerbated to help locate it. When I force the BulletM2 and NanostationM5 to 100Mbps full duplex connectivity between them is lost. I thought good, I've got a bad cable so I replaced the cable. Still no good. Tried another. Still no good. The units are close together and connected together with a 6' cable. After trying various cables I still can't get forced 100Mbps full duplex to work. With 100Mbps full dup forced there is no connectivity, not even ping. If I revert to auto negotiate they connect fine. I'm assuming they are connecting at 100Mbps and probably full duplex because if I run a speed test from the BulletM2 to the far NanostationM5 (data path is from the
Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernetwhen forced to 100Mbps full duplex
Cisco's are finiky Keep in mind that if you are going to force the Ubnt Radio to 100Full.. then you should be doing the same to the Cisco as well. Having said that, I will share a recent experience.. We have qty 3 runs of outdoor shielded cable run done within flexible conduit, inside a building between it's North Telco Room and the South Telco Room about a 100 ft length. On one of the cables going to a Linksys/Cisco POE Switch... and a NBM5... were getting CRC errors on any combination of duplex setting except when running 10meg full duplex. Redid the cable connectors a couple of times still no change... Replaced the cable with the spare run (1 of 3) cables... No More CRC Errors. Go Figure Moral of the story Strange things happen... rare but they do happen... Regards Faisal Imtiaz Snappy Internet Telecom 7266 SW 48 Street Miami, Fl 33155 Tel: 305 663 5518 x 232 Helpdesk: 305 663 5518 option 2 Email: supp...@snappydsl.net On 6/5/2010 9:49 PM, Kevin Sullivan wrote: Actually, I've been running into a very similar issue. We have a customer who has a Nanobridge M5 plugged into a Cisco router. It mostly doesn't work with auto negotiation, (90+% packet loss), and it doesn't work at all on 100mbps full forced. It workes great at 10full forced on both ends, but obviously at lower speeds. We just hooked up a temp customer who also had a Cisco router, and had exactly the same deal, except they were into a Rocket M5. We wound up putting a switch between the Cisco and the Rocket to be able to talk at 100mbps. I'm starting to wonder if the forced 100full setting is broken. Kevin - Original Message - From: Robert Westrobert.w...@just-micro.com To: 'WISPA General List'wireless@wispa.org Sent: Saturday, June 05, 2010 5:04 PM Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernetwhen forced to 100Mbps full duplex If need be, since you have low supply of connectors, if you have any bad patch cables, cut, cross the tx/rx and splice it just to test. Any true wire geek never throws bad patch away. :) Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Greg Ihnen Sent: Saturday, June 05, 2010 7:22 PM To: WISPA General List Subject: Re: [WISPA] BulletM2 and NanostationM5 won't talk on ethernet when forced to 100Mbps full duplex I'm going to try that when I find one. I have one here somewhere but haven't found it yet. I could make one but I don't have many RJ45s and since I'm in the jungle I don't want to blow them on something that's not a necessity. I do believe if I had the cross over cable then I could force the speed and duplex if I wanted to. I was doing it more as a diagnostic tool (I don't have a cable tester). But it does seem like the problem I was having was just a loose connection as having reseated them seems to have fixed the problem. I've been running an extended ping session from one end of the network to the other (I'm up to over 2300 packets) and still not one lost. Greg On Jun 5, 2010, at 6:44 PM, RickG wrote: Did a crossover cable fix it? http://ubnt.com/forum/showthread.php?t=18882 On Sat, Jun 5, 2010 at 5:56 PM, Greg Ihnenos10ru...@gmail.com wrote: Actually no. Turns out that's the port that has nothing else but the POE injector connected. The search goes on. Greg On Jun 5, 2010, at 4:27 PM, Michael Baird wrote: Sounds like you found the issue. Regards Michael Baird I started using ethtool and backing up through the chain of gear back to the router. At one box I'm getting this. Instead of a speed it's saying Unknown!(0). and it's only negotiated half duplex. XM.v5.2# ethtool eth0_real Settings for eth0_real: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: MII PHYAD: 4 Transceiver: internal Auto-negotiation: on Current message level: 0x (0) Link detected: no On Jun 5, 2010, at 4:00 PM, Michael Baird wrote: Try ifconfig first, Ubiquiti doesn't call their interfaces eth0 and eth1, they call them eth0_real and eth1_real. Regards Michael Baird I read a bit about ethtool and then gave it a shot but this was all I got. I iterated through eth0 through eth12 and got nothing. XM.v5.2# ethtool eth0 Settings for eth0: Cannot get device settings: No such device Cannot get wake-on-lan settings: No such device Cannot get message level: No such device Cannot get link
