From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: blocking all traffic except selected ports
Date: Sat, 23 Apr 2005 18:50:47 -0400 [thread overview]
Message-ID: <20050423225047.GA9128@bender.817west.com> (raw)
In-Reply-To: <426ACDDF.5090604@crazeecanuck.homelinux.net>
On Sat, Apr 23, 2005 at 06:36:15PM -0400, Ed wrote:
> Actually (after having a pot of coffee) I just looked at `iptables -m
> multiport --help` on my box, and saw the following:
>
>
> multiport v1.3.1 options:
> --source-ports [!] port[,port:port,port...]
> --sports ...
> match source port(s)
> --destination-ports [!] port[,port:port,port...]
> --dports ...
> match destination port(s)
> --ports [!] port[,port:port,port]
> match both source and destination port(s)
>
>
> It seems multiport has been updated to use port ranges after all.
>
> (Note to self: don't reply to messages right after waking up either.
> UGH! I thought there was a reason that I switched from mport to
> multiport on my router...)
>
> https://lists.netfilter.org/pipermail/netfilter-devel/2005-January/017977.html
>
> # uname -r && iptables --version
> 2.6.11.7
> iptables v1.3.1
this brings out an interesting point--as i was speaking from an iptables
1.2.11 perspective (i have not updated a single box to 1.3.x)...we're
probably going to have to start specifying iptables version on almost
every post to keep from confusing the hell outta people.
-j
--
"Chris: Dad, there's a guy outside who says I can't go to school.
Peter: Yeah? Him and what army?
Chris: The U.S. Army.
Peter: ...that's a good army."
--Family Guy
next prev parent reply other threads:[~2005-04-23 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 8:47 blocking all trafic exapt selcter ports Kashif Ali Bukhari
2005-04-23 9:20 ` Edward Shornock
2005-04-23 9:23 ` Ed
2005-04-23 14:54 ` Jason Opperisano
2005-04-23 20:58 ` Ed
2005-04-23 22:36 ` blocking all traffic except selected ports Ed
2005-04-23 22:50 ` Jason Opperisano [this message]
2005-04-23 22:54 ` Taylor Grant
2005-04-23 23:07 ` R. DuFresne
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=20050423225047.GA9128@bender.817west.com \
--to=opie@817west.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 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.