We've utilized this method for 4 years in our school district. Once you authenticate to the portal, you could travel to any of our subnets or "venues" on campus and stay connected without issue or stay connected for 10 days until the authentication expired. It's been working fine with little to no problems, other than user errors.
Beginning this past Monday, if you disconnect from the network, travel between subnets/venues, or leave the campus and come back the next day, you have to authenticate again..each and every time you connect to the network again no matter the situation... same subnet/venue... different one.. doesn't matter.
1st Tier Ruckus email support says "that is by design and the way captive portal is supposed to work" even though we've explained it's been working NOT that way for 4 years. Anyone else see any issues like this begin lately? We are running R610 units on the bulk of our campus and R750 on another connected campus. The entire network has the issue that just started. No recent firmware upgrades. No changes to the network except for some AD DNS replication fixes recently.
