[Dnsmasq-discuss] DHCP server not assigning IP to RTMU86

[Geert Stappers]

On Sat, Jun 04, 2022 at 06:54:18PM +0200, Nicolas Cavallari wrote:
> On 23/05/2022 20:34, Kamil via Dnsmasq-discuss wrote:
> > Dear Nicolas,
> > 
> > I've tried isc-dhcp-server without "authoritative" and it still work fine
> > 
> > 
> >     If anything else fails, use tcpdump/wireshark.
> > 
> > 
> > 
> > I've used tcpdump. I've attached full log in this message:
> > https://www.mail-archive.com/dnsmasq-discuss@lists.thekelleys.org.uk/msg16249.html
> > please have a look.
> 
> There isn't enough information to debug things.  tcpdump only report a DHCP
> message of size 300 without reporting its content, which are important to
> see what's happening.
> 
> Ideally we would need a pcap file.  Censoring information in a pcap file is
> not easy but still possible with a hex editor.  Otherwise you can use
> "tshark -r capture.pcap -V" to output a text representation of the pcap,
> censor the output and give us the result.
> 
> Also, focus on the DHCP exchange with the RTMU86 that does not work.
> We already know how a successful DHCP exchange look like.

Kamil might not know how a successful DHCP exchange looks like.
Having a working example makes it much easier to debug a non-working one.

Thing I'm trying to say, is that it is an interesting problem.
I admit that I don't care about "RTMU86", but I'm really curious about
DHCP-clients that seem to work with some DHCP servers and likely not
with the dnsmasq DHCP server.

So I hope that more information about this case will be shared.


Groeten
Geert Stappers
-- 
Silence is hard to parse