After configuring Raspbian linux and a Huawei E303 3G USB stick, I am stuck accessing the machine from the Internet by its public IP address.

Details: The E303 stick was configured to work as an Ethernet device (mode switch worked OK). Linux creates an eth1 device for it and receives an ip address via DHCP from the E303 after adding the device to /etc/network/interfaces. After setting it as the default route, all access from the machine to the Internet works fine - route add default gw

The IP address eth1 receives is - or, if I use a different sub-model of the E303, it is I can tell that the E303 devices are slightly different, because - after mode switching - one of them holds the USB product id 0x014db, the other 0x014dc. Besides the assigned subnets they are not distinct.

Both sticks run a web server and may be accessed without problems, however, there are no configuration option on their network behaviour. They show their own IP address as from the 10.34.X.X subnet (from the device information web page).

Then I registered a dynamic IP address (with no-ip.com) and installed the respective software package. My public IP address is properly registered with no-ip.com (when looking at the hosts listing on their web site) and ping displays the correct, public IP address of my machine. Both, when pinging from the Raspbian and from a different machine in a separate network. Btw, when using the ddclient package, instead, I see the exact same result.

When not using the 3G stick, but plugging in the on-board Ethernet, the machine may be ping'ed, ssh'ed from the local network without problems, and I can get web pages served as well.

My assumptions are that the configuration of the E303 device, routing out, and the dynamic IP address registration are basically OK. But I have no clue how to make the machine visible to the Internet. All connections from the outside time out. The Huawei 3G stick and the telephone provider infrastructure seem to act as intermediate network devices applying NAT without port forwarding to my machine.

2 Answers 2


I had a similar problem. I found out that the the GSM modem ISP blocks all incoming traffic. I read that you can pay the ISP extra to permit incoming traffic. I only wanted to ssh to the RPi over GSM. A reverse SSH tunnel was the solution. I don't know how to solve your problem. But at least I can provide a hint to the cause of it.


You would need a port forwarding configuration in your E303 device, which just isn't available with the latest device firmware.

I saw old screenshots of the web interface which had a couple more options, but the current one is really bare-bones.

As the above poster wrote, a reverse tunnel is a good option. The host in question has to be a (semi-)static one though - or you devise some kind of destination polling and connect to the machine in question then.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .