Network error: Software caused connection abort

[Christopher Hansen]

My ssh connections to my beaglebone black crash periodically and I get this error in my ssh window.  Any ideas to keep this from happening?  I'm running debian with kernel 4.14.71-ti-r80 on the bone.  I connect in from a windows machine running MobaXterm.

Thanks.

Chris

[Dennis Lee Bieber]

On Fri, 24 Jul 2020 11:10:31 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Christopher Hansen

Not enough information to tell -- ie; /what/ software?

If it was something on the Beagle, I'd think checking log files might
show something.

OTOH: Maybe it is something in your MobaXterm crashing. Have you tried
PuTTY?


--
Dennis L Bieber

[Robert Nelson]

On Fri, Jul 24, 2020 at 1:10 PM Christopher Hansen <hans...@gmail.com> wrote:
>
> My ssh connections to my beaglebone black crash periodically and I get this error in my ssh window. Any ideas to keep this from happening? I'm running debian with kernel 4.14.71-ti-r80 on the bone. I connect in from a windows machine running MobaXterm.

Was this network connected over USB or Ethernet? (Or WIFi with an adapter?)

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Christopher Hansen]

It's ethernet. 

Chris

[Christopher Hansen]

I didn't see anything on dmesg.  I'll look for other log files.

Chris

[jonnymo]

You might want to check the host that is running MobaXterm.  Also, have a look at the Moba site for some hints:

https://mobaxterm.mobatek.net/documentation.html#6_8_3

Cheers,

Jon

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/117f42cd-9c05-4e2f-b4fe-3c76fb7789c4n%40googlegroups.com.

[Christopher Hansen]

Thanks - I followed this instruction in MobaXterm and that seemed to fix it:

This is usually the result of a packet filter or NAT device timing out your TCP connection due to inactivity. You can check the "Enable SSH keepalive" box under "Settings" --> "Configuration" --> "SSH" tab.
Enabling this option will ensure that the connection is kept "fresh" in the device's connection table.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkpCRZzzkTdiw1zDwNvwu02xzRYORQbVM3GiWpPqj5Q%3D-A%40mail.gmail.com.