RE: Multihomed hosts and virtual web hosts

Will Partain mumbled about my proposed changes:

> Don't broadcast, netmask, etc., also need to move into this?
> Also, I'm thinking "aliases" might be better than
> "local-name"...? so perhaps
> 
>     <network-interfaces> <!-- proposed rename... -->
>      <entry name="hme0"><table>
>        <entry name="ip-address">192.168.1.1</entry>
>        <entry name="netmask">255.255.255.0</entry>
>        <entry name="broadcast">192.168.1.127</entry>
>        <entry name="aliases"><list>
>          <item>gold-hme0</item>
>          <item>gold-hme0-another-alias</item>
>        </list></entry>
>      </table></entry>
>    </network-interfaces>

This looks great.

> Of course, with the lovely ARK table merging, you could just
> put

>     <network-interfaces> <!-- proposed rename... -->
>      <entry name="hme0"><table>
>        <entry name="netmask">255.255.255.0</entry>
>        <entry name="broadcast">192.168.1.127</entry>
>      </table></entry>
>    </network-interfaces>

> in a prototype and all the conforming machines would come
> right.

Moving the netmask and broadcast address into a prototype reduces
duplication, but the network interface device name, hme0, probably is the
wrong key.  A network may serve various Suns connected via hme0, qfe2, le0,
or other devices.  The same network may also have HP boxes, Linux boxes,
etc. connected via other network devices.

The netmask and broadcast address can be derived from a CIDR network
description (192.168.1.0/24 in the example).  Given a particular host IP
address, 192.168.1.1 for example, and a list of CIDR network descriptions,
it should be possible to select the relevent network and compute the
appropriate network and broadcast addresses.

Now where should we list the networks?



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com