From: Adam Rosi-Kessel <adam@rosi-kessel.org>
To: netfilter@lists.netfilter.org
Subject: OUTPUT chain, Source Port 80 ---> Destination Port Unprivileged
Date: Sun, 20 Nov 2005 14:13:03 -0500 [thread overview]
Message-ID: <4380CABF.2060705@rosi-kessel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
I've noticed that I occasionally have output packets on my webserver that
have source port 80 and a destination port > 1024 (I've recently seen 4911,
4912, 49440, 49521, and 50296).
My current OUTPUT policy drops outbound traffic except on ports that are
specifically allowed. The unprivileged ports are not currently allowed.
I've seen a few sample iptables rulesets that allow outbound traffic to
unprivileged ports from source port 80.
Can someone explain to me why this happens, or point me to an explanation
elsewhere? Are there reasons to allow (or not to allow) such traffic, i.e.,
with a rule like:
iptables -A OUTPUT -o $EXTERNAL_INTERFACE -p tcp -s $IPADDR 1024:65535 \
--source-port 80 --destination-port "1024:65535" -j ACCEPT
?
--
Adam Rosi-Kessel
http://adam.rosi-kessel.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next reply other threads:[~2005-11-20 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 19:13 Adam Rosi-Kessel [this message]
2005-11-20 20:23 ` OUTPUT chain, Source Port 80 ---> Destination Port Unprivileged Adam Rosi-Kessel
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=4380CABF.2060705@rosi-kessel.org \
--to=adam@rosi-kessel.org \
--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 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.