su 16. kesäk. 2024 klo 9.05 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> la 15. kesäk. 2024 klo 16.55 Nicolas Cavallari
> (nicolas.cavall...@green-communications.fr) kirjoitti:
> >
> > On 15/06/2024 11:33, Martin-Éric Racine wrote:
> > > On Tue, 29 Aug 2023 13:17:51 +0200 Nicolas Cavallari
> > >> This affects version 9.4.1-22 (stable) and 1:9.4.1-24~deb12u2
> > >> (stable proposed update) but not 1:10.0.2-4 (testing/unstable) as
> > >> upstream fixed it in 10.0.2:
> > >>
> > >> Upstream Bug report: 
> > >> https://github.com/NetworkConfiguration/dhcpcd/issues/179
> > >> Upstream Fix: 
> > >> https://github.com/NetworkConfiguration/dhcpcd/commit/8b29c0ddf026c1c5647c3b8c6cfe21699c4056ae
> > >>
> > >> This patch does not apply cleanly to 9.4.1 because the privsep
> > >> structure changed in 10.0.2.  It's likely that only the src/privsep.c
> > >> hunks about len == 0 and eloop_exit() needs to be backported, the other
> > >> changes are just here to avoid compiler warnings about unused
> > >> parameters.
> > >
> > > Upstream got around releasing a backport of this for branch 9 as
> > > commits 53e2f6de4ba87d0534c89cae674e6c1a48724ef0 and
> > > 6e127eac6903524d401b31893167e4529b8ab111 respectively.
> > >
> > > You are hereby invited to test and report whether this fixes it for 
> > > Stable.
> >
> > I did some quick tests on a VM:
> >
> > First, with 9.4.1-24~deb12u3 as present in debian stable:
>
> > Then I apt sourced dhcpcd, applied the two patches, rebuilt debian
> > packages and tested them.  The situation is now worse:
>
> > I then tested this patch from issue #283:
> >
> > https://github.com/NetworkConfiguration/dhcpcd/commit/727c78f503d456875e2a3cee7609288b537d9d25.patch
> >
> > And this time, it appears to fix the problem:
>
> > I didn't check if there were any adverse effect or if leases are still
> > renewed. I can't check on the production system before Monday.
>
> Please let me know.

Any news on this?

Martin-Éric

Reply via email to