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

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] Baicells - who's deployed it?

Azure is far from reliable. On Jun 19, 2016 11:03 AM, "Adair Winter" wrote: > No, just authentication. Or at least that's the way it should be. > They are hosting in azure and are supposed to have some good redundancy . > > On Sun, Jun 19, 2016 at 12:01 PM,

Re: [WISPA] Resends of TowerCoverage Website Submissions

I've been telling Jim the same thing for a long time. You've worded it better than me. Their UI/UX needs some serious outside help, but while they claim to be open to suggestions, they won't hire the help, or maybe they just don't understand the difference they'd achieve with a quality user

Re: [WISPA] Static IP Pricing

Typical cost is around $1-2/IP/Month with various fiber providers. I've been planning to charge something like $10-20/IP/Mo for commercial in order to only sell to people who really need it. On Wed, Feb 1, 2017 at 7:22 PM, Colton Conor wrote: > How much do you charge

Re: [WISPA] 60 Ghz gear

Make sure your mcs rate is set to auto, not locked at one speed. Judd On Aug 30, 2016 3:23 PM, "Dan Parrish" wrote: > Yeah, in a PTP situation, we get more than 500mbits/sec on the workbench. > Replace one end with the "AP" and we get 25-30mbits/sec. I've adjusted the >

Re: [WISPA] Switch causing packet loss?

hen TCP v1 was written, but the team had turned over >>>> by 1978 when TCP/IPv4 came out, and that group forgot about it until 1986 >>>> when things fell apart. The temporary short-term not very good fix was in >>>> layer 4 (TCP Slow Start) and that doesn'

Re: [WISPA] Switch causing packet loss?

So you're saying, make sure Flow Control is enabled on the ports? On Mon, Nov 7, 2016 at 8:22 AM, Josh Reynolds wrote: > Microbursts causing buffer drops on egress ports to non-10G capable > destinations. The switch wants to send data at a rate faster than the 1G > devices

Re: [WISPA] Switch causing packet loss?

part of every layer. Loss should > generally be localized. > > On Nov 7, 2016 9:36 AM, "Judd Dare" <judd.d...@gmail.com> wrote: > >> So you're saying, make sure Flow Control is enabled on the ports? >> >> On Mon, Nov 7, 2016 at 8:22 AM, Josh Reynolds

Re: [WISPA] Prayers for Mac Dearman

You're in our thoughts and prayers Mac. You know that you've been a great help to many of us over the years, don't hesitate to ask if there is anything at all we can do to help. Judd On Apr 17, 2017 10:57 AM, "John Scrivner" wrote: > I am certain he does not want any big

Re: [WISPA] If you can service any of these hit me off list

Sorry it looks like I replied to everyone. I meant for that follow-up to go direct to Scott. ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless

Re: [WISPA] If you can service any of these hit me off list

Scott did you find what you needed for these locations? I have an MSA with Comcast. We can deliver fiber to many metro areas with SLA. I'd be happy to see what areas we could deliver and at what cost. If you're interested, get me a list of addresses and I'll get my guy on it ASAP. Judd Dare

Re: [WISPA] Test

Reply On Aug 26, 2017 12:11 AM, wrote: Test ___ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless ___ Wireless mailing list Wireless@wispa.org