[Sussex] Unbinding Apache from an IP

[John Crowhurst]

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