From: Mike Wright <mike.wright@mailinator.com>
To: Shams Fantar <sfantar@snurf.info>
Cc: netfilter@vger.kernel.org
Subject: Re: Iptables rules.
Date: Sat, 22 Sep 2007 12:44:34 -0700 [thread overview]
Message-ID: <46F570A2.5000307@mailinator.com> (raw)
In-Reply-To: <46F56591.7010905@snurf.info>
Shams Fantar wrote:
> Hello,
>
> I am writing iptables rules. Here is the rules, they are in a script :
> http://jumble.snurf.info/iptables-start
>
> When I use it, It blocks all access to the network. Why ?
>
> Do you have suggestions for my rules ?
There has to be a way for replies to outbound traffic to get back in.
Maybe this (probably near the top):
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
The rules -A OUTPUT aren't needed because OUTPUT's policy is already ACCEPT.
hth,
:m)
next prev parent reply other threads:[~2007-09-22 19:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 18:57 Iptables rules Shams Fantar
2007-09-22 19:32 ` Eljas Alakulppi
2007-09-22 19:44 ` Mike Wright [this message]
[not found] <47fc8b35.0e1f400a.4de1.0570@mx.google.com>
2008-04-09 9:53 ` Iptables Rules Jan Engelhardt
2008-04-09 17:01 ` Minh Cao
2008-04-09 17:03 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2008-04-08 22:01 Minh Cao
2008-04-09 4:12 ` Jan Engelhardt
2005-08-04 19:36 multiports Peggy Kam
2005-08-05 6:34 ` multiports Jan Engelhardt
2005-08-10 20:13 ` Maximum number of ports? Peggy Kam
2005-09-13 22:10 ` Maximum number of rules in iptables? Peggy Kam
2005-09-15 15:22 ` iptables rules Peggy Kam
2005-09-15 15:26 ` Jörg Harmuth
2005-09-15 15:37 ` Peggy Kam
2005-09-15 16:23 ` Jörg Harmuth
2005-10-21 13:46 ` Realos
2005-10-21 16:03 ` Rob Sterenborg
2005-10-21 16:19 ` Jörg Harmuth
2005-09-15 15:33 ` Jörg Harmuth
2002-09-09 4:06 Iptables rules Didier Hung Wan Luk
2002-09-07 11:59 ashivale
2002-09-07 9:39 Didier Hung Wan Luk
2002-09-07 10:36 ` Antony Stone
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=46F570A2.5000307@mailinator.com \
--to=mike.wright@mailinator.com \
--cc=netfilter@vger.kernel.org \
--cc=sfantar@snurf.info \
/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