Bug#850424: nbd-server: IPv4 clients not authorized

Package: nbd-server Version: 1:3.20-1 Followup-For: Bug #850424 By the way, the auth file accepts the "mixed" format for v6-mapped v4 addresses. So, for example, 192.168.1.23 can be entered as :::192.168.1.23 instead of having to work out the hex bytes. But don't forget that if you specify

Bug#850424: nbd-server: IPv4 clients not authorized

Control: forwarded -1 https://github.com/NetworkBlockDevice/nbd/issues/35 This issue bit me today. The workaround suggested in the upstream bugreport works. If you have "10.1.1.10" in your authfile and have no IPV6 set up, add the IPv6-mapped address ":::0a01:010a/128" -- dam

Bug#850424: nbd-server: IPv4 clients not authorized

Hello Wouter, Adam, * Adam Borowski [06. Jan. 2017]: > Package: nbd-server > Version: 1:3.15.1-2 > Severity: important This is still the case with nbd-server 1:3.16.2-1 as in today's debian/buster. I provided an authfile containing the ip address of my client

Bug#850424: nbd-server: IPv4 clients not authorized

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