Also why not lay a cable.
Also why not lay a cable.
I don’t think so. I definitely know tech people who get a particular idea in their head and will debug it to hell and back before taking a step back and realizing the obvious thing they missed. I’ve definitely done it before myself.
> Also why not lay a cable.
It sounds like they were trying to run a network between two properties that weren’t adjacent. They may not have had permission from the neighbor in the middle to lay cable on their property, or it might’ve required laying a cable across a street.
Past ~300ft/100m, you need a repeater even for Ethernet. We would have needed at least one repeater somewhere along the line, which adds even more cost and complexity on top of needing to get permits from the city and approvals from all the neighbors in between. Anyone that says "just go get a permit from the city" has never tried doing it.
Edit: it probably did as the story is 10 years old.
Other than that I'd agree about your solution being optimal back then, and now. Btw how did you check the power brick, peak to peak voltage measurements? Bad capacitors is likely the single most common failure.
Also, if it was roughly 10 years ago then upgrading to N wireless was a good solution anyway. Not only did it solve the problem but it would've given then quicker speeds.
According to the stories the two bridge endpoints were in different buildings a few blocks apart. You can't just lay a cable in the middle of a public street.
"Just" move it higher vs replace ~10yr old (at the time) equipment with newer, faster equipment that doesn't have the problem? Easy answer if you ask me, and I'd make the same choice again with ~10yrs of retrospect -- the same 802.11n antennas are still there today!