Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
11-24-2005, 10:46 PM
|
#1
|
Member
Registered: Aug 2005
Location: NY,USA
Distribution: Debian, Gentoo, Ubuntu
Posts: 103
Rep:
|
router issue (accessing local webserver)
my router is a debian box with dual NICs, routing to eth0 from the internet on eth1 using iptables
i have a webserver running on 192.168.1.5 on port 6080. When i request http://domain:6080 from within the same LAN as the webserver, I get connection refused. When I connect to http://192.168.1.5:6080 within the LAN, it works perfectly.
When someone outside the network requests http://domain:6080, it works fine.
I am currently using my super-unstable linksys router until I can resolve this, so that I can put the linux box back in.
yay for you guys!
edit: this happens with all ports that are accessed from within the LAN via the domain, so I need this issue to be resolved for all ports (although I suppose any fix would fix that)
Last edited by FliesLikeABrick; 11-24-2005 at 10:47 PM.
|
|
|
11-25-2005, 06:50 AM
|
#2
|
Member
Registered: Jan 2003
Location: Cambridgeshire, UK
Distribution: Mint (Desktop), Debian (Server)
Posts: 891
Rep: 
|
When you do http://domain/server from the inside you will be getting the outside address as a dns response. So an inside device will be attempting to access the outside interface address. I don't know for sure if this is the issue but some routers will not allow it. You will probably need to use a static host entry if you really want to resolve the name. Is it really a biggy?
|
|
|
11-25-2005, 10:57 AM
|
#3
|
Member
Registered: Aug 2005
Location: NY,USA
Distribution: Debian, Gentoo, Ubuntu
Posts: 103
Original Poster
Rep:
|
yes it is a biggy. I could live with it, but there are 3 other people in this house who use that server for hosting things(sites, images), and they wouldn't understand why it has always worked and now doesnt.
What is this about a static host entry? I wouldn't mind going an extra step or two to make this work
|
|
|
11-25-2005, 11:41 AM
|
#4
|
Member
Registered: Jan 2003
Location: Cambridgeshire, UK
Distribution: Mint (Desktop), Debian (Server)
Posts: 891
Rep: 
|
if you check out /etc/hosts its a file for manually entering hostnames. IP should theoretically check the hosts file first before attemting a DNS resolution, so if you stick an entry in it pointing your domain name at the internal address it should sort you out. You do need to do it on each of your workstations tho...
Its also possible that you need an IP tables entry specifically allowing traffic sourced from your internal network destined to the external address, that might also sort it.
|
|
|
11-25-2005, 11:43 AM
|
#5
|
Member
Registered: Aug 2005
Location: NY,USA
Distribution: Debian, Gentoo, Ubuntu
Posts: 103
Original Poster
Rep:
|
the iptables solution sounds better, because then i could route the traffic to different computers internally depending on what port, right?
I actually run 2 webservers in the LAN, and it sounds like the static host file entry would route all requests to the domain from within the LAN to that one box, whereas with the iptables entry I'd be able to specify ports.
Is this the correct impression?
|
|
|
All times are GMT -5. The time now is 06:55 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|