No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Issues while setting up the Whitelist feature

Publication Date:  2016-09-30 Views:  199 Downloads:  0

Issue Description

We have the following scenario:

- TE30 with V500R002C00SPC200 firmware version having a private IP address ( for example

- One personal computer in the same network ( IP:

 - Router with private and public network interfaces ( &

The entire network setup can be viewed under the below schema:



Handling Process

The Whitelist option was activated to prevent unauthorized access and unwanted calls.

However, as per instructions to be found under the Administrative Guide, the engineer wanted to add also the IP address of the computer so that the whitelist and other operations could be peformed onto the TE30.

Whenever the Whitelist was activated, the engineer was adding onto the TE30 the on the web page causing the TE30 to block access to the administrative web page from the same computer for which that IP address was used.

Given the fact that whenever using that computer to access the TE30, the router was using the internal routing table and IP addressing (thus the request to access the webpage was made from ->, the IP address to be added onto the Whitelist should have been and not the public IP address of the computer -

Root Cause

Given the fact the router was having two interfaces (Private IP interface & Public IP interface) and based on routing principles all requests coming from an IP on the same network to another IP in the same network will not be routed to another network and then returned to that network.

Also, given the above scenario, the routing of the packets (requests) is done from to and not through the internet.


Add the private IP of the computer ( to the Whitelist instead of the public IP