From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: Jan Niggemann <jn@hz6.de>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrack GRE behaves differently in 3.17 / 3.18
Date: Thu, 22 Jan 2015 00:21:58 +0100 [thread overview]
Message-ID: <54C03496.30504@plouf.fr.eu.org> (raw)
In-Reply-To: <20150121200324.Horde.ukdDqFj6DTInNSIVwG4VzA1@htjn.suhail.uberspace.de>
Jan Niggemann a écrit :
>
> nf_conntrack_proto_gre 12886 0
> nf_conntrack_ipv4 18003 1
> nf_defrag_ipv4 12443 1 nf_conntrack_ipv4
> xt_conntrack 12601 1
> nf_conntrack 57737 3
> nf_conntrack_proto_gre,xt_conntrack,nf_conntrack_ipv4
> x_tables 18078 5
> ip_tables,xt_tcpudp,xt_conntrack,iptable_filter,iptable_mangle
I do not see nf_conntrack_pptp here. It is required so that the first
GRE packet has the RELATED state.
Note : IIRC IME, the first GRE packet in a PPTP connection may be sent
by either side, client or server. GRE is used by PPTP to transport PPP,
and PPP is a peer-to-peer protocol, not client-server.
next prev parent reply other threads:[~2015-01-21 23:21 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 [this message]
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
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=54C03496.30504@plouf.fr.eu.org \
--to=pascal@plouf.fr.eu.org \
--cc=jn@hz6.de \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox