AP 1 - connected to Switch 1. AP1 is powered via PoE++. (STP is enabled)
AP 2 - connected to Switch 2. AP2 is powered via powered adapter. (STP is enabled)
Switch 1 is connected to Switch 2. (STP is enabled)
Router - DHCP server is connected to Switch 1.
Occasionally, the network cable for AP2 is disconnected, for whatever reason may be. I need to still be able to connect to the network via AP2. So, I enabled the Wireless Bridge feature between AP1 and AP2 and was able to maintain connectivity to the network.
But, then a few hours later, I'm able to reconnect the ethernet cable to AP2, so then, the bridge connection becomes redundant.
Is it okay to maintain this setup? ( AP1 connected to Switch 1, AP2 connected to Switch 2), and the Wireless Bridge between AP1-AP2. I know things are working, as I have STP enabled on all four devices. The only drawback is that the APs need to decide which they'd be using to send traffic - either via the LAN or the Wireless bridge, so a bit of a delay.)
What's a better approach to add redudancy or cater to maintaining connectivity despite AP2 losing its ethernet connection at times.
Thank you for your thoughts. Standard practices is the way to go! Until I can sort out a permenant switch-port for that AP2, I've simply disabled the Wireless bridge from AP1. As and when the need arises that AP2s' ethernet cable is disconnected, I'll re-enable the Wireless bridge from AP1.
Usually, the ethernet cable disconnection from AP2 happens to sort out that things that arise, and a couple of days later I'd be able to re-connect it. I'll add a note on the cable to remind myself to enable the bridge on AP1. The bridge configuration exists and will remain in-active on AP2. So whenver AP1 is enabled - the bridge will come alive.
Maintaining an active wireless bridge between AP1 and AP2, even when AP2's Ethernet is connected, can work due to STP preventing loops, but it's not ideal due to potential delays in path selection, less efficient routing, increased complexity, and wireless resource usage. Better redundancy approaches include Link Aggregation (if switches support), dual Ethernet ports on AP2 with failover, managed switches with monitoring, addressing the root cause of disconnections, or a secondary wired connection for AP2. Prioritize wired redundancy solutions for seamless failover and better performance over relying on a continuous wireless bridge.
Thank you for your thoughts. Standard practices is the way to go! Until I can sort out a permenant switch-port for that AP2, I've simply disabled the Wireless bridge from AP1. As and when the need arises that AP2s' ethernet cable is disconnected, I'll re-enable the Wireless bridge from AP1.
Usually, the ethernet cable disconnection from AP2 happens to sort out that things that arise, and a couple of days later I'd be able to re-connect it. I'll add a note on the cable to remind myself to enable the bridge on AP1. The bridge configuration exists and will remain in-active on AP2. So whenver AP1 is enabled - the bridge will come alive.
