From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: weird iptables behaviour
Date: Fri, 16 Sep 2005 01:15:05 -0500 [thread overview]
Message-ID: <200509160115.05246.rob0@gmx.co.uk> (raw)
In-Reply-To: <432A5C09.5000105@riverviewtech.net>
On Friday 2005-September-16 00:45, Grant Taylor wrote:
> > On the openvpn box, FORWARD policy is DROP, so I did
> > "iptables -I FORWARD -i tap0 -j ACCEPT" and thought this
> > should do the trick. But I was wrong. The only solutions I
>
> First of all you will need to have a corresponding rule:
>
> iptables -I FORWARD -o tap0 -j ACCEPT
>
> To allow traffic in the reverse direction too.
Better yet, the usual stateful rule:
iptables -I FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-09-16 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 21:46 weird iptables behaviour Gabriel
2005-09-16 5:45 ` Grant Taylor
2005-09-16 6:15 ` /dev/rob0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-16 18:48 Gabriel
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=200509160115.05246.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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.