Topic: Aditional DHCP range

[CharlieBrady]

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.

You also need to *physically* separate them. And you use a router for that. For the subnet or subnets which are physically separated from the SME server, use a different DHCP server.

[mercyh]

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.

How can your DHCP server hand out an address to a subnet range it can't even talk too??

I am still curious as to what you would like to achieve....

Do you have some device on your network that can separate access to other workstations on the subnet based on an IP address range? (not a separate subnet) What sort of "rules" are you creating?

If you have such a device, I would like to know what it is.


If you intend to do the separation based on separate subnet. (which is not accessible from the other subnet.) You will need to do as Charlie says and physically separate them. You will then need to put a router between them that allows access only to the shared resources that they both need access too. This can be done with separate hardware and wiring (switches, etc) or with switches with Vlan tagged ports.

*A router can be used to allow 'any' two networks to talk to each other, not just from the WAN (internet) to the LAN.

[uniqsys]

I'll try that

So, if changing the subnet mask on the DHCP works, will you be telling Charlie to leave the bug as is?   

[johnp]

I currently run 5 separate vlan networks in the office. My sme base handles dhcp for 2 of these and a third is via coova-chilli. The other 2 vlans are used for voip traffic on 2 distinct systems (dhcp handled by voip system for these).  Yes I do have a layer 3 switch for inter-vlan routing.

[CharlieBrady]

I currently run 5 separate vlan networks in the office. My sme base handles dhcp for 2 of these

What have you done to make that possible?

[johnp]

Basically duplicated all necessary templates for the second network in templates-custom. Then added an ip helper-address that points to the sme server to the second vlan in the L3 switch.

Since I had to add special options for the IP phones, I ended up using custom templates for most of dhcpd.conf. Since the Mitel teleworker did(does) support the old method of IP Phone support, I was able to use their code as a model. Hacked in support for the new option 125 method of IP phone optioning. Although it is functional, I'm sure it isn't graceful.