F5F Stay Refreshed Power Users Networks UBNT radios are assigned a 169.x.x.x. IP address.

UBNT radios are assigned a 169.x.x.x. IP address.

UBNT radios are assigned a 169.x.x.x. IP address.

C
Cy__
Junior Member
Find
8
12-28-2023, 02:31 AM
#1
I've got Ubuntu radios (PowerBeams or Litebeams) with static IPs at 192.168.85.253. They appear as 169.x.x.x in the discovery tool, which is outside the DHCP range. Check what's causing this mismatch and how to resolve it.
Reply
Reply
C
Cy__
12-28-2023, 02:31 AM #1

I've got Ubuntu radios (PowerBeams or Litebeams) with static IPs at 192.168.85.253. They appear as 169.x.x.x in the discovery tool, which is outside the DHCP range. Check what's causing this mismatch and how to resolve it.

Reply
Reply
K
kcaz56
Senior Member
Find
664
12-28-2023, 12:36 PM
#2
Lack sufficient details. Confirm if devices are linked via a wireless network. Check if they operate in bridge or router mode. Determine whether you're using the discovery tool from the LAN side or the Wi-Fi side. Test manually by entering IP addresses.
Reply
Reply
K
kcaz56
12-28-2023, 12:36 PM #2

Lack sufficient details. Confirm if devices are linked via a wireless network. Check if they operate in bridge or router mode. Determine whether you're using the discovery tool from the LAN side or the Wi-Fi side. Test manually by entering IP addresses.

Reply
Reply
B
Back2Blaze
Member
Find
204
12-28-2023, 03:53 PM
#3
They form a local network connecting multiple buildings. I’m leveraging the discovery tool on the LAN side. The mention of entering IP addresses manually seems unclear. I can reach them via a web browser using the 169 address.
Reply
Reply
B
Back2Blaze
12-28-2023, 03:53 PM #3

They form a local network connecting multiple buildings. I’m leveraging the discovery tool on the LAN side. The mention of entering IP addresses manually seems unclear. I can reach them via a web browser using the 169 address.

Reply
Reply
X
xBoomBeach
Member
Find
191
12-28-2023, 08:36 PM
#4
The system shows 169, indicating DHCP isn’t assigning an IP address. It might mean the static configuration wasn’t saved or you changed the device to bridge mode, which resets the IP settings.
Reply
Reply
X
xBoomBeach
12-28-2023, 08:36 PM #4

The system shows 169, indicating DHCP isn’t assigning an IP address. It might mean the static configuration wasn’t saved or you changed the device to bridge mode, which resets the IP settings.

Reply
Reply
D
DiamondXX101
Member
Find
108
12-28-2023, 08:58 PM
#5
Verify your DHCP settings and ensure DHCP traffic is permitted in any firewall connecting DHCP and AP networks. The range 169.254.*.* is reserved, indicating the device cannot secure a DHCP lease.
Reply
Reply
D
DiamondXX101
12-28-2023, 08:58 PM #5

Verify your DHCP settings and ensure DHCP traffic is permitted in any firewall connecting DHCP and AP networks. The range 169.254.*.* is reserved, indicating the device cannot secure a DHCP lease.

Reply
Reply
S
ShadowSpartan
Junior Member
Find
31
12-29-2023, 07:10 PM
#6
You're encountering an APIPA issue... Review your DHCP settings. If other devices are getting valid DHCP IP addresses, attempt to assign a static IP on the affected device within the same subnet while excluding that IP from the DHCP server.
Reply
Reply
S
ShadowSpartan
12-29-2023, 07:10 PM #6

You're encountering an APIPA issue... Review your DHCP settings. If other devices are getting valid DHCP IP addresses, attempt to assign a static IP on the affected device within the same subnet while excluding that IP from the DHCP server.

Reply
Reply