[Sussex] Unbinding Apache from an IP

Al Bennett al at plasticfish.co.uk
Mon Feb 6 23:02:23 UTC 2006


Thanks Guys, particularly John for proving I'm not going entirely insane!

Jon got me close by properly restarting Apache, which solved part of the 
problem.

I know this is possible, but for the life of me I can't get Apache and 
OpenSSH to play nice and stick to one IP address each.  One or the other 
will complain when being started that something is bound to *:80 when 
netstat shows that isn't true.

With a bit more experimentation I could probably have got this to work but 
I've run out of time as I'm off again tomorrow and this is a semi-production 
server and SSH is my only access, so I don't want to break it too badly!

Thanks for helping!

Al

----- Original Message ----- 
From: "John Crowhurst" <fyremoon at fyremoon.net>
To: <sdp.williams at btinternet.com>; "LUG email list for the Sussex Counties" 
<sussex at mailman.lug.org.uk>
Sent: Saturday, February 04, 2006 12:04 AM
Subject: Re: [Sussex] Unbinding Apache from an IP


> On Fri, February 3, 2006 17:51, Stephen Williams said:
>> Have a look in the apache config files for a section that looks like
>> this:
>>
>>
>> # Listen: Allows you to bind Apache to specific IP addresses and/or
>> # ports, instead of the default. See also the <VirtualHost>
>> # directive.
>> #
>> # Change this to Listen on specific IP addresses as shown below to
>> # prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
>> #
>> #Listen 12.34.56.78:80
>> Listen 80
>
> I decided earlier today to test out my theories with my Linux firewall. I
> assigned two additional IP addresses to it (its primary is 192.168.2.1)
> 192.168.2.64 and 192.168.2.65
>
> I changed my httpd.conf file so that the server listens on 192.168.2.1 and
> 192.168.2.64 and restarted Apache.
>
>>From my web browser, I looked at 192.168.2.1 and 192.168.2.64 and saw
> content, then looked at 192.168.2.65 and still saw content even though I
> hadn't specified this IP in the httpd.conf file.
>
> I then uncommented the BindAddress 192.168.2.1 entry and restarted Apache.
>
> This time from my web browser I could reach 192.168.2.1 and 192.168.2.64,
> but not 192.168.2.65
>
> Bear in mind I'm using Apache 1.3, BindAddress is depreciated in Apache 
> 2.0
>
> --
> John
>
> _______________________________________________
> Sussex mailing list
> Sussex at mailman.lug.org.uk
> E-mail Address: sussex at mailman.lug.org.uk
> Sussex LUG Website: http://www.sussex.lug.org.uk/
> http://mailman.lug.org.uk/mailman/listinfo/sussex
>
> 





More information about the Sussex mailing list