On Fri, Feb 23, 2001 at 04:34:05AM +0100, Jesper Skriver wrote:
> On Thu, Feb 22, 2001 at 09:20:44PM -0600, Jonathan Lemon wrote:
> > On Fri, Feb 23, 2001 at 03:49:52AM +0100, Jesper Skriver wrote:
> > >
> > > I still think we should react to the following as a minimum
> > > - type 3 code 0 net unreachable
> > > - type 3 code 1 host unreachable
> >
> > RFC 1122, Section 4.2.3.9 says:
> >
> > o Destination Unreachable -- codes 0, 1, 5
> > Since these Unreachable messages indicate soft error
> > conditions, TCP MUST NOT abort the connection, and it
> > SHOULD make the information available to the
> > application.
> >
> > I think that these should be transients.
>
> As discussed on IRC I suggest adding the ability (under control of a
> sysctl, disabled by default) to treat 0/1 (perhaps even 5) like 2,3,9 &
> 10.
Forget this, as discussed on IRC, it would be better to have a code 0/1
trigger a immediate retransmit of the SYN, this would also give us
timeouts < 10 secs ...
If jlemon doesn't beat me to it, I'll try to look at this in the weekend
... as a possible "take III"
/Jesper
--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
Work: Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: FreeBSD committer @ AS2109 (A much smaller network ;-)
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
