public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
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 18:20:00 -0000	[thread overview]
Message-ID: <20051019182149.575E03DAE2@rivatek.dnsalias.net> (raw)
In-Reply-To: <43561EFF.8030200@lmco.com>

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".  ;)

> 1. udp_output calls ip_output
> [...]
> 8. ip_output believes that all is well with the first segment and 
> proceeds to send the second.  By now, the ARP resolution process has 
> completed, and the second segment is transmitted normally.
>
> Is this normal?

I think so.  UDP packets are allowed to vanish pretty much
anywhere along the way.

-- 
Grant Edwards                   grante             Yow!  I have many CHARTS
                                  at               and DIAGRAMS...
                               visi.com            

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

  parent reply	other threads:[~2005-10-19 18:20 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 ` Grant Edwards [this message]
2005-10-19 20:57   ` [ECOS] " Andrew Lunn
2005-10-19 21:16     ` Grant Edwards
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=20051019182149.575E03DAE2@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).