Hi,
On Fri, 20 Feb 2015, Sten Spans wrote:
>
> We've been quite happily using the option82 support with
> ISC DHCPD 4.2.6 and a configuration similar to the following:
>
<snipp/>
>
> However if I manually generate a request (via tcpreplay)
> which looks like this:
>
<snipp/>
> Then I get:
>
> Feb 20 14:37:14 mccmdns2 dhcpd: DHCPDISCOVER from e8:39:35:26:63:8e
> circuit-id mccx-c1-p1-sw1 remote-id 1:7:6d:63:63:78:73:77:35 via 172.16.0.130
> Feb 20 14:37:14 mccmdns2 dhcpd: DHCPOFFER on 172.16.0.131 to
> e8:39:35:26:63:8e via 172.16.0.130
>
> Anybody got a clue what's going wrong here?
> I've been trying to spot the issue using the source,
> but haven't been able to come up with anything so far.
where did you capture the first packet trace ?
Are you sure all the data is getting to the dhcp server.
Some switches or other relay agents might clean out you circuit id
before getting to the dhcp server.
Be sure to capture on the dhcp server to see exactly what gets through
to it.
Greetings
Christian
--
Christian Kratzer CK Software GmbH
Email:
[hidden email] Wildberger Weg 24/2
Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden
Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart
Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer
Web:
http://www.cksoft.de/_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Locked
