Re: [Telrad] Uplink throughput again

So then we need a read only root account. That would be very helpful. On 02/16/2017 11:58 AM, Jeremy Austin wrote: On Thu, Feb 16, 2017 at 7:58 AM, Adam Moffett > wrote: Is there a way to monitor CPU usage on the EPC?

Re: [Telrad] Uplink throughput again

I think you mean a non-privileged shell account. :) Pedantically yours, -- Nathan From: telrad-boun...@wispa.org [mailto:telrad-boun...@wispa.org] On Behalf Of Hanson Sent: Thursday, February 16, 2017 12:54 PM To: telrad@wispa.org Subject: Re: [Telrad] Uplink throughput again So then we need

Re: [Telrad] Uplink throughput again

Finally, a joke on the Telrad list. On Thu, Feb 16, 2017 at 1:10 PM Nathan Anderson wrote: > I think you mean a non-privileged shell account. :) > > > > Pedantically yours, > > > > -- Nathan > > > > *From:* telrad-boun...@wispa.org [mailto:telrad-boun...@wispa.org] *On >

Re: [Telrad] Ethernet RX FCS errors from BreezeWay?

The cables we were using were 7ft pre-manufactured 5e patch cables. So for grins, I took 10ft of Cat. 6 off of a spool and put my own ends on. 10 minutes later, what happened? FCS ERROR. https://getyarn.io/yarn-clip/0f901d47-7954-40e1-a539-b6cea39d93c0

Re: [Telrad] Ethernet RX FCS errors from BreezeWay?

We went from like 1 meter to 2 meter and from port 5 into port nine on two different EPC's and that did the trick at the locations we were having an issue. -- Justin Davis COO SkyWerx Industries, LLC > On Feb 16, 2017, at 5:54 AM, Nathan Anderson wrote: > > Port 9 was the

Re: [Telrad] Ethernet RX FCS errors from BreezeWay?

Nathan have you used a bit longer cable from EPC to router and use port 9. This fixed our FCS error issue. -- Justin Davis COO SkyWerx Industries, LLC > On Feb 16, 2017, at 5:00 AM, Nathan Anderson wrote: > > So, as an update to this, we are still seeing these FCS errors