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.
Correct me if I'm wrong, but if his isp blocks port 80, that would mean that the port was either blocked from the source directly, or from the router/modem that the isp provided you with.
So, if you wanted to redirect a certain domain.com to go to a different location, maybe you could look into dns as a solution. I don't know that much about dns, but I think that could be a solution.
yeah you are right. if one runs ip forward on the local machine the packets must first reach the machine on the initial port from which they will be forwarded. if the ISP is blocking the packets then they wont reach the machine and hence they wont be forwarded.
i am sorry i missed that one before
what you need is a port forwarding serive provider. there are lots of then and some are free the last time i checked. do a google search and you can find some.
I have also been looking at the port forwarding services. Like http://no-ip.com/ but this does raise an interesting question though. Could you make a dns server that takes a domain name without the :8080 for example and translate it go be forwarded to a certain IP with :8080 attached?
Distribution: Solaris 10, Solaris 8.0, Fedora Core 3
Posts: 203
Rep:
Are you sure its your ISP that blocks port 80 or your router? Are you trying to host a webpage? For my webserver to be visible to the outside I have to forward requests to port 80 on my router to my webserver.
if the isp blocks traffic to port 80, then there really isn't anyway to serve the content without using another port, which will require you to specify the port number in the URL. one options is to tunnel connections from someone else's box, but I can't imagine anyone offering to do that for you (it would be easier to simply host the content there).
regarding the question in post 7, the DNS doesn't handle port numbering, only the addressing, so it would not be possible to have lookups automatically append :8080 through DNS
for the first account you make a redirect called like foo2.no-ip.com
and you direct that http address to your home IP
THEN you create a WEB redirect that links foo.no-ip.com to foo2.no-ip.com:8080 (where 8080 is the port you've chosen for your http server on your local machine)
then foo.no-ip.com is your address, and your ISP can KISS OFF!!!
www.dynu.com offers port forwarding. Check them out. I have never used their port forwarding service, but I think they alter the name for you (i.e. changin port 80 to port 8080) without the user having to type in the port number.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.