# Security zone with IP addresses **URL:** \ **Category:** Ignition\ **Tags:** ignition81, security\ **Created:** [March 7, 2022, 11:00am UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899 "2022-03-07T11:00:53Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![marcos.bartolome](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcos.bartolome/32/58225_2.png) [@marcos.bartolome](https://forum.inductiveautomation.com/u/marcos.bartolome)\ **Post date:** [March 7, 2022, 11:00am UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/1 "2022-03-07T11:00:53Z")
Hello, I trying to create a security zone to prevent access to perspective from outside of a specific IP range. (192.168._._) I’ve created the security zone and I’ve configurated the project properties to restrict access to user outside this zone. I’ve tried configuring the IP addresses of the security zone in different ways and I can’t get it to work: IP Addresses: 192.168._._ IP Addresses: 192.168.0-255.0-255 I have even tried: _._._._ or from the localhost: 127.0.0.1 …and none of this works, it always forbids me access. I have only managed to access the perspective with the security zone actived, if I fill the IP Addressing with a single \* This is an example of the configurations I have tried: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/4/4432e36aabd4034b9161733e654b078647148a33.png) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 7, 2022, 11:40am UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/2 "2022-03-07T11:40:19Z")
In your Perspective client, what is the value of `session.props.host`? This is what is used for the IP address filtering. This is for 8.1.5 at least, I have a feeling it's changed in later versions as I think hostnames are actually supported now with reverse DNS. This is what I was talking about, 8.1.10 (8.1.9 was canned) > [@Perspective - Scripting - Get Computer name and IP of client](https://forum.inductiveautomation.com/t/perspective-scripting-get-computer-name-and-ip-of-client/49626/5): > > In 8.1.9 you’ll be able to opt-in to a setting on the gateway that has the gateway do a reverse DNS lookup to attempt to verify the hostname based on the provided IP: “When enabled, Ignition’s web server will attempt to resolve the remote HTTP client’s hostname by performing a reverse DNS lookup using the remote HTTP client’s IP address where appropriate, which could have a performance impact for each request which attempts a hostname lookup. When disabled, Ignition’s web server will not attem… ---
**Author:** ![marcos.bartolome](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcos.bartolome/32/58225_2.png) [@marcos.bartolome](https://forum.inductiveautomation.com/u/marcos.bartolome)\ **Post date:** [March 7, 2022, 12:08pm UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/3 "2022-03-07T12:08:51Z")
if I print {[System]Client/Network/IPAddress} on my client and I get the address 192.168.200.1 The client public IP is 147.161.191.94 (I don’t know if you mean this IP) I tried 147.161.191.94, 147.161._._ and 147.161._._ on IP addresses but it still doesn’t work. (I’m using igntion 8.1.14) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 7, 2022, 12:12pm UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/4 "2022-03-07T12:12:51Z")
> [@nminchin](#): > > In your Perspective client, what is the value of `session.props.host` ? Yes, but what is the value of `session.props.host`? and have you tried adding 192.168.200.1 into the IP Address Identifiers list in Security Zones? ---
**Author:** ![marcos.bartolome](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcos.bartolome/32/58225_2.png) [@marcos.bartolome](https://forum.inductiveautomation.com/u/marcos.bartolome)\ **Post date:** [March 7, 2022, 12:47pm UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/5 "2022-03-07T12:47:44Z")
> [@nminchin](#): > > 192.168.200.1 Yes, I tried 192.168.200.1 the session.props.host in the designer says: 127.0.0.1 but if I print {session.props.host} on the client, it prints: [0:0:0:0:0:0:0:1] ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 7, 2022, 12:49pm UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/6 "2022-03-07T12:49:43Z")
You might need to launch the client using the ip address of your gateway (in this case it looks like your PC) and not the loopback address (i.e. localhost or 127.0.0.1) E.g. [http://192.168.200.1:8088](http://192.168.200.1:8088) ---
**Author:** ![marcos.bartolome](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcos.bartolome/32/58225_2.png) [@marcos.bartolome](https://forum.inductiveautomation.com/u/marcos.bartolome)\ **Post date:** [March 7, 2022, 3:28pm UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/7 "2022-03-07T15:28:13Z")
That is, if I launch it from that address instead of localhost it works. I have set the IP address as 192.168.\*. \* @nminchin, thank you very much for your time, I appreciate it. ---
**Author:** ![pettis.nicholas81334](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@pettis.nicholas81334](https://forum.inductiveautomation.com/u/pettis.nicholas81334)\ **Post date:** [March 21, 2025, 9:50am UTC](https://forum.inductiveautomation.com/t/security-zone-with-ip-addresses/56899/8 "2025-03-21T09:50:50Z")
you can use subnet masks to cover a range of ip addresses instead of listing each one separetely. Also, chekc for overlapping security zones that might be affecting access