Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is probably a management web interface listening on 80. Configure the management web interface to listen on a different port and then try again.
Hi,
Thanks for your advice.
I found it. The router default setting takes up this port. Now I have 2 options;
1) change the default setting listening to port 8080 and forward port 80 to the remote PC which in my case is the guest of KVM running Apache web server.
OR
2) retain the default setting and forward port 8080 to the remote PC. But I have no idea how to make this change on the guest listening port 8080 instead of 80. Besides can visitors browse the websites on the server if forwarding port 8080 instead of port 80?
1. depends on the router. need to check the manual...
2. in that case they can reach that server by: http://host:8080/some/path/..., you need to tell the user they need to specify the port.
1. depends on the router. need to check the manual...
I'll consult the techical support of TP-Link agent to clarify it. There is no manual with its delivery.
Quote:
2. in that case they can reach that server by: http://host:8080/some/path/..., you need to tell the user they need to specify the port.
Performed following test on a PC running Virtualbox
Host - Ubuntu 14.04
VM - Apache web server running on Ubuntu 14.04 desktop
On router (Forwarding)
Service Port 8080
Internal Port - blank
IP Address - 192.168.0.xxx
Protocol - ALL
Status - Enabled
Common Service Port - not selected
Unable to connect
Firefox can't establish a connection to the server at 192.168.0.xxx:8080.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
Did you add 8080 to your apache config now?
You don't need to.
You only use 8080 from an external machine - your router forwards that to 80 on the apache host.
Local machines just use 80 as per normal.
No, switch of the remote management on your PUBLIC interface.
Did you add 8080 to your apache config now?
You don't need to.
You only use 8080 from an external machine - your router forwards that to 80 on the apache host.
Local machines just use 80 as per normal.
Hi,
Router remote management closed. I haven't edited apache config in this test.
OK.
That is a separate problem, most likely bad pathnames in your site links.
Backing up a bit - if you are only trying this from machines on your LAN (as indicated by the 192.168.x.x addressing) then port forwarding on your router has nothing to do with anything.
OK.
That is a separate problem, most likely bad pathnames in your site links.
Backing up a bit - if you are only trying this from machines on your LAN (as indicated by the 192.168.x.x addressing) then port forwarding on your router has nothing to do with anything.
This is only a test.
I'm prepared running my websites on VMs which can be visited on Internet. Currently my websites are hosted on Godaddy server with copy websites on local servers, i.e. VMs. My planning is when the local websites are up visitors will browse them on Internet, not on Godaddy server. When the local websites are down visitors will browse the websites on Godaddy server.
But I must make sure the local websites can be browsed on other machines.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
