These 2 SSIDs are not routed to our company network in any way. We have 2 wireless routers/controllers for high availability, our corporate network SSIDs provide DHCP from our internal DHCP server; but, both guest wireless SSIDs use the controllers for the DHCP server. The only problem is that
Controller 1 has 1/2 of each individual DHCP scope and it has the default gateway of 102.1 and 103.1
Controller 2 has the other 1/2 of each individual scope and it has the default gateway of 102.127 and 103.127.
The Wireless Guest Lans work great and they have no connection to the corporate network; but, I noticed that if either controller is off-line the guest users must do an ipconfig /release to clear out the IP settings (default gateway for that SSSID in order to receive the correct IP settings from the other controller (Controller 2). Hence the guest access is not a seamless fail-over process. If you are connected to a controller 2 ( a unique gateway IP address) and already have controller 1's Default gateway ip address cacahed in memory … you will not be able to connect to the internet from controller 2 until you perform an ipconfig /release.
Is there a better way to design the Guest Wifi Access for these 2 x GUest SSID's? Currenlty we have 1 older WiFi Controller in production; but, it was thought to have 2 controllers for the new setup and provide High Availability. The current WiFi setup doe snot have this DHCP design problem.
Any Ideas for a better design and easier guest access transition to truly benefit from H.A.? The corporate networks are unaffected because their network ip addresses are originating from our corporate network and not from the Wireless controllers
8/22/2022 - Mon
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.