From: Mart Frauenlob <mart.frauenlob@chello.at>
To: Jan Niggemann <jn@hz6.de>, Mart Frauenlob <mart.frauenlob@chello.at>
Cc: Pascal Hambourg <pascal@plouf.fr.eu.org>, netfilter@vger.kernel.org
Subject: Re: conntrack GRE behaves differently in 3.17 / 3.18
Date: Sat, 24 Jan 2015 16:28:42 +0100 [thread overview]
Message-ID: <54C3BA2A.9050201@chello.at> (raw)
In-Reply-To: <20150124084457.Horde.7lzdxvLxV9PON4YIA4wqmA5@htjn.suhail.uberspace.de>
On 24.01.2015 08:44, Jan Niggemann wrote:
> Zitat von Mart Frauenlob <mart.frauenlob@chello.at>:
>> Even if the modules are loaded, you need to allow the first gre packet
>> as you pointed out above.
> At least on my system it's sufficient that I load conntrack_pptp. With
> the following rules I can then create a pptp connection:
> -P INPUT DROP
> -P FORWARD DROP
> -P OUTPUT ACCEPT
> -A INPUT -i lo -j ACCEPT
> -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
> I do not need to explicitly allow any gre traffic for the pptp vpn to work.
Because it's accepted in the OUTPUT chain by the default policy?
next prev parent reply other threads:[~2015-01-24 15:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 13:04 conntrack GRE behaves differently in 3.17 / 3.18 Jan Niggemann
2015-01-21 2:01 ` Eliezer Croitoru
2015-01-21 13:19 ` Jan Niggemann
2015-01-21 14:33 ` Mart Frauenlob
2015-01-21 19:03 ` Jan Niggemann
2015-01-21 23:21 ` Pascal Hambourg
2015-01-22 7:55 ` Jan Niggemann
2015-01-22 10:10 ` Mart Frauenlob
2015-01-22 15:40 ` Eliezer Croitoru
2015-01-22 18:51 ` Neal Murphy
2015-01-22 20:33 ` Pascal Hambourg
2015-01-22 21:51 ` Jan Niggemann
2015-01-22 22:28 ` Neal Murphy
2015-01-23 23:20 ` Mart Frauenlob
2015-01-24 7:44 ` Jan Niggemann
2015-01-24 15:28 ` Mart Frauenlob [this message]
2015-01-24 20:07 ` Pascal Hambourg
[not found] <1430142363.3948.12.camel@alum.wpi.edu>
2015-04-27 13:47 ` Lubomir Rintel
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=54C3BA2A.9050201@chello.at \
--to=mart.frauenlob@chello.at \
--cc=jn@hz6.de \
--cc=netfilter@vger.kernel.org \
--cc=pascal@plouf.fr.eu.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