From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9542 invoked by alias); 29 Mar 2013 09:13:44 -0000 Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org Received: (qmail 9093 invoked by uid 89); 29 Mar 2013 09:13:35 -0000 X-Spam-SWARE-Status: No, score=3.8 required=5.0 tests=AWL,BAYES_50,BOTNET,KHOP_THREADED,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.1 Received: from ip2.televic.com (HELO ip2.televic.com) (81.82.194.222) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 29 Mar 2013 09:13:31 +0000 Received: from SRV-VS06.TELEVIC.COM ([10.0.0.46]) by SRV-VS06.TELEVIC.COM ([10.0.0.46]) with mapi; Fri, 29 Mar 2013 10:13:28 +0100 From: =?iso-8859-1?Q?Lambrecht_J=FCrgen?= To: Max Seidenstuecker CC: "ecos-devel@ecos.sourceware.org" Date: Fri, 29 Mar 2013 09:13:00 -0000 Subject: Re: FreeBSD TCP/IP stacks update to newer version possible? Message-ID: <51555B37.4010804@televic.com> References: In-Reply-To: user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2013-03/txt/msg00006.txt.bz2 On 03/28/2013 05:03 PM, Max Seidenstuecker wrote: > 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. Why not LwIP? It also has IPv6. Mark, we are also still using freeBSD, and I still have to evaluate LwIP=20 against our needs.. > > 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? I think it will be more than that.. I don't know really the Kame project, but it was also for FreeBSD, a PC=20 network stack. So it must be adapted to embedded use. Here for example 2 issues that I discovered in the eCos freeBSD port=20 that you don't see on a PC: - by default the maximum fragmented packet size is 9kB (instead of 64kB) - at ARP request timeout, only 1 packet is buffered. So if you are doing=20 network bandwith testing with UDP messages, you will loose packets every=20 5 minutes (default ARP timeout) I was also thinking of doing something like that, but only to add VLAN=20 tagging support to eCos. But I can also use our switch chip to add VLAN tags as workaround. So=20 that task is not so urgent anymore... I am interested in helping, but I have only limited time. Kind regards, J=FCrgen > > Sincerely, > Max --=20 J=FCrgen Lambrecht R&D Associate Tel: +32 (0)51 303045 Fax: +32 (0)51 310670 http://www.televic-rail.com Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium Company number 0825.539.581 - RPR Kortrijk