From: Jukka Laaksola (jukka.laaksola_at_netland.fi)
Date: Fri 23 Aug 2002 - 11:07:09 BST
Jacques Gelinas wrote:
> On Mon, 22 Jul 2002 09:06:53 -0500, Jukka Laaksola wrote
>
>>Jacques Gelinas wrote:
>
>
>>>We will need to change the way we handle that. Instead of having
>>>IPROOT and IPROOTDEV, we will have something like
>>>
>>>IPROOT="eth0/IP1 eth1/IP2 IP3 IP4"
>>>IPROOTDEV=eth2
>>>
>>>Any IP no explicitly tied to a device will be configured with IPROOTDEV. In
>>>the example above, IP3 and IP4 will go on eth2.
>>>
>>>What do you think ?
>>
>>Sounds good to me. It's quite clear way to configure IPs and devices.
>>Perhaps the feature is in the next version of vserser?
>
>
> Finally I implented it using : instead of /
>
> IPROOT="eth0:1.2.3.4 eth1:2.3.4.5"
On the main server network configuration:
eth0 10.10.10.35 netmask 255.255.255.0 broadcast 10.10.10.255
eth1 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
I have now IPROOT="eth1:192.168.0.11 212.x.x.10 80.x.x.10 10.10.10.33"
and IPROOT=eth0 in the /etc/vservers/v1.conf.
The problem is netmask ja broadcast for those ip aliases. If I
understood right, IPROOTMASK and IPROOTBCAST doesn't have multi-ip/nic
support.
After the virtual server v1 has started my network configuration:
eth0 10.10.10.35 netmask 255.255.255.0 broadcast 10.10.10.255
eth0:v11 212.x.x.10 netmask 255.255.255.0 broadcast 192.168.0.255
eth0:v12 80.x.x.10 netmask 255.255.255.0 broadcast 192.168.0.255
eth0:v13 10.10.10.33 netmask 255.255.255.0 broadcast 192.168.0.255
eth1 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
eth1:v1 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255
So eth1:v1 is only correct configured ip-alias.
212.x.x.10 and 80.x.x.10 should have netmask 255.255.255.248 and
broadcasts 212.x.x.15 and 80.x.x.15...
And 10.10.10.33 should have netmask 255.255.255.0 and broadcast
10.10.10.255.
How can I configure my network correct with vserver?-)
I can use manually ifconfig for configure tohe ip-aliases
and remove IPROOT and IPROOTDEV from /etc/vservers/v1.conf. Then I can't
use portmap ja rpc-programs in the virtual host. So this is not working
solution.
>
> One day will implement the / to support per IP netmask...
>
That would solve my problem, but when is it coming?
Have a nice weekend for vserver-list's readers.
Thanks for Jack and friends
Jukka
-- Jukka Laaksola Netland Oy