topic Re: Web auth AP based restriction in Network Access Control

Web auth AP based restriction

annen — Sun, 15 Apr 2018 15:20:03 GMT

Hello team

We have a hotel customer and they want to install 1815W APs in every room (WLC will be 5520). In addition to this, they want the guests to be able to connect to their own AP in their own room only, using web auth. So the guests in room 101 will connect to AP101, guests in room 102 will connect to AP102 and so on. How can this be accomplished?

Thanks

Re: Web auth AP based restriction

hslai — Sun, 15 Apr 2018 22:57:50 GMT

One possibility is to set Called Station ID Type to "AP Name:SSID".

Then, set either an existing attribute or a custom attribute to AP Name. For example,

If Radius:Called-Station-ID Starts With Guest:OptionalData1 ...

Re: Web auth AP based restriction

Jason Kunst — Mon, 16 Apr 2018 00:22:36 GMT

I believe there might be a bug associating optional data in an authorization rule match

Re: Web auth AP based restriction

annen — Mon, 16 Apr 2018 10:23:32 GMT

Thanks. But all the APs will be broadcasting the sames SSID. Will it work in that case too?

Regards

Re: Web auth AP based restriction

hslai — Mon, 16 Apr 2018 14:29:53 GMT

That would not be an issue.

However, care needs to be taken to tune the wireless radios, shielding, and interferences so that the room would receive considerably weak signals from the APs from other rooms. Please consult the wireless team for such support, if needed.

Re: Web auth AP based restriction

Craig Hyps — Tue, 17 Apr 2018 04:01:23 GMT

May be related to

CSCuv42389

New custom fields not showing up under authz policy attributes

If not working, I recall one SE handled via workaround: "I could still use ‘OptionalData1’ which is visible in the Guest attribute list, by creating a custom Guest field with the same name, which allows me to work around the problem."