From: gabrix <sickuser@gmail.com>
To: netfilter@lists.netfilter.org
Subject: only checking if i make correct custom chains
Date: Sat, 31 Mar 2007 15:39:44 +0200 [thread overview]
Message-ID: <460E64A0.2040000@gabrix.ath.cx> (raw)
I only want to see if i interpret iptables custom chains correctly .In
this chain EXAMPLE i want to build a jump that make various things.This
is an example :
IPT=/sbin/iptables
$IPT -N EXAMPLE
$IPT -A EXAMPLE -p tcp --dport 80 -j ACCEPT
$IPT -A EXAMPLE -p tcp --dport 1:65535 DROP
$IPT -A EXAMPLE -p udp --dport 1024:65535 -j DROP
$IPT -A EXAMPLE -p icmp --icmp-type any -j ULOG --ulog-prefix
"DROPPED_ICMP :"
$IPT -A EXAMPLE -p icmp --icmp-type any -j DROP
$IPT -I INPUT -i eth0 -p all -d Myhost -j EXAMPLE
Is all this correct ???? i want for the jump EXAMPLE to accept tcp
connections on port 80 , drop all others , drop all udp on unprivileged
ports , ulog all icmp and than drop them all in one jump and that is
going to happen first of all "I".I'd correct ?Thanks for the attenction !!!
--
http://tor.gabrix.ath.cx
next reply other threads:[~2007-03-31 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 13:39 gabrix [this message]
2007-04-02 20:21 ` only checking if i make correct custom chains Martijn Lievaart
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=460E64A0.2040000@gabrix.ath.cx \
--to=sickuser@gmail.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