Bridging with AP170 discovery

  • 1
  • Idea
  • Updated 8 months ago
  • (Edited)
Not sure if anyone else found this but we have had this scenario happen twice. Apparently one of the gotchas in bridging is that both sides of the bridge must be in the same IP range. 

- This school had run out of IPs and elected to create a Superscope instead of expanding the network from a /23 to something else. 
- During a reboot of both sides of the bridge, the bridge was lost.
- Portal AP came up with a 10.1.x.x/23 IP
- "sh hive <hive name> neighbor" said it could see the bridge but would "Conn-time" reset after 180 seconds
- "sh lldp neighbor" said it saw the Mesh Point but with a 10.3.x.x/23 IP
- The 10.1.x.x/23 and 10.3.x.x/23 networks were part of the Superscope and defined as Secondary networks in the router.
- The two networks are pingable from each other

Our "fix" was to reboot the Portal AP until it grabbed an IP from the 10.3.x.x/23 network. Ran the "sh hive" command and then it finally made it past 180 seconds. We then set the IP address on the two AP170's.

So the takeaway is this. Don't use DHCP on bridges.
Photo of Robert Haviland

Robert Haviland

  • 3 Posts
  • 0 Reply Likes

Posted 8 months ago

  • 1

There are no replies.