nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How I can make clients connected to this WLAN can not access the configuration ZoneDirector and APs?

unknown

I have a ZoneDirector with the following settings: type Standard Usage, Open Authentication and WPA2/AES encriytion options.

How I can make clients connected to this WLAN can not access the configuration ZoneDirector and APs?

Find more posts tagged with

Accepted answers

All comments

keith_redfield

Hi Francisco,

When you initially configured the ZoneDirector, one of the first things it requires is that you set a login password for the admin account. Unless you've given that password to your users, they will not have any access to the ZD administrative functions. The connected AP's inherit the same login credentials and so are similarly protected.

Did I mis-understand your question?

unknown

I meant how to make customers can not access the entry screen APs and ZoneDirector so they can not prove passwords. Ie access to the ips of the access points and the zone are refused or manage the configuration part is on another network.

unknown

In ZD gui have a look at

configure

system

management access control

Image_ images_messages_5f91c40b135b77e247933ba7_19fc6ab347bcd82e273f7357229b371e_restrictIPs_inline-a1f15c0a-1e29-4a14-8a7a-50fdafb2bd53-282160574.jpg1397043798

Image_ images_messages_5f91c40b135b77e247933ba7_19fc6ab347bcd82e273f7357229b371e_restrictIPs_inline-a1f15c0a-1e29-4a14-8a7a-50fdafb2bd53-282160574.jpg1397043798

You could lock it down very precisely (but be careful you allow yourself access)!

unknown

Thanks for the reply

with this configuration block access to the zone director but how blocking access to the access points?

unknown

Slightly off the wall suggestion: Using different subnet for APs from rest of your network.

Use ZD DHCP option and specify seperate IP subnet so that the clients get IPs on different address range from APs.

Seems a bit hammer to crack nut plus possible side-effects depending your specific environment. Needs thinking through before doing.

Bigger brains than mine might be able to suggest a neater workaround.

Failing that make sure your ZD password is very secure (which it should be anyway). Reiterating Keiths' first suggestion.

unknown

ok thanks