From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: [Fwd: FreeBSD network stack question]
Date: Wed, 19 Oct 2005 21:16:00 -0000 [thread overview]
Message-ID: <20051019211805.5B6213C030@rivatek.dnsalias.net> (raw)
In-Reply-To: <20051019205708.GL7087@lunn.ch>
In gmane.os.ecos.general, you wrote:
> On Wed, Oct 19, 2005 at 01:21:49PM -0500, Grant Edwards wrote:
>> In gmane.os.ecos.general, you wrote:
>>
>> > If we collect a packet trace with tcpdump, we see an ARP request and ARP
>> > reply, then we see the 2nd segment of the first message - the first
>> > segment of the first message is never transmitted.
>>
>> Now you understand why there's a "U" in "UDP". ;)
>
> Unreliable Datagram Protocol? Well its actually User Datagram Protocl.
Sure, that's what the RFC says, but we all know it really
stands for "Unreliable".
>> I think so. UDP packets are allowed to vanish pretty much
>> anywhere along the way.
>
> Looking at the code it seems like it will hold onto one packet
> until the ARP responce is received. If there are more than one
> request to send a packet while the ARP process is still going
> on, only the last packet is kept. All others are thrown away.
That sounds right.
--
Grant Edwards grante Yow! FIRST, I was in a
at TRUCK...THEN, I was in
visi.com a DINER...
--
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 prev parent reply other threads:[~2005-10-19 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 17:26 [ECOS] " Barry Wealand
2005-10-19 18:01 ` Daniel Helgason
2005-10-19 18:01 ` Gary Thomas
2005-10-19 19:11 ` Barry Wealand
2005-10-19 18:20 ` [ECOS] " Grant Edwards
2005-10-19 20:57 ` Andrew Lunn
2005-10-19 21:16 ` Grant Edwards [this message]
2005-10-21 12:04 ` [ECOS] RE : [ECOS] " Arnaud Chataignier
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=20051019211805.5B6213C030@rivatek.dnsalias.net \
--to=grante@visi.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).