Date: Sat, 12 Apr 2003 23:05:00 -0400 From: Barney Wolff <barney@pit.databus.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: current@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts Message-ID: <20030413030500.GA64896@pit.databus.com> In-Reply-To: <20030412.204912.76964336.imp@bsdimp.com> References: <109.225ca595.2bc723f2@aol.com> <20030412.204912.76964336.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 12, 2003 at 08:49:12PM -0600, M. Warner Losh wrote: > In message: <109.225ca595.2bc723f2@aol.com> > BelletJr@aol.com writes: > : Why does not connect(2) return any error when trying to connect to a host > : unreachable because of an infinite loop in the routes? No time-out occurs and > : the value 0 is returned by connect(2). > > Hmmmmm, you are correct. I was sure that you were nuts, but on > -current the following program returns no error at all... Telnet > shows the same behavior. This is clearly wrong. It's not just current; stable behaves exactly the same. The problem is that the icmp time-exceeded packet gets translated into an error code of 0, which confuses things. I've filed a PR with a suggested fix: http://www.freebsd.org/cgi/query-pr.cgi?pr=50839 -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030413030500.GA64896>