The server has 4 ip addresses. Apache is only listening on the first in the range (despite the wildcard *:80 being used in httpd.conf).

I want to set up a virtual host and bind it to one of the other ip addresses.

Thank you

Hi,

That's easy

One of Apache's related web pages.

Google would have given you the answer in no time flat.

Anyways,

Hope this helps.

In httpd.conf:

Listen 80

Will cause Apache to listen on all interfaces (on all ip addresses) to listen on a specific ip address change this to something like

Listen 192.168.0.133:80

As I said "despite the wildcard *:80 being used in httpd.conf". I.e. the problem does not appear to be with the apache configuration.

When trying to access one of the other IP addresses with a web browser, it just hangs and says the server is taking too long to respond.

Hi,

Wildcard????

A wildcard is not allowed.

It's:
Listen 80

or

Listen 1.2.3.4:80
Listen 12.13.14.15:80
Listen 192.170.2.1:80
<etc>

As stated in the url I posted before...........

To check if apache is listening (and on which port(s)/ip(s)): netstat -a -n | grep ":80 "

I appreciate your help

I was referring to the syntax in the VirtualHost directive. But yes, there is "listen 80" not changed from the default, in the main configuration.

netstat produces:

tcp 0 0 :::80 :::* LISTEN

I believe this means to listen on all available ip addresses. Although I notice some other services e.g. mysql have 0.0.0.0 instead of :::

again, thanks for your help

(by the way, if it makes any difference, I am using apache2)

tcp 0 0 :::80 :::* LISTEN
That looks like a ipv6 notation. Square brackets (in your httpd.conf) could cause this.

Take a look here:

ipv6/apache

It's a link about how to set up ipv6, but maybe you can check entries in your httpd.conf against what's told there and remove/change the 'corrupt' (example??) entry.

Does it work with just one ip (Listen 1.2.3.4:80)??

Hope this helps.

listen / apache 2.0

There are no square brackets in the configuration.

Apache listens fine on the first IP in the range.

I tried specifically with just one of the other ips as you suggested and got an error "could not assign requested address: make_sock: could not bind to address...".

Perhaps the server does not acknowledge the other ips - does not know they are there? Is there a configuration to tell it which ip addresses it has, or does it just know automatically? (The hosting company set up the server and I am sure they knew what they were doing).

Really! I guess that apache docs need to be updated then, and the apache binary has to be scolded for not functioning correctly!

Seriously though, if you have something like:

Listen *:80

Then Apache will listen on all IP addresses (on that machine) on port 80.

Just FYI.

@KimVette: I do agree that it seems to work. Just tried it

I truly don't know if the *.80 notation is a proven concept and should be added/corrected in the manuals. And if unsure its always wise to remove the undocumented stuff and use documented settings only.

I wonder how the Apache people would react if we filed a bug report

I figured it out. I needed to set-up an IP aliase for the other IP using ifconfig. The command goes like this:

ifconfig eth0:0 ***.***.***.***

where ***.***.***.*** is the ip address.

If anyone comes across this thread with a similiar problem. Do a search on setting up ip aliases with ifconfig. You may also need to also set up a route (with the route command) to the ip, but ifconfig seemed to do this automatically for me.