IPWhiteListing: Access from a different IP possible even tho that IP is not in the IPWhiteList

[Goran_Iliev]

I set the ipwhitelist to the wowza streaming engine server ip, which is for example 192.168.2.2.
If i try to connect to manager on the same system, i can connect to the GUI. That is good.
But if I try to access the GUI (Manager) on a computer from a different subnet (subnet routing is done) it is also possible, even though i did not put the ip of this new computer in the whitelist? but i do specify the ip 192.168.2.2 under wowza streaming engine url on the new computer while trying to access. I am not sure if it is a right behaviour or not, since IPWhiteList should be checking if the access request is comming from one of the defined IPs right?

PS: On the remote client, i did not install wowza Streaming Engine Manager. I am just opeing a browser and then give the http://192.168.2.2:8088/enginemanager/ url then give the credentials and under "wowza streaming engine url "

[Karel_Boek]

If you set the IP address in /conf/Server.xml under /Root/Server/RESTInterface/IPWhiteList then you may be able to open the login page from the other computer, but when you try to login you should get an error, because the front-end is loading but the connection to the REST API should be blocked.