NetBSD Problem Report #9978
Received: (qmail 18149 invoked from network); 25 Apr 2000 08:32:52 -0000
Message-Id: <200004250832.e3P8Whb01987@itojun.org>
Date: Tue, 25 Apr 2000 17:32:43 +0900 (JST)
From: itojun@itojun.org
Reply-To: itojun@itojun.org
To: gnats-bugs@gnats.netbsd.org
Subject: TCP RST rate control changes node behavior slightly
X-Send-Pr-Version: 3.95
>Number: 9978
>Category: kern
>Synopsis: TCP RST rate control changes node behavior slightly
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: itojun
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Apr 25 08:33:00 +0000 2000
>Closed-Date: Tue Sep 05 15:12:33 +0000 2000
>Last-Modified: Tue Sep 05 15:12:33 +0000 2000
>Originator: Jun-ichiro itojun Hagino
>Release: netbsd-current
>Organization:
itojun.org
>Environment:
NetBSD starfruit.itojun.org 1.4X NetBSD 1.4X (STARFRUIT) #198: Mon Apr 24 15:42:04 JST 2000 itojun@ginger.itojun.org:/usr/home/itojun/NetBSD/src/sys/arch/i386/compile/STARFRUIT i386
>Description:
NetBSD-current implements rate control for TCP RST (which is a great
thing). However, it sometimes annoy normal usage.
For example, if we try tcp connection attempt via IPv6 and IPv4
onto the same host, rate limit will apply.
>How-To-Repeat:
Configure following entries into /etc/hosts and try "telnet
localhost 9999" (there should be no server on tcp port 9999).
you will see a SYN to ::1, RST, SYN to 127.0.0.1, (RST suppressed
by rate limit here), then SYN again to 127.0.0.1, and RST. Due to
RST suppression, telnet attempt will take longer time to terminate
than before.
::1 localhost
127.0.0.1 localhost
>Fix:
not sure if this is a problem or not.
1. we may need to document it in bold font?
2. more clever rate limit logic? clever means more possiblity for
security weakness...
>Release-Note:
>Audit-Trail:
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: kern/9978
Date: Fri, 28 Apr 2000 12:58:05 +0200
I guess this special case could be caught, without causing real weaknesses,
by implementing the rate control per transport protocol (one for ipv4, one
for ipv6) used.
Are there other examples you're thinking of?
(For the general case, where N possibly-legitimate users bang on the same
server triggering the RST rate control, there's no help. System administration
might want to tune the allowed rate a bit there.)
-is
From: Darren Reed <darrenr@reed.wattle.id.au>
To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: kern/9978
Date: Sat, 6 May 2000 15:23:41 +1000 (EST)
Hmmm, is it even worth rate limiting across loopback interfaces ?
State-Changed-From-To: open->feedback
State-Changed-By: itojun
State-Changed-When: Wed Aug 2 07:41:35 PDT 2000
State-Changed-Why:
fixed in main trunc, need to revisit 1.5
Responsible-Changed-From-To: kern-bug-people->itojun
Responsible-Changed-By: itojun
Responsible-Changed-When: Wed Aug 2 07:41:35 PDT 2000
Responsible-Changed-Why:
i'll look into it
State-Changed-From-To: feedback->closed
State-Changed-By: itojun
State-Changed-When: Tue Sep 5 08:12:16 PDT 2000
State-Changed-Why:
merged to 1.5
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.