Forum Discussion
Solved
Connecting Ubiquiti Litebeam link to Network Access Hub
Hi all, We are replacing our old ZTE cell modem with a new fibre connection using the Network Access hub. We currently have a Ubiquiti Litebeam AC5 link radio to our remote building for internet acc...
The WAN static IP on the router would likely have been the problem. The NH20 has a default subnet of 192.168.1.x. If you haven't changed that subnet on the NH20, either manually reserve a static IP for that router on the NH20, or change the WAN IP on the router itself manually and reboot everything.
The NH20 will not be able to assign any IPs to devices if you have a router on the far end as that router would be assigning IPs itself. Only exception would be if you have the router in bridged mode or as an access point only so that DHCP would be handled by the NH20.
Thanks for the help.
As mentioned the litebeam has been working as is for 2 years with the ZTE279 cell modem, it provides a radio link to the flying field club house router which has a WAN static IP of 192.168.0.105, which is the IP I saw on the NH20 connection list. We have 4 cameras and a weather station at the club house. Today I switched the club house router back to Dynamic IP for the WAN and it made no difference. Litebeams are setup in bridge mode.
It's entirely possible I don't understand how the NH20 behaves, it's a modem and a router, so shouldn't it assign an IP for each connected device out of the IP pool? I plugged the litebeam back into the cell modem for now until I can get back there tomorrow to try other things. It came right back up and works, it's just painfully slow as we only have LTE here and about 40 users. The radio link is about 600 meters and is around 350Mbps.
Any other thoughts?
Cheers
Nighthawk
Community Power User
Community Power UserThe WAN static IP on the router would likely have been the problem. The NH20 has a default subnet of 192.168.1.x. If you haven't changed that subnet on the NH20, either manually reserve a static IP for that router on the NH20, or change the WAN IP on the router itself manually and reboot everything.
The NH20 will not be able to assign any IPs to devices if you have a router on the far end as that router would be assigning IPs itself. Only exception would be if you have the router in bridged mode or as an access point only so that DHCP would be handled by the NH20.
Thanks Nighthawk! We have a winner.
I had changed the subnet in the NH20 to 192.168.0.x so I wouldn't have to change things at the remote site. What finally did it was to change the remote router WAN to Dynamic IP, and then ultimately, when it powered down last night (solar site) and rebooted this morning, it came back up, was assigned an IP and is working 100%. Amazingly fast. I can stream all 4 Reolink cameras at the highest res and framerate and it's completley smooth.
Thank you so much everyone for your help, much apprciated.
Cheers!
