On Sun, 20 Apr 2025 19:58:53 +0300 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> wrote: > Hey Daniel, > On Wed, 16 Apr 2025 07:55:52 +0300 > =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> > wrote: > > On Mon, 03 Mar 2025 17:37:21 +0100 =?utf-8?q?Daniel_Gr=C3=B6ber?= > > <d...@darkboxed.org> wrote: > > > Package: dhcpcd > > > Version: 1:9.4.1-24~deb12u4 > > > Severity: normal > > > X-Debbugs-Cc: d...@darkboxed.org > > > > > > Hi Martin, > > > > > > I have the following RAs on my network including multiple DNSSL > > > options. According to [RFC 8106 section 5.2] > > > > > > > If it is desirable to have different Lifetime values, multiple DNSSL > > > > options can be used. > > > > > > [RFC 8106]: https://datatracker.ietf.org/doc/html/rfc8106#section-5.2 > > > > > > So this should be supported. However dhcpcd doesn't merge the > > > lists only installing the first one in /etc/resolv.conf: > > > > > > search rack.dxld.at dyn.dxld.at pub.dxld.at > > > > > > I tested against rdnssd (after undoing dhcpcd's sysctl mangling [#266] > > > another issue we'll have to deal with later) and it get's it right. > > > Looking at /var/run/rdnssd/resolv.conf: > > > > > > search rack.dxld.at dyn.dxld.at pub.dxld.at inn.dxld.at > > > > > > [#266]: https://github.com/NetworkConfiguration/dhcpcd/issues/266 > > > > > > Except... I actually wanted a different order, but we can't have > > > everything as that seems to be RFC compliant :-) > > > > Does this upstream commit fix the issue for you: > > > > https://github.com/NetworkConfiguration/dhcpcd/commit/dabdf5728e5b419c3a23f8e2bf21e344f29cbf43 > > Can you confirm?
Ping? Martin-Éric
