Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
We have the following scenario:
- TE30 with V500R002C00SPC200 firmware version having a private IP address ( for example 192.168.10.10/24)
- One personal computer in the same network ( IP: 192.168.10.15/24)
- Router with private and public network interfaces (192.168.10.0/24 & 126.96.36.199)
The entire network setup can be viewed under the below schema:
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 188.8.131.52 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 192.168.10.15 ->192.168.10.10), the IP address to be added onto the Whitelist should have been 192.168.10.15 and not the public IP address of the computer - 184.108.40.206
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 192.168.10.15 to 192.168.10.10 and not through the internet.