From: "Derick Anderson" <danderson@vikus.com>
To: netfilter@lists.netfilter.org
Subject: RE: stop accepting new connections on port 80
Date: Wed, 7 Dec 2005 16:58:00 -0500 [thread overview]
Message-ID: <FAC4E024BF776842876169173CE2F01313B3C4@mailbox.vikus.com> (raw)
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of Spam User
> Sent: Wednesday, December 07, 2005 3:39 PM
> To: netfilter@lists.netfilter.org
> Subject: stop accepting new connections on port 80
>
> Hi,
>
> I've been trying to figure out how to get iptables to stop
> accepting new connections on port 80 while letting the
> existing connections finish up what they're doing.
>
> I thought it would be as easy as removing the rule that
> allows new connections and leaving the rule that allowed
> related and established connections, but when I remove the
> rule that allows new connections, all connections stop working.
[snip]
I don't know exactly how you're determining the above: is it a long
download that gets killed? HTTP opens at least (and usually only) one
connection per page so the problem may be that the connection is already
closed even though the page is still being viewed. Unless you are
downloading something it's not likely your connection will last much
longer than four or five seconds on a heavily graphical page with
broadband.
Your rules look ok at first glance so I would recommend some time with
Ethereal and a long download from the web server. Download a big file
once with your default rules and see what happens. Then delete the file
and download it again, this time running your kill-new-connections
script and see if the file transfer gets knocked immediately.
> Thanks,
>
> Mike
Derick Anderson
next reply other threads:[~2005-12-07 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 21:58 Derick Anderson [this message]
2005-12-07 22:18 ` stop accepting new connections on port 80 Spam User
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 13:50 Derick Anderson
2005-12-07 20:38 Spam User
2005-12-09 18:42 ` Bill Hance
2005-12-09 19:08 ` R. DuFresne
2006-01-03 7:12 ` Jan Engelhardt
2005-12-14 20:33 ` Nick Drage
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=FAC4E024BF776842876169173CE2F01313B3C4@mailbox.vikus.com \
--to=danderson@vikus.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox