[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Combining 4 C-class networks: how?



In article <cistron.Pine.LNX.4.10.10007100803240.24184-100000@login2.powertech.no>,
Harald Thingelstad  <thingels@powertech.no> wrote:
>First:
>The 10.x.x.x network range is, due to standard ip ranges, class A.
>You have used a subnet mask to divide it into 2^16 sub-ip-ranges, using
>four of them.
>
>So a simple solution might be (i've not actually done this) to treat it
>like the class A network it actually is.
>This requires reconfiguration of the windows machines however. (Or
>multiple broadcast adresses, if possible.)
>
>The free adress ranges for class C networks are 192.168.y.x  , y=0..255.
>(256 class C networks.)

Sorry to break in on this thread and being off-topic, but...
CIDR is 10 years old! Anyone still thinking in class A and class C
is probably still using COBOL too... sigh

Anyway - are the windows machines able to talk to each other
even though they are in different networks ?

If yes - see how they do this. Perhaps there is a router for each
network somewhere, or some funky route add statements.

If not - then your approach with the 3 aliases is the right one,
except that you should make sure that you use unused IP addresses
to prevent clashes like you've experienced

Mike.



Reply to: