From: Ted Kaczmarek <tedkaz@optonline.net>
To: netfilter@lists.netfilter.org
Subject: udp/tcp port range rules for forward/input chains
Date: Tue, 14 Oct 2003 23:10:18 -0400 [thread overview]
Message-ID: <1066187418.14600.28.camel@tarkus> (raw)
Digging around the only thing I found was a patch-o-matic that allowed
for doing a range of 15 ports.
I see many references with dnat and snat, but nothing besides the patch
for input or forward chains.
If anyone has a link that or info that can steer me in the right
direction the beers are on me at the Javits Center Linux show.
Thanks,
Ted
PS: this is by far the best maintained mailing list I am on, kudo's to
all the contributors/participants.
next reply other threads:[~2003-10-15 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 3:10 Ted Kaczmarek [this message]
2003-10-15 6:27 ` udp/tcp port range rules for forward/input chains Joel Newkirk
2003-10-16 21:34 ` Ted Kaczmarek
2003-10-16 21:49 ` Joel Newkirk
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=1066187418.14600.28.camel@tarkus \
--to=tedkaz@optonline.net \
--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