Date: Sun, 11 Jun 2017 14:23:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 219927] awg0 stops working after a long output under ssh Message-ID: <bug-219927-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219927 Bug ID: 219927 Summary: awg0 stops working after a long output under ssh Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: hlh@restart.be Environment: pine64+ 2GB FreeBSD norquay.restart.bel 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318945M: = Sat Jun 10 11:47:44 CEST 2017=20=20=20=20 root@norquay.restart.bel:/usr/obj/usr/src/sys/NORQUAY arm64 If I connect from a wireless computer (FreeBSD 11.1-PRERELEASE #0 r318860) = and run a command with a big output (eg `find /`) the awg0 stops working quickly (under 20 seconds of output). If I do the same with telnet from the same computer, the output is much lon= ger but awg0 stops working. If I do the same from a wired computer then I must run `find /` 2 or 3 times before awg0 stops working. I can rsync through ssh 12GB without problem in both directions (from and to the pine64 and the wireless computer). I have a `tcpdump -w ssh.data port 22`. (8.3 MB) I can connect with a serial console to the pine64 after awg0 stop working. ifconfig awg0 down ifconfig awg0 up don't restore the connectivity. I must reboot to restore connectvity. Henri --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219927-7>