From: "Marc-François LUCCA-DANIAU" <mfld.fr@gmail.com>
To: ELKS <Linux-8086@vger.kernel.org>
Subject: Question on ELKS networking maturity
Date: Mon, 20 Feb 2017 12:49:46 +0100 [thread overview]
Message-ID: <CACpuWUnAtCnD2oTHG3CLPEAQMNa0m0gU+HNFLVoyJr7N4s+Nuw@mail.gmail.com> (raw)
Hello all,
While implementing the Ethernet capability in ELKS in collaboration
with Georg, I am getting uncomfortable as we find more and more bugs
in the existing networking stack.
The latest finding is an incorrect management of the sequence numbers
in the TCP layer when accepting incoming connections.
I made the assumption at the beginning that ELKS was reasonably mature
on networking, but obviously I was wrong, and have to revise my
development plan.
So my question to the experienced ones that know the history: what was
the status of the networking features around 2015 ? Were the cmdlets
like httpd, tinyirc, telnet, etc, working with SLIP ? Or was it an
inactive (and so not exercised) part of the project ?
Thanks in advance to provide some background information here,
MFLD
next reply other threads:[~2017-02-20 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 11:49 Marc-François LUCCA-DANIAU [this message]
2017-02-20 12:57 ` Question on ELKS networking maturity Jody Bruchon
2017-02-20 13:41 ` Georg Potthast 2
2017-02-20 15:16 ` Alan Cox
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=CACpuWUnAtCnD2oTHG3CLPEAQMNa0m0gU+HNFLVoyJr7N4s+Nuw@mail.gmail.com \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).