Re: dhcpcd failure

[Roy Marples <roy%marples.name@localhost>]

On 21/02/2019 17:02, triaxx wrote:
> Le 2019-02-21 17:52, Roy Marples a écrit :
> > On 21/02/2019 16:45, triaxx wrote:
> > > As least cisco respects -J but it doesn't fix the problem.
> > >
> > > 16:40:06.514754 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], 
> > > proto UDP (17), length 576)
> > >      192.168.0.1.bootps > 255.255.255.255.bootpc: [udp sum ok] 
> > > BOOTP/DHCP, Reply, length 548, xid 0xe090f980, Flags [Broadcast] 
> > > (0x8000)
> > >        Your-IP 192.168.0.11
> > >        Server-IP 192.168.0.1
> > >        Client-Ethernet-Address 80:ee:73:c1:cd:36 (oui Unknown)
> > >        Vendor-rfc1048 Extensions
> > >          Magic Cookie 0x63825363
> > >          DHCP-Message Option 53, length 1: Offer
> > >          Server-ID Option 54, length 4: 192.168.0.1
> > >          Lease-Time Option 51, length 4: 86400
> > >          Subnet-Mask Option 1, length 4: 255.255.255.0
> > >          Default-Gateway Option 3, length 4: 192.168.0.1
> > >          Domain-Name-Server Option 6, length 4: 192.168.0.1
> > >          Domain-Name Option 15, length 11: "atlas.local"
> > >          END Option 255, length 0
> > >          PAD Option 0, length 0, occurs 261
> >
> > So it's now broadcast which is good.
> > Does dhcpcd not see that?
> >
> > Roy
> > No, it does not.

Does it log anything about a reply with the debug flag set? -d