<div dir="ltr">Did you saw that this file contains password information, don't you?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-07-30 13:33 GMT-03:00 Senko, Mike <span dir="ltr"><<a href="mailto:Mike.Senko@seattle.gov" target="_blank">Mike.Senko@seattle.gov</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The switch configuration is attached.<br>
<br>
It's really pretty basic, it's a rugged com switch, menu driven/selection. I've configured the dhcp relay agent and the ports where the clients and server reside. Hmm, I'll move the server to a different port to differentiate client/server a little more but have low expectations for success.<br>
<span class="HOEnZb"><font color="#888888"><br>
Mike<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: <a href="mailto:dhcp-users-bounces@lists.isc.org">dhcp-users-bounces@lists.isc.org</a> [mailto:<a href="mailto:dhcp-users-bounces@lists.isc.org">dhcp-users-bounces@lists.isc.org</a>] On Behalf Of Joseph Bernard<br>
Sent: Wednesday, July 30, 2014 8:48 AM<br>
To: Users of ISC DHCP<br>
Subject: Re: single dhcp server with multiple subnets<br>
<br>
Can you attach the config for your switch?<br>
<br>
Thanks,<br>
Joseph B.<br>
<br>
On Jul 30, 2014, at 11:40 AM, Senko, Mike <<a href="mailto:Mike.Senko@seattle.gov">Mike.Senko@seattle.gov</a>> wrote:<br>
<br>
> Spent the day yesterday working on the issue and decided to break the<br>
> network down to more basic elements to try to at least cross vlans for dhcp requests.<br>
><br>
> I reconfigured the network so both the dhcp server and dhcp client are on the same network switch.<br>
><br>
> I placed the dhcp server in vlan6, as before and placed the dhcp client in vlan 7 (or 8 or 5).<br>
> The DHCP server receives the dhcp request and assigns an address,<br>
> always for its own vlan, vlan6 as evidenced in the syslog messages.<br>
><br>
> It suggests the dhcp relay agent is not passing on the vlan/subnet<br>
> information from the client. I don't know what else to think at the moment.<br>
><br>
> 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.<br>
><br>
> Thanks,<br>
><br>
> Mike<br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:dhcp-users-bounces@lists.isc.org">dhcp-users-bounces@lists.isc.org</a><br>
> [mailto:<a href="mailto:dhcp-users-bounces@lists.isc.org">dhcp-users-bounces@lists.isc.org</a>] On Behalf Of Simon Hobson<br>
> Sent: Tuesday, July 29, 2014 12:16 AM<br>
> To: Users of ISC DHCP<br>
> Subject: Re: single dhcp server with multiple subnets<br>
><br>
> "Senko, Mike" <<a href="mailto:Mike.Senko@seattle.gov">Mike.Senko@seattle.gov</a>> wrote:<br>
><br>
>> Jul 28 11:48:06 TestLabPC dhcpd: DHCPDISCOVER from b4:b5:2f:29:d1:c9<br>
>> (SCL2304L) via 10.1.6.2 Jul 28 11:48:07 TestLabPC dhcpd: DHCPOFFER on<br>
>> 10.1.6.200 to b4:b5:2f:29:d1:c9 (SCL2304L) via 10.1.6.2<br>
><br>
>> 13:00:53.378085 IP 10.1.6.2.43408 > 10.1.6.56.bootps: BOOTP/DHCP,<br>
>> Request from b4:b5:2f:29:d1:c9 (oui Unknown), length 303<br>
>> 13:00:54.379236 IP 10.1.6.56.bootps > 10.1.6.2.bootps: BOOTP/DHCP,<br>
>> Reply, length 300<br>
><br>
>> If I connect the laptop to the same switch as the dhcp server switch,<br>
>> vlan6 (<a href="http://10.1.6.0/24" target="_blank">10.1.6.0/24</a>), the laptop picks up the address 10.1.6.200 - as<br>
>> expected<br>
><br>
> It looks like you still do not have your network setup correctly. I<br>
> know from experience that some switches are "not very intuitive" when<br>
> setting up VLANs :(<br>
><br>
> 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".<br>
> _______________________________________________<br>
> dhcp-users mailing list<br>
> <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
> <dhcpd.conf><syslog>_______________________________________________<br>
> dhcp-users mailing list<br>
> <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</div></div><br>_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br></blockquote></div><br></div>