From: Benedikt Gollatz <ben@differentialschokolade.org>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: Problem with IPv6 tunnel
Date: Fri, 10 Jul 2009 13:50:21 +0200 [thread overview]
Message-ID: <23412bf8079dabef19ddd9fbe9022f66@localhost> (raw)
In-Reply-To: <4A560E0D.40806@plouf.fr.eu.org>
On Thu, 09 Jul 2009 17:34:37 +0200, Pascal Hambourg
<pascal.mail@plouf.fr.eu.org> wrote:
> Benedikt Gollatz a écrit :
>> On Thu, 9 Jul 2009 15:06:52 +0200, David Balažic <xerces9@gmail.com>
>> wrote:
>> You need to accept proto-41
>> packets in the PREROUTING chain to stop the connection tracker from
>> looking
>> at them.
>
> Wrong. Connection tracking happens anyway.
You'll have to tell that to the authors of the SixXS FAQ.
> Anyway what David need is to allow 6in4 traffic from the tunnel
> endpoint. This has nothing to do with connection tracking.
Traffic passing through at first and after a certain time not being able to
pass anymore is a classic symptom of problems with connection tracking.
next prev parent reply other threads:[~2009-07-10 11:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 8:31 Problem with IPv6 tunnel David Balažic
2009-06-19 10:18 ` Benedikt Gollatz
2009-06-19 12:03 ` David Balažic
2009-06-19 12:13 ` Benedikt Gollatz
2009-06-19 12:57 ` David Balažic
2009-06-19 13:08 ` Benedikt Gollatz
2009-06-19 13:37 ` David Balažic
2009-06-21 13:44 ` Chris Hills
2009-06-21 13:46 ` Chris Hills
2009-07-09 15:30 ` Pascal Hambourg
2009-06-19 10:18 ` Benedikt Gollatz
2009-07-09 11:48 ` David Balažic
2009-07-09 13:06 ` David Balažic
2009-07-09 14:51 ` Benedikt Gollatz
2009-07-09 15:34 ` Pascal Hambourg
2009-07-10 11:50 ` Benedikt Gollatz [this message]
2009-07-10 13:40 ` Pascal Hambourg
2009-07-10 15:00 ` David Balažic
2009-07-10 15:30 ` Pascal Hambourg
2009-07-10 22:31 ` David Balažic
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=23412bf8079dabef19ddd9fbe9022f66@localhost \
--to=ben@differentialschokolade.org \
--cc=netfilter@vger.kernel.org \
--cc=pascal.mail@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