Your message dated Tue, 7 Mar 2023 12:04:38 +0200 with message-id <[email protected]> and subject line This was closed in 1:3.24-1 has caused the Debian Bug report #850424, regarding nbd-server: IPv4 clients not authorized 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 [email protected] immediately.) -- 850424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850424 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nbd-server Version: 1:3.15.1-2 Severity: important Hi! I've just upgraded a server to stretch, and IPv4 connections are rejected as "not authorized". Downgrading nbd-server to 1:3.8-4+deb8u2 makes it work again. The global config is all defaults; the export defines just authfile and exportname. The original authfile that worked on jessie was: .---- 10.0.1.9 2001:6a0:118::9 `---- (redundant, as that's the same client). For simplicity, I've tried single-entry versions: .---- 10.0.1.9 `---- Jan 5 08:29:24 mordor nbd_server[26057]: virtstyle ipliteral Jan 5 08:29:24 mordor nbd_server[26057]: connect from 10.0.1.9, assigned file is /dev/sdd4 Jan 5 08:29:24 mordor nbd_server[26057]: Client '10.0.1.9' is not authorized to access #731626 suggests that, despite what the documentation (both prose and examples) says, single-IP entries require a "/32" appended. That's a bit strange as that bug is from wheezy yet jessie works ok, but indeed the syslog output changes: .---- 10.0.1.9/32 `---- Jan 5 08:39:07 mordor nbd_server[26335]: virtstyle ipliteral Jan 5 08:39:07 mordor nbd_server[26335]: connect from 10.0.1.9, assigned file is /dev/sdd4 Jan 5 08:39:07 mordor nbd_server[26335]: client address does not match 2/10: address family mismatch (IPv4 vs IPv6?) Jan 5 08:39:07 mordor nbd_server[26335]: client address does not match 2/10: address family mismatch (IPv4 vs IPv6?) Jan 5 08:39:07 mordor nbd_server[26335]: client address does not match 2/10: address family mismatch (IPv4 vs IPv6?) Jan 5 08:39:07 mordor nbd_server[26335]: Client '10.0.1.9' is not authorized to access And indeed: tcp TIME-WAIT 0 0 ::ffff:10.0.1.90:10809 ::ffff:10.0.1.9:59800 That's odd as both messages which mention the IP properly decapsulate IPv4, so nbd-server listening on a shared socket shouldn't be a problem. On the other hand, IPv6 works fine (although only when appending "/128", despite what the docs say): .---- 2001:6a0:118::9/128 `---- Jan 5 08:29:40 mordor nbd_server[26061]: virtstyle ipliteral Jan 5 08:29:40 mordor nbd_server[26061]: connect from 2001:6a0:118::9, assigned file is /dev/sdd4 Jan 5 08:29:40 mordor nbd_server[26061]: Starting to serve Jan 5 08:29:40 mordor nbd_server[26061]: Size of exported file/device is 356204412928 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14.77-vs2.3.6.15-x32 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages nbd-server depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-8 ii libglib2.0-0 2.50.2-2 ii libgnutls30 3.5.7-3 ii ucf 3.0036 nbd-server recommends no packages. nbd-server suggests no packages. -- debconf information: nbd-server/convert: true nbd-server/useports: false nbd-server/autogen: nbd-server/filename: nbd-server/port: nbd-server/number: 0 nbd-server/name:
--- End Message ---
--- Begin Message ---Version: 1:3.24-1 This bug was closed upstream with 3.24, but I forgot to mark it as such in the changelog. -- w@uter.{be,co.za} wouter@{grep.be,fosdem.org,debian.org} I will have a Tin-Actinium-Potassium mixture, thanks.
--- End Message ---
