Topic: Aditional DHCP range

[brick]

Hi,
I created two extra ranges for my Local Network, I'm trying to separate the clients that are part of the lab, wireless, school admin and students.
I have set the clients under the Hostnames and Addresses panel, but only the clients that are part of the orginal range can get addresses, none of the 'new' range works.
I looked under the dhcpd.conf and can only see the original network as well.
Is there something I'm missing?
Is there something I can do do deliver the IP's to the extra range?

[uniqsys]

Hi,
I created two extra ranges for my Local Network, I'm trying to separate the clients that are part of the lab, wireless, school admin and students.
I have set the clients under the Hostnames and Addresses panel, but only the clients that are part of the orginal range can get addresses, none of the 'new' range works.

Could you explain yourself better here, please?  What do you mean by "created two extra ranges" ?

It appears that you are trying to assign specific IP addresses to specific machines as described in the Admin manual on http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#Hostnames_and_addresses

I looked under the dhcpd.conf and can only see the original network as well.
Is there something I'm missing?
Is there something I can do do deliver the IP's to the extra range?

Are the ranges included in your server console DHCP range?  Do you have the proper subnet mask?

[mercyh]

Are you actually talking about separate subnets?

E.g: Subnet #1 IP range 192.168.1.xxx Subnet mask 255.255.255.0
      Subnet #2 IP range 192.168.2.xxx Subnet mask 255.255.255.0

[brick]

Are you actually talking about separate subnets?

E.g: Subnet #1 IP range 192.168.1.xxx Subnet mask 255.255.255.0
      Subnet #2 IP range 192.168.2.xxx Subnet mask 255.255.255.0

Exactly!

uniqsys:
The server console does not allow me to include extra ranges, and I can only see the original range under the dhcpd.conf:

Code: [Select]

subnet 192.168.0.0 netmask 255.255.255.0
{
    option broadcast-address    192.168.0.255;
But I can see the config for the hosts that I added, such as:

Code: [Select]

host wrt.yorktown.sme.homelinux.net {
    hardware ethernet 00:13:10:62:19:E0;
    fixed-address 192.168.200.241;
}


[mercyh]

But I can see the config for the hosts that I added, such as:

You are not talking about a separate range of addresses on your local network. That would be something like the following.

IP address range #1 192.168.0.50 - 192.168.0.100, subnet mask 255.255.255.0

IP address range #2 192.168.0.150 192.168.0.200, subnet mask 255.255.255.0

=====================

You are actually talking about two different networks that would need a router between them or an additional local network added in server manager to see the server. I also do not think that you can use one DHCP server to handle both networks but I could be mistaken on this.

You might be able to give the server an IP address of say 192.168.0.1 and a subnet mask of 255.255.0.0 (allowing it to talk to all 192.168.xxx.xxx subnets) and then give the workstations 192.168.0.xxx and 192.168.200.xxx with subnet masks of 255.255.255.0. But I have never tried this and am not sure it would work and the workstations with the 192.168.200.xxx would not be able to communicate with the server.

[uniqsys]

Exactly!

uniqsys:
The server console does not allow me to include extra ranges, and I can only see the original range under the dhcpd.conf:

That is correct it doesn't, but I think if you change your DHCP subnet mask to 255.255.0.0 it would include the 192.168.200.xxx requests.  I have never attempted such a configuration so I have no experience for you. Sorry.

[CharlieBrady]

This is a known bug. The hostnames and addresses panel should not allow you to enter MAC addresses for addresses which are not on the local network.

http://bugs.contribs.org/show_bug.cgi?id=3809

You also shouldn't be trying to set up multiple networks on the same physical LAN. Different networks need to have a router between them.

[mercyh]

That is correct it doesn't, but I think if you change your DHCP subnet mask to 255.255.0.0 it would include the 192.168.200.xxx requests.

This will not not separate the clients as they will all be on the same subnet. It is just a much larger subnet.

[brick]

This will not not separate the clients as they will all be on the same subnet. It is just a much larger subnet.

Which is what I'm looking for.

[cactus]

Which is what I'm looking for.

You can only seperate them using routers like stated earlier. You can configure them to be on a different subnet however, but they will be able to contact each other. Blocking traffic requires a router.

If you would like to change your subnet log in as admin and reconfigure your server to use a broader subnet than the normal C-class subnet (255.255.255.0). You would need to choose a B-class subnet (255.255.x.0) to allow for more than 256 hosts on your network.

Take a look at subnet calculation to see how you should arrange your subnet to do so. Here is a subnet calculator that might show you how many hosts are allowed based on the choosen subnet: http://www.subnet-calculator.com/subnet.php?net_class=B

[brick]

Thanks for all the replies, but I'm not looking at routing or securing the network. I have a separate device for that, which works as a bridge and I can control the traffic by ports or signatures, it even allows me to control ARP and tie MAC to IP.

[mercyh]

Thanks for all the replies, but I'm not looking at routing or securing the network. I have a separate device for that, which works as a bridge and I can control the traffic by ports or signatures, it even allows me to control ARP and tie MAC to IP.

This will not not separate the clients as they will all be on the same subnet. It is just a much larger subnet.

Which is what I'm looking for.

Then what are you looking for?

I thought you were wanting to protect the LAN from itself. Separate the sheep and the lions among your users.

[brick]

Yes, and in my case I'm creating the rules by range, and why I need the DHCP to deliver the IP in the new range.

[cactus]

Yes, and in my case I'm creating the rules by range, and why I need the DHCP to deliver the IP in the new range.

So why not try extending the subnet like I suggested?

[brick]

So why not try extending the subnet like I suggested?

I'll try that