[cobalt-users] QUBE2 Virtual hosting on my Qube2..woes, woes and yet more woes :|

["Jason Aspinall" <jaspinall@xxxxxxxxxxxxxxx>]

I'm following the advice from the Cobalt site with respect to doing a spot
of light virtual hosting on my Qube 2 (1 site), and upon trying to get eth0
to respond to a second public IP, I seem to be hitting a brick wall :|

This is how I'm trying to set the virtual port up:

DEVICE=eth0:0
IPADDR=62.172.76.136
NETWORK=62.172.76.128
NETMASK=255.255.255.240
BROADCAST=62.172.76.129
ONBOOT=yes
ALIAS=yes
BOOTPROTO=none

When the server reboots, the config file automagically changes to:

DEVICE=eth0:0
IPADDR=62.172.76.136
NETWORK=62.172.76.0
NETMASK=255.255.255.0
BROADCAST=62.172.76.255
ONBOOT=yes
ALIAS=yes
BOOTPROTO=none

How come?  The rebooted settings are useless :|

Upon resetting the values to the correct ones, and issuing the IFUP command,
I can ping the address 62.172.76.136 and get a reply.

I've also setup the virtual hosting settings in the httpd.conf file right at
the bottom between the <VirtualHost> </VirtualHost>, yet I can see the
'virtual site' over my lan by putting the web address or IP in a web browser
(so long as I also put the Listen directives above the VirtualHost stuff),
yet over my dialup at home, I can ping the address, get a response, but no
webpages load :|

Also, if I leave the Listen directives in the httpd.conf file, I can no
longer see *any* of my FrontPage Sub-webs over the lan.  As our intranet
quite extensively uses FP for publication purposes, I /cannot/ leave the
Listen directives in.

Anyone with a clue or two more than me care to push me in the right
direction over the initial multiple port problem, then the webserver
settings..

TIA

--
Jason Aspinall
Lion Laboratories Limited, Barry, UK, CF63 2BE
Tel +44(0)1446 744244 Fax +44(0)1446 720937