On Fri, 8 Apr 2016 12:03:43 + (UTC)
chris...@astron.com (Christos Zoulas) wrote:
> In article <20160408090513.d1d9cd1ea02ea764e0a1b...@googlemail.com>,
> Sad Clouds wrote:
> >On Thu, 7 Apr 2016 10:48:28 -0600 (MDT)
> >Swift Griggs
In article <20160408090513.d1d9cd1ea02ea764e0a1b...@googlemail.com>,
Sad Clouds wrote:
>On Thu, 7 Apr 2016 10:48:28 -0600 (MDT)
>Swift Griggs wrote:
>
>> On Thu, 7 Apr 2016, Christos Zoulas wrote:
>> > >I attached gdb on sparc64 to sshd
On Fri, Apr 08, 2016 at 09:05:13AM +0100, Sad Clouds wrote:
> So I'm inclined to think it's either hme0 hardware issue, or NetBSD
> kernel bug.
Ah, hme driver bug - the sparc64 machines I use most heavily have other
network interfaces. I'll try to reproduce it on a machine with hme.
Martin
On Thu, 7 Apr 2016 10:48:28 -0600 (MDT)
Swift Griggs wrote:
> On Thu, 7 Apr 2016, Christos Zoulas wrote:
> > >I attached gdb on sparc64 to sshd process and after 30 seconds got
> > >the following
> > Do you have a NAT/firewall and you don't have keep state in your
> > pass
On Thu, 7 Apr 2016, Christos Zoulas wrote:
> >I attached gdb on sparc64 to sshd process and after 30 seconds got the
> >following
> Do you have a NAT/firewall and you don't have keep state in your pass rules?
I've also seen misconfigured NIDS system that are setup for TCP
"shootdown" (ie..
In article <20160407221122.5a987a60d8b1205bf3a42...@googlemail.com>,
Sad Clouds wrote:
>On Thu, 7 Apr 2016 15:46:51 +0200
>Martin Husemann wrote:
>
>> On Thu, Apr 07, 2016 at 02:35:59PM +0100, Sad Clouds wrote:
>> > sshd: bl_init: connect
On Thu, Apr 07, 2016 at 02:35:59PM +0100, Sad Clouds wrote:
> sshd: bl_init: connect failed for `/var/run/blsock' (No such file or
> directory)
That is the connection to blacklistd (which you probably are not running).
Should be unrelated. I don't see any such issues on my sparc64 machines.
I've just upgraded my sparc64 machine to latest NetBSD-7 and unable to
scp large files to this machine, as ssh keeps dropping connections after
some time.
src.tar
9% 262MB 1.2MB/s 1.3MB/s 36:01 ETA
Connection to ultra10 closed by remote host. lost connection
I see the following in the