From: Patrick McHardy <kaber@trash.net>
To: patrizio.bassi@gmail.com
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Fw: Re: 2.6.14-rc1 Critical bug: machine complete freeze
Date: Sun, 18 Sep 2005 18:58:55 +0200 [thread overview]
Message-ID: <432D9CCF.6000104@trash.net> (raw)
In-Reply-To: <432D944D.9020800@gmail.com>
Patrizio Bassi wrote:
> Patrick McHardy ha scritto:
>
>>> My iptables script was about 1 year old, and worked perfectly.
>>> New kernel (dunno which...2.6.1x) introduced this problem.
>>>
>> Try adding some logging rules to see why it gets dropped (-m state
>> --state INVALID for example).
>>
> the question is: why first time it's dropped and after reload not?
If the ping is already running before you load your NAT rules their
might already be state for the "connection" without NAT initialized.
> i've also supposed a time problem..waiting for bridge propagating and so
> on.
>
> after some mins i tried, and got same problem, so there must be some
> initialization problems.
>
> i suspect in bridge interface enabling/disabling and iptables in
> following bridge changes.
I don't know your setup, so I can't comment on this. But again,
some logging rules should at least tell whats happening to the
packets.
prev parent reply other threads:[~2005-09-18 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050917133943.30983afd.akpm@osdl.org>
[not found] ` <432C8178.40201@trash.net>
[not found] ` <432C8398.9060202@gmail.com>
[not found] ` <432C8590.9070600@trash.net>
[not found] ` <432D15BC.3070500@gmail.com>
2005-09-18 15:03 ` Fw: Re: 2.6.14-rc1 Critical bug: machine complete freeze Patrick McHardy
[not found] ` <432D944D.9020800@gmail.com>
2005-09-18 16:58 ` Patrick McHardy [this message]
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=432D9CCF.6000104@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=patrizio.bassi@gmail.com \
/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.