From: Samuel Tardieu <sam@rfc1149.net>
To: linux-kernel@vger.kernel.org
Subject: Re: TCP stack behaviour question
Date: 19 Sep 2006 14:03:30 +0200 [thread overview]
Message-ID: <87wt802hd9.fsf@willow.rfc1149.net> (raw)
In-Reply-To: 005a01c6db50$587929c0$294b82ce@stuartm
>>>>> "Stuart" == Stuart MacDonald <stuartm@connecttech.com> writes:
Stuart> I suppose that the TCP retransmits aren't being sent because
Stuart> the ethernet and/or IP layers don't know what's going on,
Stuart> which is what's producing the arps. Is that correct?
It seems correct. You cannot expect TCP packets to be sent if the
target is supposedly on a directly connected network and ARP cannot
get its MAC address. What should the IP layer put as the MAC address
if it is unknown?
You may want to run another test with another unreachable target
located after a router, so that the MAC address of the router is used
on the wire. You should see all the TCP retransmits you expect to see.
Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/
next prev parent reply other threads:[~2006-09-19 12:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 18:29 TCP stack behaviour question Stuart MacDonald
2006-09-19 12:03 ` Samuel Tardieu [this message]
2006-09-19 14:00 ` Stuart MacDonald
2006-09-20 9:54 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-09-15 17:28 Stuart MacDonald
2006-09-18 8:29 ` Andi Kleen
2006-09-18 13:20 ` Stuart MacDonald
2006-09-18 13:54 ` Andi Kleen
2006-09-18 14:19 ` Stuart MacDonald
2006-09-18 14:31 ` Andi Kleen
2006-09-18 15:38 ` Michael Kerrisk
2006-09-18 17:01 ` Stuart MacDonald
2006-09-19 6:13 ` Michael Kerrisk
2006-09-19 6:47 ` Andi Kleen
2006-09-19 14:50 ` Michael Kerrisk
2006-09-20 9:55 ` Andi Kleen
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=87wt802hd9.fsf@willow.rfc1149.net \
--to=sam@rfc1149.net \
--cc=linux-kernel@vger.kernel.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