Point to Point Wireless Bridge Recomendations

And the documentation is silent both on what type of POE comes out the passthrough port, and what the maximum passthrough power is. One guy on the Ubiquiti forums says:
I bought a pair of the NS-5AC units and another LPR camera, for experimentation in my house, before I approach my industrial neighbor for cooperation to deploy. First impressions:
  1. Units unbox with a static IP address of 192.168.1.20.
    1. Why are manufacturers so allergic to DHCP for networking infrastructure products?
    2. As with the PLAs I played with last week, plugging into two of these guarantees an IP address conflict, right away.
    3. These NS-5AC units are supposed to boot up with a "management WiFi" network, but I prefer to configure them over Ethernet.
  2. I always forget that it's more efficient to set up the remote unit of the pair first, then set up the LAN side.
    1. But I got them configured for DHCP, plugged them in on opposite sides of my dining table, and powered them up.
    2. The link came up quickly, and the management tools give me pretty good feedback on link quality.
    3. The two units are literally 15' apart, so they're probably way too close for optimal connectivity, but it works and gives me a few hundred Mbps tested throughput via the management tool, and not through iperf, yet.
  3. Once I got the link up I changed the default SSID and WPA2 key (on the remote side first!!!), and enabled POE passthrough.
    1. It took me 30 minutes and a bunch of un/plugging to figure out why the camera didn't work, which was because these NS-5AC units come with 24 V passive POE adapters instead of 802.3af adapters. .
    2. The NS-5AC units put out whatever's put in, and most cameras use 802.3af, so this is a surprising choice given than Ubiquiti specifically advertises this feature for powering IP cameras.
    3. I can't imagine that there's a big difference in cost to Ubiquiti when they sell 802.3af adapters at retail for $8.00.
    4. Fortunately I have bunch of these lying around, so I was able to power up the NS-5AC units on 802.3af and power the camera through the pass-through ports from either unit.
  4. So, with this combination of features I'll be able to use one cable to power the LAN side of the bridge and one camera, and then walk over to my industrial neighbor with a set of stuff ask for permission to plug into AC power, and that'll establish the "B" bridge in my OP.
  5. Now that this works, I ordered a second pair to be my "A" bridge. I'll test first, but I'm hoping that, once the "A" units are paired, I can just connect the "Main" ports between Remote B and LAN A via a long Ethernet cable, and it'll just work.
    1. 1733000952046.png
    2. Or will I need a switch between Remote B and LAN A?
 
LOL. I forgot that this isn't my thread. I'm the Blue Iris server, and I'm trying to enable placement of LPR cameras at these other locations, that I don't control, because my angle to the driveways is all wrong:

1733002073230.png
 
Since this got bumped, to update my post here re the TP-Link CPE210 the one that I was using for the remote end died the other day. Can only keep wireless up for a few minutes after repower then it drops out. Got several years out of it. Finally said F' it and just ran a cable.
 
  • Like
Reactions: TonyR
Since this got bumped, to update my post here re the TP-Link CPE210 the one that I was using for the remote end died the other day. Can only keep wireless up for a few minutes after repower then it drops out. Got several years out of it. Finally said F' it and just ran a cable.
22 months so far on a pair of CPE210's I installed for a client (fingers crossed). :rolleyes:
 
  • Like
Reactions: Mike A.
22 months so far on a pair of CPE210's I installed for a client (fingers crossed). :rolleyes:
My other one's still good so 50/50 shot by my experience. ; ) I think what did mine in for whatever reason was that we had a bunch of real quick power losses/restores over about 5 minutes one day.

Also just FYI, if you ever want to use just one as a client to another AP, it doesn't like an SSID with both 5 and 2.4 on it. Couldn't get it to make a connection. Made a separate one with just 2.4 alone and it hooks right up.
 
  • Like
Reactions: TonyR
My other one's still good so 50/50 shot by my experience. ; ) I think what did mine in for whatever reason was that we had a bunch of real quick power losses/restores over about 5 minutes one day.

Also just FYI, if you ever want to use just one as a client to another AP, it doesn't like an SSID with both 5 and 2.4 on it. Couldn't get it to make a connection. Made a separate one with just 2.4 alone and it hooks right up.
I usually use Ubiquiti but 2 years ago the availability was spotty and when you did find them they were way too much compared to pre-COVID prices so clients wanted to try the TP-LINK units. I've put their Unifi clone overhead as a WAP in a Mexican restaurant 2 years ago and have installed probably 2 dozen of their switches in 5 years, all working great so it wasn't a real risky move. But I did expect a little less from them than the UBNT....I have about 8 UBNT units (4 bridges) in operation since 2015 and not one issue. Another 2 bridges in place for about 2 years then owners moved out and I bought their used units. Since circa 2015 I have had one NSM2 and one NSM5 Loco damaged by firece lightning though.

I just remembered I put in a set of the TP-LINK 5GHz CPE510's between my stepmom's house and her barn/guest house when she got her 300Mbps fiber June of '23. Also "so far, so good." :cool:
 
Here's the test setup in my kitchen/dining area:

1733074697970.png
 
I have three pairs of these NS_5AC working around my yard. One is for my LPR cams at the front of the driveway.
They seem solid, although I do get some momentary dropouts occasionally with one pair.

One pair is fairly new, a few months old. They other two pair have been running for a couple of years now.

If you ever want to do an automated reboot of the unit, you can use Putty Plink program and a simple one line .bat file

plink -batch -ssh <username here>@<IP address of unit here> -pw <password here> "reboot"

I keep a log of the disconnects and when they reach a certain point I reboot the unit.
 
  • Like
Reactions: TheWaterbug