Httpd bind

**scientica** · 10-05-2003

I can't be like this: the router is giving you a new ip every now and then?

**mattspencer** · 10-05-2003

Yeah, I don't unsderstand it either, all i know is that my ip was 24.136.175.195

and i plugged it into the router and it changed to

24.136.169.112

which is what it is now.

**bpark** · 10-05-2003

You probably get DHCP from your ISP. The previous time you had it set to a certain IP, it worked because that was the IP that was leased at that time. By the time you setup a router, a new IP was probably obtained and that's probably the reason why it wasn't working.

**Allblack** · 10-05-2003

What kind of router do you have? Is it one where you can connect several pc's to? Or some kind of build in solution?d to the net and get's a dynamic ip like yours. I have my network behind the router in the 192.168 range. On my router I opened port 80 to point to one of my pc's.o it does not matter if the ISP IP changes because all http traffic gets forwarded to my webserver.

Obviously my isp provided some kind of dynamic dns solution so that my domain name is always accessible.

**bpark** · 10-05-2003

Yes, forwarding port 80 does that. However, you still have to know if your public IP has changed. If a computer from the outside is trying to connect using the old public IP, then it will not work after your router has leased a new IP. In Matt's case, he used the "Listen" directive for apache to listen specifically to the public IP. I too am confused to why it won't work with the new IP but this directive is really unecessary unless setting up multiple ports or multiple sockets.

Matt:
Can you double check your public IP and set it again. I think this might have something to do w/NAT. Since the request for port 80 is forwarded to your computer, I'm not 100% sure if the source IP still remains the public IP as the packet is being forwarded. If the src IP remains as public IP (theoretically speaking, i don't see why it would need to change), then you should not have any problems at all. By the way, do you have any other computers? If you do, you can try connecting from inside the network to your Web server. Of course set this it back to 24.136.169.112 and test it. My guess is that it won't when "Listen" is set to that IP.

**mattspencer** · 11-05-2003

ok, sorry it took me so long to post. From what i've seen and learned in the past few weeks is that, if you are behind a router, you can't tell apache to listen to the routers external (public) IP, or the computers external IP. What you need to do is say

Code:

Listen *&#58;80

which means (i think) that apache will listen to a packet sent to ANY external IP as long as it comes through port 80. so, if you have no router use

Code:

Listen &#40;external IP&#41;&#58;&#40;port&#41;

if you are behind a router, use

Code:

Listen *&#58;&#40;port&#41;

.

I know how frustrating it is to get this stuff working, so if anyone needs help setting up a basic apache server, email me at mattspencer1@earthlink.net.

I would like to thank everyone for their help.

**mikecarlyle** · 02-24-2008

Hi Matt where is the linux config file?

**devils casper** · 02-24-2008

Hi mikecarlyle !

Welcome to the LinuxForums.

This thread is very old.
I would suggest you to start a New Thread and explain your problem in detail. We will try our best to help you.

Sorry for inconvenience. Thread Locked.

Thread Tools

Display

Httpd bind

Posting Permissions