All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13626] New: Can't connect to openssh-server
Date: Wed, 17 Mar 2021 14:49:09 +0000	[thread overview]
Message-ID: <bug-13626-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13626

            Bug ID: 13626
           Summary: Can't connect to openssh-server
           Product: buildroot
           Version: 2021.02
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: posta at debevv.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8806
  --> https://bugs.busybox.net/attachment.cgi?id=8806&action=edit
Client and server logs, defconfig

The openssh-server installed on the board abruptly closes the connection before
the key exchange with the client.
I tried fiddling with ciphers and macs on both sides, changing network
interfaces MTUs (I read online that there are issue related to openssh),
changing client, but the problem persists.
sshd_config is the default one.
I also tried with busybox as init, instead as systemd.
I attached the client and server logs and my defconfig.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-03-17 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 14:49 bugzilla at busybox.net [this message]
2021-03-24 21:48 ` [Buildroot] [Bug 13626] Can't connect to openssh-server bugzilla at busybox.net
2021-08-17 19:02 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13626-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.