From: Gary Thomas <gary@chez-thomas.org>
To: Wolfgang Heppner <hep@iis.fhg.de>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] FreeBSD-Stack not responding
Date: Mon, 29 Jul 2002 05:53:00 -0000 [thread overview]
Message-ID: <1027947225.23151.8.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3D430AA8.CBF0C91@iis.fhg.de>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Sat, 2002-07-27 at 15:03, Wolfgang Heppner wrote:
> Hello,
>
> I recently switched from the Open- to the FreeBSD stack (latest CVS
> version)
> When i try to send Data to my target (e.g. ascii strings via a telnet
> client on Linux and/or Windows), the data is lost in the stack (the
> "read" call in my application never returns) - even when a connection
> could be established and my application could send a "Prompt" to the
> telnet client! With the OpenBSD Stack this works fine.
>
> I figured out that packets are dropped in the cyg_tcp_input function
> because of a bad checksum.
>
> I got some warnings during the eCos-built:
> implicit declarations of function 'cyg_in_cksum_hdr' in ip_input.c:332
> implicit declarations of function 'cyg_in_cksum_hdr' and
> 'cyg_in_cksum_skip'
> in ip_output and
> implicit declarations of function 'cyg_in_pseudo' in tcp_input:405
> (among some others)
These are just warnings and should be harmless.
>
> Has anybode experienced similar problems with the FreeBSD stack?
> Any ideas?
>
> Thanks in advance
> Wolfgang
>
> PS: I built the eCos library with the new_net template and removed libm
> and dns support.
What's the target?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-07-29 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 14:04 Wolfgang Heppner
2002-07-29 5:53 ` Gary Thomas [this message]
2002-07-30 1:26 ` Wolfgang Heppner
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=1027947225.23151.8.camel@hermes.chez-thomas.org \
--to=gary@chez-thomas.org \
--cc=ecos-discuss@sources.redhat.com \
--cc=hep@iis.fhg.de \
/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).