single dhcp server with multiple subnets

[Senko, Mike]

Spent the day yesterday working on the issue and decided to break the network down to more basic elements
to try to at least cross vlans for dhcp requests.

I reconfigured the network so both the dhcp server and dhcp client are on the same network switch.

I placed the dhcp server in vlan6, as before and placed the dhcp client in vlan 7 (or 8 or 5). 
The DHCP server receives the dhcp request and assigns an address, always for its own vlan, vlan6 as evidenced in the syslog
messages.

It suggests the dhcp relay agent is not passing on the vlan/subnet information from the client. I don't know what else to think
at the moment.

This is my first time setting up a dhcp server, if anyone can critique the dhcpd.conf configuration I can at least eliminate that from my troubleshooting. I have attached both the Config and syslog outputs to this email.

Thanks,

Mike

-----Original Message-----
From: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] On Behalf Of Simon Hobson
Sent: Tuesday, July 29, 2014 12:16 AM
To: Users of ISC DHCP
Subject: Re: single dhcp server with multiple subnets

"Senko, Mike" <Mike.Senko at seattle.gov> wrote:

> Jul 28 11:48:06 TestLabPC dhcpd: DHCPDISCOVER from b4:b5:2f:29:d1:c9 
> (SCL2304L) via 10.1.6.2 Jul 28 11:48:07 TestLabPC dhcpd: DHCPOFFER on 
> 10.1.6.200 to b4:b5:2f:29:d1:c9 (SCL2304L) via 10.1.6.2

> 13:00:53.378085 IP 10.1.6.2.43408 > 10.1.6.56.bootps: BOOTP/DHCP, 
> Request from b4:b5:2f:29:d1:c9 (oui Unknown), length 303
> 13:00:54.379236 IP 10.1.6.56.bootps > 10.1.6.2.bootps: BOOTP/DHCP, 
> Reply, length 300

> If I connect the laptop to the same switch as the dhcp server switch, 
> vlan6 (10.1.6.0/24), the laptop picks up the address 10.1.6.200 - as 
> expected

It looks like you still do not have your network setup correctly. I know from experience that some switches are "not very intuitive" when setting up VLANs :(

I would suggest manually configuring 1 or more devices with IP addresses appropriate to the network they *should* be in and get the network correct. Once you fix that then you should find the DHCP "just works".
_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dhcpd.conf
Type: application/octet-stream
Size: 4494 bytes
Desc: dhcpd.conf
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20140730/26a3b894/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syslog
Type: application/octet-stream
Size: 287751 bytes
Desc: syslog
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20140730/26a3b894/attachment-0003.obj>