From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200302140044.h1E0iAM24758@augusta.math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Speaking of routing....
In-Reply-To: Your message of "Thu, 13 Feb 2003 19:32:04 EST."
             <7e38167c7e140e20a8c47d19c9f0ffbb@plan9.bell-labs.com>
From: Dan Cross <cross@math.psu.edu>
Date: Thu, 13 Feb 2003 19:44:10 -0500
Topicbox-Message-UUID: 5e8a1bfa-eacb-11e9-9e20-41e7f4b1d025

> 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.