Re: scp dropping connections
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.. sending RSTs to both sides with valid SEQ numbers causing an instant disconnect). Occasionally they will see something in the encrypted data stream (or just the fact that it's encrypted) and shoot down the connection because it violates some network policy (usually just misconfigured to think that). If that's the cause, it's very easy to see it in a packet trace because all the sudden out of nowhere you just see an RST hit you and kill the connection. Then on the opposite (client) side, if you take a trace at the same time, you won't see it actually _sending_ the RST. Thus, you know a NIDS spoofed it. -Swift
Re: Graphics wiki page
On Thu, 7 Apr 2016, co...@sdf.org wrote: > Others have recommended using such a live image when purchasing hardware > like a laptop at a store. That is exactly what I do. I take a USB stick with a copy of NetBSD installed on it into the store and boot it up. Then I simply run startx and watch the action from there. BTW, if there is work to be done with C or shell script to help with any kind of test suite + website idea like this in the future, then I'd be willing to help out a bit. The same goes for hardware. PCIe-wise I have @20 discrete Radeon and 6 Nvidia graphics cards. Most of them work, but some don't. I'd be willing to test them directly or mail them to folks who want to help. There are only 1 or 2 I'd care to get back. Thanks, Swift
Re: scp dropping connections
In article <20160407221122.5a987a60d8b1205bf3a42...@googlemail.com>, Sad Cloudswrote: >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 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. >> >> Martin > >I can reproduce this every time, not sure if this is a bug, or maybe >buggy hardware > >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? christos
Re: Graphics wiki page
On Thu, Apr 07, 2016 at 06:23:38PM +0100, David Brownlee wrote: > What might also be nice would be USB image which could try to fire up > X11 and some relevant app or apps to allow people to perform a quick > "smoke test" to quickly get *some* data points... There is ./build.sh live-image. I think it satisfies your needs. Others have recommended using such a live image when purchasing hardware like a laptop at a store.
Re: Graphics wiki page
On 5 April 2016 at 18:02, Swift Griggswrote: > > On Sun, 3 Apr 2016, co...@sdf.org wrote: > > It would be more fruitful to provide a page where people list hardware > > that works for them, http://dmesgd.nycbug.org is close. > > That's very cool. The idea, in general, reminds me of the supported > hardware database for BeOS back in the day. I got a lot of mileage out of > that. Currently, none of the BSD distros have anything like that which > I'm aware of. I was hoping some of that info would appear in on the wiki > at netbsd.se but then it got taken down and replaced with the official > NetBSD wiki which doesn't seem to get nearly the same amount of love / > content for whatever reason. I think something like dmesgd, but specifically for reporting how well graphics cards (or onboard hardware) works with specific NetBSD versions would be extremely helpful. Particularly if it could have a suggestion on what to test and user settable fields to indicate same. Sounds like a nice standalone site for someone to write :) What might also be nice would be USB image which could try to fire up X11 and some relevant app or apps to allow people to perform a quick "smoke test" to quickly get *some* data points...
Re: scp dropping connections
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. Martin
scp dropping connections
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 logs, but not sure if this is related: sshd: bl_init: connect failed for `/var/run/blsock' (No such file or directory) ultra10# ls -l /var/run total 148 -rw-r--r-- 1 root wheel 4 Apr 7 14:11 cron.pid drwxr-xr-x 2 dbus dbus512 Apr 7 14:11 dbus -rw-r--r-- 1 root wheel 21811 Apr 7 14:09 dev.cdb -rw-r--r-- 1 root wheel 19036 Apr 7 14:10 dmesg.boot -rw-r--r-- 1 root wheel 4 Apr 7 14:11 inetd.pid srw-rw-rw- 1 root wheel 0 Apr 7 14:09 log drwxrwx--- 2 root operator512 Apr 7 14:09 lvm -rw-r--r-- 1 root wheel 3 Apr 7 14:11 ntpd.pid -rw-r--r-- 1 root wheel 5316 Apr 7 14:11 rc.log -rw-r--r-- 1 root wheel 4 Apr 7 14:11 rpc.lockd.pid -rw-r--r-- 1 root wheel 4 Apr 7 14:11 rpc.statd.pid -rw-r--r-- 1 root wheel 4 Apr 7 14:10 rpcbind.pid srwxrwxrwx 1 root wheel 0 Apr 7 14:10 rpcbind.sock -rw-r--r-- 1 root wheel 4 Apr 7 14:11 sshd.pid -rw-r--r-- 1 root wheel 4 Apr 7 14:09 syslogd.pid -rw-r--r-- 1 root wheel 0 Apr 7 14:09 syslogd.sockets -rw-rw-r-- 1 root utmp520 Apr 7 14:11 utmp -rw-rw-r-- 1 root utmp 3120 Apr 7 14:11 utmpx Doe anyone have any idea what may be causing it?