Bug#834832: listen on [::]:69 works only once

2016-08-20 Thread Marc Haber
On Sat, Aug 20, 2016 at 08:34:11AM +0930, Ron wrote:
> Are you really running 5.2+20150808-1 on the machine where you are
> seeing this

No. I filed this in a hurry.



Bug#834832: listen on [::]:69 works only once

2016-08-19 Thread Ron

Hi Marc,

On Fri, Aug 19, 2016 at 05:09:58PM +0200, Marc Haber wrote:
> Package: tftpd-hpa
> Version: 5.2+20150808-1
> Severity: normal
> Tags: ipv6
> 
> Hi,
> 
> /usr/sbin/in.tftpd --listen --user tftp --address [::]:69 --secure /srv/tftp
> 
> serves only the first request. All subsequent requests result in "Aug
> 19 17:07:08 weave in.tftpd[13781]: connect: Address family not
> supported by protocol" written to the syslog and the request times out.
> 
> After restarting the process, exactly one request is served again.
> 
> setting --address 0.0.0.0:69 probably turns off IPv6, but makes IPv4
> work reliably. I don't think this is the itended behavior.

I think you're going to need to provide a bit more information about
exactly what you are doing here (like what address you are connecting
from at least) ...

"Only serves the first request" seems like a rather odd failure mode,
which makes me think you're not connecting the same way for the
subsequent requests ...


Are you really running 5.2+20150808-1 on the machine where you are
seeing this, since there was an issue with IPv4 mapped IPv6 addresses
that should have been fixed in that release (see #793921).

  Cheers,
  Ron



Bug#834832: listen on [::]:69 works only once

2016-08-19 Thread Marc Haber
Package: tftpd-hpa
Version: 5.2+20150808-1
Severity: normal
Tags: ipv6

Hi,

/usr/sbin/in.tftpd --listen --user tftp --address [::]:69 --secure /srv/tftp

serves only the first request. All subsequent requests result in "Aug
19 17:07:08 weave in.tftpd[13781]: connect: Address family not
supported by protocol" written to the syslog and the request times out.

After restarting the process, exactly one request is served again.

setting --address 0.0.0.0:69 probably turns off IPv6, but makes IPv4
work reliably. I don't think this is the itended behavior.

Greetings
Marc