Anybody doing port forwarding on Huawei router? Sure could use some help!

[Lopburi99]

I have 3BB's True 50M VDSL plan which came with a Huawei HG630 V2 router. I have successfully set up call forwarding on other routers in the past but I am getting nowhere with this one -- can't figure out how to do it -- Driving me nuts! I have a Raspberry Pi 3 server set up and running Lighttpd on port 99. Any help or suggestions greatly appreciated!

[Crossy]

Try here for step-by-step guides:-

https://portforward.com/huawei/

 

 

[sniffdog]

Dont setup call forwarding on a router .. it simply doesn't work.[emoji12]


Sent from my iPhone using Tapatalk

[RichCor]

Also make sure 3BB is issuing your router an actual public IP address, and not a Carrier-Grade IP in the 100.64.0.0/10 (100.64.0.0 – 100.127.255.255).

Edited November 29, 2016 by RichCor

[Lopburi99]

5 hours ago, Crossy said:

Try here for step-by-step guides:-

https://portforward.com/huawei/

 

 

Great, this looks exactly like what I need! I had a couple of minutes to try it before leaving for a couple hours but I must have done something wrong. The port tester said port 80 was in use and to close program using it (nothing using it that I am aware of). Can't wait to try it again tonight. Thanks Crossy!

 

(RichCor, checked and my IP is public)

Edited November 29, 2016 by Lopburi99

[RichCor]

24 minutes ago, Lopburi99 said:

 The port tester said port 80 was in use and to close program using it (nothing using it that I am aware of).

 

Port 80 is used to access the Router's web-based admin/setup.

 

Use is usually hard coded by the embedded Router OS so it's BLOCKED on the WAN side and the LAN side is forwarded to the Router HTML-based internal web-server daemon running admin software interface.  

 

Some higher-end Routers will allow forwarding WAN side port 80 independent of the LAN side configuration. 

[Lopburi99]

Hmm. Then if I exit the web-based admin program, will it close the port so it can be used for forwarding? I can test in the morning. Otherwise, what go-around can I use?

[RichCor]

You can't close it, as it's a server daemon process always running on your router.

While you might also have problems forwarding ports 21, 22, 23 and 80 (as the router OS reserves these for itself), all the other ports should be available for forwarding.

Edited November 29, 2016 by RichCor

[Lopburi99]

38 minutes ago, RichCor said:

You can't close it, as it's a server daemon process always running on your router.

While you might also have problems forwarding ports 21, 22, 23 and 80 (as the router OS reserves these for itself), all the other ports should be available for forwarding.

 

But port 80 is the common HTTP port. So this router cannot be used with a HTTP server? What good is forwarding a different port if DNS servers are using port 80? This is making less and less sense. I must be missing something fundamental.

[RichCor]

Web Servers are typically hosted on port 80 for http and port 443 for https incoming requests.   These are the assumed defaults so browsers can make public connections. The web server can be hosted on most ANY port, but that port must then be called out using in the URI (ex:  http://www.xxx.yyy:zzzz ) where zzz in the non-standard port being called by the web browser.

 

If you're hosting your own Domain Name Server then they primarily utilize UDP port 53 for incoming, and serve requests on a random port of 49152 - 65535.

 

What exactly are you hosting that you want Internet facing?

Edited November 29, 2016 by RichCor

[Lopburi99]

My own Wordpress website running on my Pi. Just trying to make it accessible to the public by hosting it on port 80. Nothing usual. Thanks for helping me understand what is going on here.

[Lopburi99]

Damn, I think I've discovered the problem. My friend (with whom I share our/his 3BB service) uses Skype regularly and I just read Skype uses port 80 by default! So now I need to figure out how to change Skype's settings to use a different port. Should be easy enough to do. But first I need to try to convince my friend I won't screw up his use of Skype...<sigh>

 

Note: In my previous comment, "nothing usual" should be "nothing unusual")

Edited November 30, 2016 by Lopburi99
To correct typo

[RichCor]

Yea, as some ISPs sometimes block ports to keep residential customers from hosting services.  Some instant communication programs like Skype and TeamViewer will reserve common ports like 80 and 443 (that are normally reserved for http and https traffic) as backup fail-over methods for traversing through NAT firewalls.

 

According to Microsoft:

If the port chosen for incoming connections becomes unavailable, by default ports 80 and 443 will be used by Skype as alternatives. If another application (such as Apache HTTP server or IIS) uses these ports, you can either configure the server application to use other ports, or you can configure Skype to not use these ports.

[maxpower]

On 11/30/2016 at 9:19 AM, Lopburi99 said:

My own Wordpress website running on my Pi. Just trying to make it accessible to the public by hosting it on port 80. Nothing usual. Thanks for helping me understand what is going on here.

 

Before you waste more time fighting port forwarding check what ports your ISP has open. I believe AIS have quite a restriction and only open selected ports upon request. Not sure about 3BB

[Lopburi99]

I just got an email reply from 3BB. Port Forwarding IS allowed and no ports are blocked. Port 80 was specifically acknowledged as forward-able.

 

I disabled Skype from using ports 80 and 443. Forwarding still not working. Back at it again tonight.

Edited December 3, 2016 by Lopburi99

[maxpower]

Just now, Lopburi99 said:

I just got an email reply from 3BB. Port Forwarding IS allowed and no ports are blocked. Port 80 was specifically acknowledged as forward-able.

 

I disabled Skype from using ports 80 and 443. Forwarding still not working. Back at it again tonight.

Question. Your Pi has a static IP and you can access your wordpress locally just by using the local IP without any port specified - correct ?

[Lopburi99]

Yes Maxpower. I have the Pi on LAN static port 99. If I type in 192.168.1.99 in my browser, my site comes up.

[maxpower]

On 11/29/2016 at 7:04 PM, RichCor said:

 

 

Change Pi http config to listen on port 80 then test from Lan side to see if ok.

Set modem forwarding -

External start port 80
External end port 80
Internal host 192.168.1.99
Internal port 80

Go to a site like http://www.yougetsignal.com/tools/open-ports/

Check if  port 80 is open on your WAN IP.
 

[RichCor]

So 3BB gateway isn't blocking ports, but it looks like your router is still reserving/blocking port 80.  

[Lopburi99]

Mystery identified and semi-solved! Skype was the culprit! It sometimes may use ports 80 and 443, and we have several people who have Skype configured.

 

The solution was to use a port number different than 80 (I chose 8099) in my server configuration and fill out the forwarding rule accordingly. Sure enough, the port checker finally returned "OPEN". The only thing keeping the solution from being perfect is the port number needs to be added for the browser, e.g. MySite:8099. I believe no commercial DNS servers pass on port numbers. So I will need to contact those using Skype on my system and getting into the configuration file to uncheck the "use port 80 or 443 if needed" box. Then I can have GoDaddy's DNS servers will send clients straight into (reset value) of port 99 for smooth web operations right to my server.

Edited December 6, 2016 by Lopburi99

[RichCor]

If you configure your web server for https: (port 443) it might work without issue (or having to add a :port to the domain, and it would be secure to boot (pun intended).

[maxpower]

17 hours ago, Lopburi99 said:

Mystery identified and semi-solved! Skype was the culprit! It sometimes may use ports 80 and 443, and we have several people who have Skype configured.

 

The solution was to use a port number different than 80 (I chose 8099) in my server configuration and fill out the forwarding rule accordingly. Sure enough, the port checker finally returned "OPEN". The only thing keeping the solution from being perfect is the port number needs to be added for the browser, e.g. MySite:8099. I believe no commercial DNS servers pass on port numbers. So I will need to contact those using Skype on my system and getting into the configuration file to uncheck the "use port 80 or 443 if needed" box. Then I can have GoDaddy's DNS servers will send clients straight into (reset value) of port 99 for smooth web operations right to my server.

 

So Skype on a Windows machine has started a LAN fight over port 80 with a server on a Raspberry Pi. Cool.
 

 

[Lopburi99]

20 hours ago, RichCor said:

If you configure your web server for https: (port 443) it might work without issue (or having to add a :port to the domain, and it would be secure to boot (pun intended).

 

Unfortunately didn't pass my test.

[Lopburi99]

7 hours ago, maxpower said:

 

So Skype on a Windows machine has started a LAN fight over port 80 with a server on a Raspberry Pi. Cool.
 

 

 

Right, I came across that. Some fairly intense complaints against Skype for "hogging" a port specifically designated worldwide for HTTP!

[RichCor]

Do you have UPnP enabled?  I would disable that, reboot your router, then try again.

 

Many communication suites sitting behind NAT Firewalls will try to use UPnP to automagically create their own port forwarding tunnels (even without express permission) as UPnP gives them that ability to create and reserve Port/LAN IP tunnels on the fly.

 

Usually these same suites will stay away from the common ports, but will use them in fallback mode when the other port options fail.

 

Anyway, once UPnP is disabled, and all your port forwards are explicitly put in place and the router rebooted then the "https:" default using port 443, and maybe even "http:" default using port 80 might forward correctly with those forwards properly set .  There is still the possibility the router won't forward 80 or 443 if they are hard-coded in the router to reserve for itself.    

[maxpower]

1 hour ago, Lopburi99 said:

 

Right, I came across that. Some fairly intense complaints against Skype for "hogging" a port specifically designated worldwide for HTTP!

 

Where on your network is this Skype port hogging taking place. Is your router bombarded with incoming port 80 requests and thrown in the towel.

[Lopburi99]

On 12/7/2016 at 7:01 PM, maxpower said:

 

Where on your network is this Skype port hogging taking place. Is your router bombarded with incoming port 80 requests and thrown in the towel.

 

Not clear where the Skype interference is coming from. There are a several Skype users, and I  don't know if everybody has turned off use of 80, 443. Doesn't matter now, I've found a good solution (see my next post).

[Lopburi99]

Ok everybody,  you need to know about this. Cheapname.com offers a DNS service which allows "URL redirect" which takes a port number. Solved the problem!

[Lopburi99]

22 hours ago, Lopburi99 said:

Ok everybody,  you need to know about this. Cheapname.com offers a DNS service which allows "URL redirect" which takes a port number. Solved the problem!

 

Oops! Make that Namecheap.com. Wake up Don. 

[Morakot]

Old thread, but...

 

Did anyone find out whether ports 80 and 443 are hardwired in this routers? Or can one really forwarded these two ports to anywhere on the LAN?

 

Cheers!