3

After taking the router out of its box and powering it up, we change the default SSID (for example, from GL-AR300M-000 to Router7) and LAN IP address so it is on the 10.66.171.x range, then set up a couple port forwards, for example 8080, to point to an internal address, (for example 10.66.171.20). We also scan and connect it to our building WiFi network (let’s call it BuildingNetwork), which will assign the router an IP address on the 192.168.1.x range, for example 192.168.1.89.
Because the computer on 10.66.171.20 has a web server on port 8080, I can access that content if I connect directly to the router by connecting to SSID Router7 and go to http://10.66.171.20:8080.
Normally, If I connect to BuildingNetwork, I can access the same content if I go to http://192.168.1.89:8080, because the port forwards are in place. But on this particular unit they just don’t work, they time out. Most ironically, however, I can access the content by connecting to Router7 directly and opening http://192.168.1.89:8080. Also, the computer on 10.66.171.20 HAS internet connection, so it IS successfully connected. But the port forwards don’t work as they usually do.