From: "Wager Philipp" <pwager@gmx.de>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] free-bsd tcp/ip stack problems on mbx821
Date: Mon, 23 Aug 2004 09:36:00 -0000 [thread overview]
Message-ID: <000201c488f3$a14b3eb0$5a07010a@schleppos> (raw)
In-Reply-To: <1093252266.27474.ezmlm@ecos.sourceware.org>
Hi,
I've got problems getting any tcp-session established with the free-bsd
tcp/ip stack on my mbx821 board.
Has anyone tested the stack on mbx hardware yet?
The problem seems to arise from bad tcp checksums calculated in
in_delayed_cksum() from ip_output.c
I'm using latest cvs checkout ecos sources
and prebuild toolchain from ecoscentric (gcc version 3.2.1)
Any hints would be greatly appreciated.
Thanks
Philipp Wager
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2004-08-23 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1093252266.27474.ezmlm@ecos.sourceware.org>
2004-08-23 9:36 ` Wager Philipp [this message]
2004-08-23 11:51 ` Gary Thomas
2004-08-31 19:34 ` [ECOS] EB40A Angel monitor image Carlos Camargo
2004-08-24 4:42 ` [ECOS] free-bsd tcp/ip stack problems on mbx821 mohanlal jangir
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='000201c488f3$a14b3eb0$5a07010a@schleppos' \
--to=pwager@gmx.de \
--cc=ecos-discuss@sources.redhat.com \
/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).