From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Speaking of routing....
Date: Thu, 13 Feb 2003 19:44:10 -0500 [thread overview]
Message-ID: <200302140044.h1E0iAM24758@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Thu, 13 Feb 2003 19:32:04 EST." <7e38167c7e140e20a8c47d19c9f0ffbb@plan9.bell-labs.com>
> As for the delay, there wouldn't be one if your inside dns server
> came back quickly with a nonexistant domain response. However, if
> it comes back with an address that won't work in the inside or
> doesn't come back, you're stuck with the timeout.
That's fine, I understand that part. I guess I'm confused with what
the IP stack does with the packet it's trying to send if no route exists
for it. Why would it take time timing out if it had no place to send
it? That is, if the IP stack only knows how to send to hosts on
172.16.1.0/24, and no where else, why does it need to timeout when
it tries to send a packet to 146.186.132.2? More importantly, what's
it doing with that packet in the mean time? Not that I'm really worried
about it at this point, I'm just curious.
- Dan C.
next prev parent reply other threads:[~2003-02-14 0:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030213095533.L50666@ >
2003-02-13 22:16 ` Dan Cross
2003-02-13 22:24 ` andrey mirtchovski
2003-02-13 22:27 ` David Gordon Hogan
2003-02-13 23:14 ` Dan Cross
2003-02-13 23:23 ` northern snowfall
2003-02-13 23:24 ` David Gordon Hogan
2003-02-13 23:46 ` Dan Cross
2003-02-14 0:11 ` Russ Cox
2003-02-14 0:17 ` Dan Cross
2003-02-14 0:21 ` David Presotto
2003-02-14 0:29 ` northern snowfall
2003-02-14 16:40 ` [9fans] FS dimension northern snowfall
2003-02-14 0:31 ` [9fans] Speaking of routing Dan Cross
2003-02-14 0:34 ` David Presotto
2003-02-14 0:32 ` David Presotto
2003-02-14 0:44 ` Dan Cross [this message]
2003-02-14 0:48 ` David Presotto
2003-02-14 0:50 ` Dan Cross
2003-02-14 0:52 ` David Presotto
2003-02-14 0:57 ` Dan Cross
2003-02-13 16:52 Dan Cross
2003-02-13 17:03 ` andrey mirtchovski
2003-02-13 17:13 ` Skip Tavakkolian
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=200302140044.h1E0iAM24758@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).