public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: ARP-related problem
Date: Sun, 27 Jan 2013 21:40:00 -0000	[thread overview]
Message-ID: <20130127214014.GA13255@grante> (raw)

On 2013-01-25, Grant Edwards <grant.b.edwards@gmail.com> wrote:

> I've been examining Ethernet traces from a customer site where there
> appear to be problems associated with the eCos ARP table entry
> timeouts.

It seems this is a known problem with a known fix, so I thought I
would follow-up just for the record...

Bernd Edlinger has kindly pointed me to a patch he submitted that
among other things fixes the periodic packet loss due to ARP entry
timeouts:

  http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001656

It would be interesting to have a chat with whoever decided that
letting the entry expire every 20 minutes [and thus potentially
discarding tx packets] was the right thing to do.

While it's obvious that discarding eCos's tx packets is part of the
design of the BSD ARP subsystem, what I haven't figured out is why the
TCP connection doesn't recover.  The smart money is betting on
Microsft as the culprit: one end of the TCP/IP connection is Windows
7, and the customer claims they never had the problem when using XP.

How long as TCP/IP been around?  It seems nothing is so old and well
understood that it can't be screwed up by Microsoft...

--
Grant

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2013-01-27 21:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130127214014.GA13255@grante \
    --to=grant.b.edwards@gmail.com \
    --cc=ecos-discuss@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).