From: Max Seidenstuecker <naturally-aligned@web.de>
To: ecos-devel@ecos.sourceware.org
Subject: FreeBSD TCP/IP stacks update to newer version possible?
Date: Thu, 28 Mar 2013 16:03:00 -0000 [thread overview]
Message-ID: <CAASVbFFr5_TCuypUQauNo7J3zVMo9VQDC-udp1Yqfq51nLnaVw@mail.gmail.com> (raw)
Hello everyone,
for a research project our company is aiming to use eCos on the target
hardware. The major requirement is a working IPv6 implementation and
TLS/SSL. In eCos there is a FreeBSD-based TCP/IP stack and an OpenSSL
implementation available.
I see so many changes in the KAME project (FreeBSD IPv6 base) that I
am wondering if the version in eCos is stable enough. Has anyone got a
summary of the changes between 2001 and 2006 where the project
concluded? So we can see if an update is needed or worth doing.
What would the tasks be to update an already ported stack? I would
rate myself as a rookie in the area of network and OS related
programming. But from what I saw in the code it seems like there is an
compatibilty layer (eCos wrapper) provided for easy updates to the
code. Would a copy/paste job and some minor adjustments to the code do
the trick then?
Sincerely,
Max
next reply other threads:[~2013-03-28 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 16:03 Max Seidenstuecker [this message]
2013-03-29 9:13 ` Lambrecht Jürgen
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=CAASVbFFr5_TCuypUQauNo7J3zVMo9VQDC-udp1Yqfq51nLnaVw@mail.gmail.com \
--to=naturally-aligned@web.de \
--cc=ecos-devel@ecos.sourceware.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).