Hello Pawel,

Thank you for reporting this issue.  I am not sure about the problem you're
reporting; there were a number of patches applied to the atftpd sources in this
release.  Could you test with the version here?

http://people.debian.org/~tmancill/atftpd_0.7.dfsg-9.3~squeeze1_i386.deb

This is a proposed update for the version in squeeze.

Thank you,
tony

On 02/15/2011 12:45 PM, Paweł Różański wrote:
> Package: atftpd
> Version: 0.7.dfsg-9.1
> Severity: normal
> 
> --- Please enter the report below this line. ---
> 
>  After system upgrade from Lenny to Squeeze, atftpd stopped to send
> files to some clients. These clients use tftp from busybox (version
> BusyBox v1.8.2; embedded hardware). Other clients (tftp 0.17-18 from
> Squeeze) in the same subnet seem to work fine.
>  Atftpd is run with:
> /usr/sbin/atftpd --tftpd-timeout 300 --retry-timeout 5 --no-multicast
> --maxthread 100 --verbose=5 --daemon --bind-address 212.67.x.x --pidfile
> /atftpd_212.67.x.x.pid /opt/212.67.x.x
> 
> Dump of traffic:
> 2011-02-09 16:30:02.428049 172.18.x.x -> 212.67.x.x TFTP Read Request,
> File: device.cfg\000, Transfer type: octet\000
> 2011-02-09 16:30:02.432206 212.67.y.y -> 172.18.x.x UDP Source port:
> 39806  Destination port: 2048
> 2011-02-09 16:30:02.435420 172.18.x.x -> 212.67.x.x TFTP
> Acknowledgement, Block: 1
> 2011-02-09 16:30:02.435474 212.67.x.x -> 172.18.x.x ICMP Destination
> unreachable (Port unreachable)
> 2011-02-09 16:30:02.485345 172.18.x.x -> 212.67.x.x TFTP
> Acknowledgement, Block: 1
> 2011-02-09 16:30:02.485409 212.67.x.x -> 172.18.x.x ICMP Destination
> unreachable (Port unreachable)
> 2011-02-09 16:30:02.560398 172.18.x.x -> 212.67.x.x TFTP
> Acknowledgement, Block: 1
> 2011-02-09 16:30:02.560482 212.67.x.x -> 172.18.x.x ICMP Destination
> unreachable (Port unreachable)
> 2011-02-09 16:30:02.672413 172.18.x.x -> 212.67.x.x TFTP
> Acknowledgement, Block: 1
> 2011-02-09 16:30:02.672471 212.67.x.x -> 172.18.x.x ICMP Destination
> unreachable (Port unreachable)
> 2011-02-09 16:30:02.840339 172.18.x.x -> 212.67.x.x TFTP
> Acknowledgement, Block: 1
> 
> Interesting thing is 2011-02-09 16:30:02.432206 212.67.y.y -> 172.18.x.x
> UDP Source port: 39806  Destination port: 2048
> 
> 212.67.y.y is other than 212.67.x.x, but still existing on this machine.
> 
> Returning to 0.7.dfsg-6 from Lenny on this upgraded system solved the
> problem, that's why I guess problem may be with atftpd.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to