Yep, what Matt said... that setting will more than likely fix it. On Thu, Nov 2, 2017 at 7:36 PM, Matt Hoppes < mattli...@rivervalleyinternet.net> wrote:
> It's the input cable that's the issue. > > It's stupid. > > > /interface ethernet poe settings set ether1-poe-in-long-cable=yes > > On Nov 2, 2017, at 20:07, Jason McKemie <j.mcke...@veloxinetbroadband.com> > wrote: > > That is a royal pain if I went through all of that for a setting. The > strange thing is that the output port is the short cable at about 3', the > input is about 80'. > > On Thursday, November 2, 2017, Matt Hoppes <mattlists@ > rivervalleyinternet.net> wrote: > >> There's some setting somewhere about long distance PoE short detection >> that needs to be turned off. Royal pain. >> >> > On Nov 2, 2017, at 19:09, Jason McKemie <j.mckemie@veloxinetbroadband. >> com> wrote: >> > >> > I've got a powerbox causing me grief. It works fine powering a Baicells >> CPE on the bench, but when I put it in place with 80' of cable between it >> and the power supply I get a short circuit message when trying to power up >> the Baicells. I've tried a new jumper between the powerbox and the >> Baicells, new ends on the main run going to the powerbox, and a different >> power supply - all to no avail. Am I really past the distance limit? If so, >> WTF Mikrotik? >> >
