Windows Loopback interface and SSH tunnels, or a story of one Huawei Router

Some stuff sounds simple and obvious for one group of people, and sounds crazy for another. One good story started after some attempts to remotely connect to the Web portal of one Huawei 4G Router. The caveat in this situation is that a direct connection was not possible, only thru a Linux Router. Because administrators are lazy – setting up a fully operational VPN was not the case, so I tried to make and SSH tunnel forward. But failed… at start.

Here is an simplified example of the topology:

The typical “fast” solution would be create and SSH session and point the browser to http://localhost:1880 (in case something is already listening to port 80. In fact, like Skype likes to do)

ssh user@RouterA -L 1880:

The problem evolved when I realized that the Router’s web portal had hard-coded URIs (although it took a minute to make myself look into Page and Network inspection) with the Routers LAN address ( in our example). In result – the page was unable to load and the portal was unusable.

The solution found sounds nasty,  but quite simple:

1. Create a New loopback inferface on the administrator PC. The creation on Windows in fact is quite straightforward (

2. Assign the Huawei Router’s IP address with netmask /32 ( on the loopback interface. E.g –

3. Open a SSH tunnel, with IP definition for tunnel forward:

ssh user@RouterA -L

4. Open web browser and navigate to and voila


1. At first I tried a /24 definition of the network mask. That did work at start, but stopped working at some point for a clearly understandable reason. (At least there was no overlapping in routes). Changing the netmask to /32 bringed it back to life.

2. Don’t forget to “disable” the Loopback adapter when you are done, or if you get a Network overlapping you will definitely spend some time on debugging.