RE: Network address class

[David M . Arroyo Díaz]

It seems that I made a mistake on the configuration of the server.

On my /etc/hosts file I forgot to include the hostname of the machine and
it's own IP address (because I use DNS as name resolution method). I've just
corrected the file and now cfengine gives me the subnet network address
class.

But I think that this is not a complete solution, because cfengine parses
the content of the hosts file and takes the first occurrence where the
hostname appears for build the network address class (for example 172_32_2).
So, what happens if you have multiple nic's pointing to different ip
subnets? The answer is that cfengine only builds the subnet address classes
for the first one, remaining the rest ignored.

Am I wrong, or is another misconfiguration of my host?

Wouldn´t be better to include as defined classes all of the local subnets
that the host "see"?



-----Original Message-----
From: Mark.Burgess@iu.hio.no [mailto:Mark.Burgess@iu.hio.no]
Sent: jueves, 26 de julio de 2001 16:40
To: darroyo@ya.com
Subject: Re: Network address class


On 26 Jul, David M.Arroyo Díaz wrote:

> I have 3 different private network address spaces, 192.168.1.0,
192.168.0.0, 172.32.2.0,
> and 3 public class c subnets.
>
> I want to set up a script that performs some actions on the hosts wich IP
address is in
> the interval 192.168.1.1 to 192.168.1.254, another different actions for
the hosts from
> 192.168.0.1 to 192.168.0.254, and finally other configuration steps for
the hosts from
> 172.32.2.1 to 172.32.2.254.
>
> I could write a script like this (one for each subnet):
>
> 192_168_0_1::
>     actions_to_be_done
> 192_168_0_2::
>     actions_to_be_done
> ....................
> But this represents 762 entries in total!! (one for each host)

How about:

  192_168_0::
       actions to be done