Hi All,

I have configured dhcp3-server on my debian box and I'm wanting to offer dhcp on one of the vlan interfaces. The dhcp is functioning but when I test applying it to a different vlan, the original PC can still get an IP.

For example:
eth1 has vlan100 and vlan200. Our managed switch has the ports configured such the pc1 is on vlan100 and pc2 is on vlan2. This works fine and I can inter-route between vlans with static IPs.

Our dhcp config is currently set as:


ping-check true;
ddns-update-style none;
default-lease-time 21600;
max-lease-time 86400;
INTERFACES="vlan100";
authoritative;

subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.1 192.168.0.250;
option domain-name-servers 192.168.0.254;
option routers 192.168.0.254;
option broadcast-address 192.168.0.255;
option subnet-mask 255.255.255.0;
}


I've researched this issue but can't find a definative answer?

Thanks
Anubis.

well your config only has one subnet, are you running the same subnet on two vlan's?? I really hope not. As for what else is wrong, you can see that the INTERFACES line looks totally diffferent from the other lines doesn't it? It does not belong in that file at all, infact I'd have thought that it'd stop DHCPD loading at all as the symtax is totally illegal there. I assume it goes in /etc/sysconfig/dhpcd or similar, something that will be directly turned into a command line argument, not a config inside the program.

Hi Chris,

Thanks for your reply.

I've now added the additional subnets for all of the applicable network interfaces and just by this it is now doing what it should be doing.

I found the 'INTERFACES' part in another forum thread and thought I'd try it. I too find it strange that it allowed the daemon to start properly and it didn't throw up any errors in the syslog. However I've now removed it anyway as it had (obviously) no effect.

Thanks again for your help.
Anubis.