The two subnets are not physically connected but a Client should be
able to connect to Subnet A or to Subnet B as well.
JohnStanley Writes:
This is what is confusing. If there *NOT* Physically Connected you will
never CONNECT to them. Hope you can calculate SNs ans SNMs. You can add as
many Nested code blocks you need for Subnets. My advice for you is to use
the 10.x.x.x range of addys to give you more subnets to work with. So give
this a go.
option domain-name "YOU.com";
option domain-name-servers "192.168.0.1, 193.190.63.172"
option subnet-mask 255.255.255.0; # Global Subnet mask
default-lease-time 600;
max-lease-time 7200;
# Here is Subnet number 1.
subnet 192.168.0.0 netmask 255.255.255.240 { # Subnet for first 13 devices,
10 of which are servers, 3 printers
range 192.168.0.10 192.168.0.13; # Range of IP's for our printers only.
option subnet-mask 255.255.255.240;
option broadcast-address 192.168.0.15; # This is the subnets broadcast
address.
option routers 192.168.0.14; # The gateway of this subnet.
option time-servers 192.168.0.14; # Gateway is running a timeserver.
option ntp-servers 192.168.0.14; # Gateway running a timeserver.
}
# Here is Subnet number 2.
subnet 192.168.0.16 netmask 255.255.255.224 { # Subnet for 29 computers
range 192.168.0.17 192.168.0.45;
option subnet-mask 255.255.255.224;
option broadcast-address 192.168.0.47;
option routers 192.168.0.46;
}
group {
host server1 { # the first fixed server for subnet 192.168.0.0/28
server-name server1;
hardware ethernet 0a:23:f2:56:33:x0;
fixed-address 192.168.0.1;
}
host server2 {
server-name server2;
hardware ethernet 0a:23:f2:56:33:x0;
fixed-address 192.168.0.2;
}
}
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
