Re: [WISPA] Any IgniteNet MetroLinq customers out there

Try a different power brick. On Jun 20, 2016 9:47 PM, "Chadwick Wachs" wrote: > One end is brick (the end that is having issues) and the other end is off > a Netonix. > > On Mon, Jun 20, 2016 at 9:37 PM, Chris Ruschmann > wrote: > >> How are you

Re: [WISPA] Any IgniteNet MetroLinq customers out there

Almost sounds like a low voltage issue or faulty boards internally. On Jun 20, 2016 10:48 AM, "Chadwick Wachs" wrote: > Update to all on this. We are running MCS1, the latest public firmware > and contacted Ignite support. They are responsive. We did get the 60 GHz >

Re: [WISPA] Any IgniteNet MetroLinq customers out there

One end is brick (the end that is having issues) and the other end is off a Netonix. On Mon, Jun 20, 2016 at 9:37 PM, Chris Ruschmann wrote: > How are you powering them? Power brick or switch? > On Jun 20, 2016 7:35 PM, "Faisal Imtiaz" wrote: > >

Re: [WISPA] Any IgniteNet MetroLinq customers out there

ours are typically powered by either the brick or a Netonix switch Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net > From: "Chris Ruschmann" > To:

Re: [WISPA] Any IgniteNet MetroLinq customers out there

How are you powering them? Power brick or switch? On Jun 20, 2016 7:35 PM, "Faisal Imtiaz" wrote: Are there the only two radios you have ? maybe there is a physical hardware issue with one of the radios.. we have seen something similar with on another link we were

Re: [WISPA] Any IgniteNet MetroLinq customers out there

Are there the only two radios you have ? maybe there is a physical hardware issue with one of the radios.. we have seen something similar with on another link we were working on for another WISP. No conclusions yet, but one radio is definitely doing hokey stuff...They have spares, will be

Re: [WISPA] Any IgniteNet MetroLinq customers out there

Update to all on this. We are running MCS1, the latest public firmware and contacted Ignite support. They are responsive. We did get the 60 GHz radios to link up once - for about 30 minutes. Then, the 60 GHz radio on the client end died. Can't open the 60 GHz aiming tool and the dashboard acts

Re: [WISPA] Any IgniteNet MetroLinq customers out there

Aiming takes patience, the scopes aren't perfect but a huge help. We found that turning off auto MCS and using fixed lower rate helped a lot. Make sure you have the newest firmware, I believe there are more updates coming out soon as well. IgniteNet support was responsive and very helpful when

Re: [WISPA] Baicells - who's deployed it?

On 6/19/2016 10:09 PM, Nathan Anderson wrote: > I believe that Patrick has said as much (not SDR) on the ISP Radio interview > with him back in April. Would certainly go a ways to explaining how they > managed to offer it for basically 1/3rd the price of competing gear. I only know what's

Re: [WISPA] Baicells - who's deployed it?

On the Baicells you can (They can at this point) repoint your gateway and it will start using the Telrad core for customer traffic. So... if I change the Baicells eNB MNS setting to the Telrad core then it will send Auth SIM card data to Telrad core, but all customer traffic still goes out the

Re: [WISPA] Baicells - who's deployed it?

The Baicells UE has a 1500 MTU as its default. Older versions of the Telrad firmware did not support 1500, but I was told the newest versions will. New versions needed for eNB, EPC, and UE to support 1500MTU. One of our customers is having an issue with his VPN. On the UBNT 5Ghz network he had

Re: [WISPA] Slightly OT: punching holes in stainless steel enclosures

http://www.tractorsupply.com/tsc/product/tractor-supply-co-underbed-truck-box-36-in-black?cm_vc=-10005 Sent from my Verizon Wireless 4G LTE DROID George Rogato wrote: >___ >Wireless mailing list >Wireless@wispa.org