From: Mike Accetta <maccetta@laurelnetworks.com>
To: netfilter-devel@lists.netfilter.org
Subject: change in behavior of OUTPUT chain reject rule in 2.6.19
Date: Fri, 15 Dec 2006 10:23:51 -0500 [thread overview]
Message-ID: <4582BE07.1080803@laurelnetworks.com> (raw)
Between 2.6.18 and 2.6.19 (and 2.6.19.1) we've observed that a reject
rule on the OUTPUT chain no longer causes a connection attempt to abort
immediately with "Connection refused". As a specific example, this rule
iptables -A OUTPUT -p tcp --destination-port 23 \
--destination 10.0.20.1 -j REJECT --reject-with tcp-reset
will cause a telnet connection to 10.0.20.1 to fail immediately under
2.6.18 but will take minutes to timeout under 2.6.19. A "git bisect"
identifies change 9d02002d2dc2c7423e5891b97727fde4d667adf1 as the
culprit. The change description gives no hint that this effect was
intended. Is this a regression?
--
Mike Accetta
ECI Telecom Ltd.
Data Networking Division (previously Laurel Networks)
next reply other threads:[~2006-12-15 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 15:23 Mike Accetta [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-15 5:36 change in behavior of OUTPUT chain reject rule in 2.6.19 Mike Accetta
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=4582BE07.1080803@laurelnetworks.com \
--to=maccetta@laurelnetworks.com \
--cc=netfilter-devel@lists.netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.