netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lars Täuber" <lars.taeuber@gmx.net>
To: netfilter@vger.kernel.org
Subject: Re: nat problem: What's so special with traffic from audibank.de?
Date: Sat, 5 Dec 2009 23:19:11 +0100	[thread overview]
Message-ID: <20091205231911.bcb9fcc0.lars.taeuber@gmx.net> (raw)
In-Reply-To: <4B18A8D4.901@trash.net>

Hallo Patrick,

On Fri, 04 Dec 2009 07:14:44 +0100 Patrick McHardy <kaber@trash.net> wrote:
> > I could solve my problem with either allow any icmp traffic from outside to any destination or use the clamp-to-pmtu in the server settings for the firewall. This is a switch in fwbuilder.

sorry i was wrong.
At first i tried the »clamp-to-pmtu« setting and it worked. After removing this setting and inserting a gloabl rule to accept every icmp traffic it still worked.
But I didn't realized that this global rule had no effect at all.


> > 
> > Why is such an ICMP message not RELATED in the meaning of
> >    echo "-A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT"
> > with a _related_ tcp connection?
> 
> It should be. Please post a dump of the relevant ICMP message
> and the connection tuples from /proc/net/nf_conntrack for the
> original TCP connection.

No such icmp message ever reached my firewall though I tryed hard to record such an icmp message. My guess is that it must have been filtered out on the way.
The clamp-to-pmtu seemed to have a lasting success.

What I'm wondering is why it just works on the firewall itself but not with the natted computers in the private network?

Sorry for replying so late.
Lars

  reply	other threads:[~2009-12-05 22:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 14:48 nat problem: What's so special with traffic from audibank.de? Lars Täuber
2009-12-03 22:22 ` Mattias Rönnblom
2009-12-03 22:54   ` Lars Täuber
2009-12-04  6:14     ` Patrick McHardy
2009-12-05 22:19       ` Lars Täuber [this message]
2009-12-06  7:37         ` Lars Täuber

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=20091205231911.bcb9fcc0.lars.taeuber@gmx.net \
    --to=lars.taeuber@gmx.net \
    --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;
as well as URLs for NNTP newsgroup(s).