|
From: Ralph B. <sl...@sa...> - 2016-10-24 10:49:41
|
On Mon, Oct 24, 2016 at 01:03:47PM +0300, ILIV wrote: > > > On Oct 24, 2016, at 12:08 PM, Ralph Böhme <sl...@sa...> wrote: > > > > On Mon, Oct 24, 2016 at 10:43:22AM +0300, ILIV wrote: > >>> On Oct 24, 2016, at 10:04 AM, Ralph Böhme <sl...@sa... <mailto:sl...@sa...>> wrote: > >>> ... > >>> I need network traces of disconnects (ie when Netatalk logs > >>> "dsi_stream_read: len:0, unexpected EOF") to determine what we're > >>> doing wrong that causes the client to disconnect. > >> > >> I should be able to help. > >> > >> How detailed should it be? If you could suggest tcpdump flags I > >> would be happy to run it for you. > > > > raw packets, so > > > > # tcpdump -w afp.pcap -i INTERFACE -s 0 port 548 > > > > INTERFACE must be substituted by the network interface name over which > > the client connects. > > Here you go > https://www.dropbox.com/s/5pdjum41ktbhe48/afp.pcap.tar.bz2?dl=0 > <https://www.dropbox.com/s/5pdjum41ktbhe48/afp.pcap.tar.bz2?dl=0> looks like the second xattr related issue that should be fixed by the proposed patch in the mail I mentioned (reattaching for convenience). Can you please test with that patch and if it still fails do another trace? -slow |