Your message dated Tue, 27 May 2025 00:04:27 +0000 with message-id <e1ujhnv-00b8gu...@fasolo.debian.org> and subject line Bug#1106321: fixed in iproute2 6.15.0-1 has caused the Debian Bug report #1106321, regarding iproute2: "ip monitor" fails with current trixie's linux kernel / iproute2 combination to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1106321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: iproute2 Version: 6.14.0-3 Severity: normal X-Debbugs-Cc: bugs....@free.fr Dear Maintainer, Having iproute2 >= 6.14 while running a linux kernel < 6.14 triggers this bug (tested using debian-13-nocloud-amd64-daily-20250520-2118.qcow2) root@localhost:~# ip monitor Failed to add ipv4 mcaddr group to list More specifically this subcommand, which didn't exist in iproute2 6.13 is affected: root@localhost:~# ip mon maddr Failed to add ipv4 mcaddr group to list root@localhost:~# ip -6 mon maddr Failed to add ipv6 mcaddr group to list causing the generic "ip monitor" command to fail. As trixie will use a 6.12.x kernel, trixie is affected. bookworm's iproute2/bookworm-backports is also affected since currently bookworm's backport kernel is also 6.12.x Workarounds: * upgrade the kernel to experimental's (currently) 6.14.6-1~exp1 * downgrade iproute2 to 6.13.0-1 (using snapshot.d.o) * on bookworm downgrade (using snapshot.d.o) iproute2 backport to 6.13.0-1~bpo12+1 Details I could gather: This appears to come from this iproute2 6.14's commit: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?h=v6.14.0&id=7240e0e40f8332dd9f11348700c0c96b8df4ca5b which appears to depend on new kernel 6.14 rtnetlink features as described in Kernelnewbies ( https://kernelnewbies.org/Linux_6.14#Networking ): Add ipv6 anycast join/leave notifications with this (kernel 6.14) commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=33d97a07b3ae6fa713919de4e1864ca04fff8f80 I guess to fix this one could: * backport (or have upstream backport) the kernel feature to 6.12.x, * or supply iproute2 6.13 instead of iproute 6.14 for trixie with some versioning trick, * or patch iproute2 to cope with a kernel not having the API changes Regards, Adel Belhouane. -- System Information: Debian Release: 13.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.27-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iproute2 depends on: ii debconf [debconf-2.0] 1.5.91 ii libbpf1 1:1.5.0-3 ii libc6 2.41-7 ii libcap2 1:2.75-7 ii libcap2-bin 1:2.75-7 ii libdb5.3t64 5.3.28+dfsg2-9 ii libelf1t64 0.192-4 ii libmnl0 1.0.5-3 ii libselinux1 3.8.1-1 ii libtirpc3t64 1.3.6+ds-1 ii libxtables12 1.8.11-2 iproute2 recommends no packages. Versions of packages iproute2 suggests: ii python3 3.13.3-1 -- debconf information excluded
--- End Message ---
--- Begin Message ---Source: iproute2 Source-Version: 6.15.0-1 Done: Luca Boccassi <bl...@debian.org> We believe that the bug you reported is fixed in the latest version of iproute2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1106...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi <bl...@debian.org> (supplier of updated iproute2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 27 May 2025 00:16:26 +0100 Source: iproute2 Architecture: source Version: 6.15.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team <debian-ker...@lists.debian.org> Changed-By: Luca Boccassi <bl...@debian.org> Closes: 1106321 Changes: iproute2 (6.15.0-1) unstable; urgency=medium . * Update upstream source from tag 'upstream/6.15.0' (Closes: #1106321) * Drop all backported patches, merged upstream * d/copyright: use GPL URL instead of old FSF postal address Checksums-Sha1: 0920d40c5aa69058162996adece07099462d057b 2348 iproute2_6.15.0-1.dsc 5f0d837dbbc803bfd3658e87e504875c0d819d74 930908 iproute2_6.15.0.orig.tar.xz ba763dbc01baae890a2484938ab3e14f59b60945 39920 iproute2_6.15.0-1.debian.tar.xz bbb305cb7be15012cc1e5b08033734072b7ea5b6 6872 iproute2_6.15.0-1_source.buildinfo Checksums-Sha256: 2558690474d6cdda5e2c4022b520935623ddd41fbf8e936315e3f4314f6f21dd 2348 iproute2_6.15.0-1.dsc 8041854a882583ad5263466736c9c8c68c74b1a35754ab770d23343f947528fb 930908 iproute2_6.15.0.orig.tar.xz 780375193dffeb85f310a918b806f2f4e480f76b815a1f0f1eac5d0488ea1a8f 39920 iproute2_6.15.0-1.debian.tar.xz ff8b51f8d7c279a25c8f6824b6ac69046303d4e5b36566bea2f697f9b5f962bd 6872 iproute2_6.15.0-1_source.buildinfo Files: ff32f139ab598ae72a0356c848dada9c 2348 net optional iproute2_6.15.0-1.dsc d85d77deed57e055cb2d1409595a6348 930908 net optional iproute2_6.15.0.orig.tar.xz d113e76b6f0042545934917d84cec1b7 39920 net optional iproute2_6.15.0-1.debian.tar.xz 4b806cca2bb9022859f34bb8a8f66caa 6872 net optional iproute2_6.15.0-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmg0/T8RHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB4XKA//eTlyI0TuvD38sZ098FC4KtnZ3q9M1Bvk XRH8RFkfua8UsAxIPXJoVyQ6zEM5L/BfND3oVeVRJ73FsQ9Hs0KE8wDKh1sbwY2a 6u6NZhg/bEXC1uOJ84tRHfhn9t7yOo4qwnGzvFPL4+rUalTTJ6jhbquJ47AKJz3Y n/mP7W/TCUZrUNJDU/k26c0AUJxaL2pJAnFkCNLR6oORIFipPqXQe7EZiMcmvfPk X5GzD5Fh/aIBPuAIrbveYMXeOxMsXJaCCNjxxUePffK+zgBvlDLKdDhlU+X7fqJs nFgpnuxChempwaEthmLNZUHD23HWis0H1gznfWhusvygqdPQGMs5kYyr56dPKO0g TLxWoeGNqvBOvWPwzHD0DLNufwxiliJgRaKLqb9luHbZCWSYCeDmLLaup551V6Hg UVMmav3RKSi1nzm6grLmKy8VadpOYLcuGXtXaSKAMdNaCHmxxR+GHO2f+SKAoITe 2acdlLofPbnoDD4uBGkY3sKd2QKn9jhNuHqrqWDVUIEtL45zIsUIMJkGMuwsm0qi Dokv7yT/fdezTGYl6SmH9zNndNcF1uOthRfHlj70kDCGjD4OH029ZV1VP2Lu1jhQ NMq3rd9VAwPPuZat0+ZR5FGoTmdDcJyfKB/+ehk3PiOR0oBobOxdZ2iTFYAXb95b VO6RsduZcac= =4e8k -----END PGP SIGNATURE-----
pgp2M3ffJ2i6c.pgp
Description: PGP signature
--- End Message ---
