From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Another newbyish question I'm afraid, -m state --state
Date: Thu, 01 Mar 2001 09:21:17 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417070@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940417067@msgid-missing>
<PRE>On Wed, 28 Feb 2001, Paul Wouters wrote:
><i> I'd like to be able to deny all new connections to a firewall, with the
</I>><i> exception of port 22 (sshd) and some ports I'd like to forward internally.
</I>
><i> However, it seems I can't make a rule that is using the state
</I>><i> AND a source/dest port in there. Eg the following won't work:
</I>><i>
</I>><i> iptables -A INPUT -i eth0 -m state --state NEW,INVALID --dport 22 -j DROP
</I>><i> iptables -A INPUT -i eth0 -m state --state NEW,INVALID -j DROP
</I>><i> iptables -A FORWARD -i eth0 -m state --state NEW,INVALID --dport 25 -j ACCEPT
</I>><i> iptables -A FORWARD -i eth0 -m state --state NEW,INVALID -j DROP
</I>><i>
</I>><i> Anyone? :)
</I>
iptables -A INPUT -i eth0 -p tcp --dport 22 -m state --state NEW,INVALID -j DROP
iptables -A INPUT -i eth0 -m state --state NEW,INVALID -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 25 -m state --state NEW,INVALID -j ACCEPT
iptables -A FORWARD -i eth0 -m state --state NEW,INVALID -j DROP
--sport and --dport need the -p tcp or -p udp flags to be set, as source and
destination ports may not make sense for certain protocols, most notably
ICMP.
Doei, Arthur.
--
/\ / | <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A> | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
</PRE>
prev parent reply other threads:[~2001-03-01 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 17:06 [LARTC] Another newbyish question I'm afraid, -m state --state matters Paul
2001-02-28 18:37 ` Patrik
2001-03-01 9:21 ` Arthur [this message]
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=marc-lartc-98373940417070@msgid-missing \
--to=lartc@vger.kernel.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.