From: Nick Khamis <symack@gmail.com>
To: neal.p.murphy@alum.wpi.edu
Cc: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: IPTables - Going Stateless
Date: Tue, 21 May 2013 12:29:14 -0400 [thread overview]
Message-ID: <CAGWRaZZYJ40WTHPqbK2nO+i_iT82iS_OBf=qCyiRBr0B1CFjiA@mail.gmail.com> (raw)
In-Reply-To: <201305211211.53740.neal.p.murphy@alum.wpi.edu>
On 5/21/13, Neal Murphy <neal.p.murphy@alum.wpi.edu> wrote:
> You still aren't accepting *each* direction. Either accept each direction
> with
> explicit rules or rewrite the rules so they apply to both directions at
> once.
> The former is probably easier to understand months later, even though it is
>
> more verbose.
>
> Mea culpa. I missed the '--dport'; that should be changed to '--sport' in
> one
> of the rules. I adjusted the rule below.
>
> N
>
> On Tuesday, May 21, 2013 11:07:10 AM you wrote:
>> Hello Everyone,
>>
>> #echo -e " - Accepting SSH Traffic"
>> $IPTABLES -A TCP -p tcp -m tcp -s 192.168.2.0/24 -d 192.168.2.5
>> --dport 22 -j ACCEPT
>> $IPTABLES -A TCP -p tcp -m tcp -s 0.0.0.0/0 -d 192.168.2.5 --dport 22 -j
>> DROP
>>
>> Everything works fine with the REJECT rules commented out, but when
>> included SSH access is blocked out. Not sure why, isn't the sequence
>> correct (i.e., the ACCPET entries before the DROP and REJECT)?
>
> SSH isn't a one-way protocol. I believe you need at least one more rule.
> This:
> -A TCP -p tcp -m tcp -s 192.168.2.0/24 -d 192.168.2.5 \
> --dport 22 -j ACCEPT
> only matches packets in one direction. You need to add:
> -A TCP -p tcp -m tcp -s 192.168.2.5 -d 192.168.2.0/24 \
> --sport 22 -j ACCEPT
> to accept packets in the other direction.
>
>
That was it!!! Thank you so much. For future searchers to similar problems:
#!/bin/bash
IPTABLES='/sbin/iptables'
#Set interface values
INTIF1='eth0'
#flush rules and delete chains
$IPTABLES -F
$IPTABLES -X
#echo -e " - Accepting input lo traffic"
$IPTABLES -A INPUT -i lo -j ACCEPT
#echo -e " - Accepting output lo traffic"
$IPTABLES -A OUTPUT -o lo -j ACCEPT
#echo -e " - Defined Chains"
$IPTABLES -N TCP
$IPTABLES -N UDP
#echo -e " - Accepting SSH Traffic"
$IPTABLES -A TCP -p tcp -m tcp -s 192.168.2.0/24 -d 192.168.2.5
--dport 22 -j ACCEPT
$IPTABLES -A TCP -p tcp -m tcp -s 192.168.2.5 --sport 22 -d
192.168.2.0/24 -j ACCEPT
$IPTABLES -A TCP -p tcp -m tcp -s 0.0.0.0/0 -d 192.168.2.5 --dport 22 -j DROP
#echo -e " - Accepting input TCP and UDP traffic to open ports"
$IPTABLES -A INPUT -i $INTIF1 -p tcp -j TCP
$IPTABLES -A INPUT -i $INTIF1 -p udp -j UDP
#echo -e " - Accepting output TCP and UDP traffic to open ports"
$IPTABLES -A OUTPUT -o $INTIF1 -p tcp -j TCP
$IPTABLES -A OUTPUT -o $INTIF1 -p udp -j UDP
#echo -e " - Dropping input TCP and UDP traffic to closed ports"
$IPTABLES -A INPUT -i $INTIF1 -p tcp -j REJECT --reject-with tcp-rst
$IPTABLES -A INPUT -i $INTIF1 -p udp -j REJECT --reject-with
icmp-port-unreachable
#echo -e " - Dropping output TCP and UDP traffic to closed ports"
$IPTABLES -A OUTPUT -o $INTIF1 -p tcp -j REJECT --reject-with tcp-rst
$IPTABLES -A OUTPUT -o $INTIF1 -p udp -j REJECT --reject-with
icmp-port-unreachable
#echo -e " - Dropping input traffic to remaining protocols sent
to closed ports"
$IPTABLES -A INPUT -i $INTIF1 -j REJECT --reject-with icmp-proto-unreachable
#echo -e " - Dropping output traffic to remaining protocols sent
to closed ports"
$IPTABLES -A OUTPUT -o $INTIF1 -j REJECT --reject-with icmp-proto-unreachable
Kind Regards,
Nick.
next parent reply other threads:[~2013-05-21 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201305211211.53740.neal.p.murphy@alum.wpi.edu>
2013-05-21 16:29 ` Nick Khamis [this message]
2013-05-21 16:53 ` [gentoo-user] Re: IPTables - Going Stateless Nick Khamis
2013-05-21 22:41 ` Mike Gilbert
2013-05-22 0:16 ` Adam Carter
[not found] ` <CAC=wYCEs6rkR5ch4rsumJKj9Kg5e+j_LEr@mail.gmail.com>
2013-05-22 2:16 ` James
[not found] <CAGWRaZbwp8jDPxDzHX6g_LkpK74iB6K4GSoU7c_5THDSx1oDmQ@mail.gmail.com>
[not found] ` <201305211133.03830.neal.p.murphy@alum.wpi.edu>
2013-05-21 16:01 ` Nick Khamis
2013-05-21 16:14 ` Alan McKinnon
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='CAGWRaZZYJ40WTHPqbK2nO+i_iT82iS_OBf=qCyiRBr0B1CFjiA@mail.gmail.com' \
--to=symack@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=neal.p.murphy@alum.wpi.edu \
/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