From: Oguz Yilmaz <oguzyilmazlist@gmail.com>
To: netfilter@vger.kernel.org
Subject: Packets stops traversing after nat PREROUTING
Date: Wed, 14 Apr 2010 11:30:32 +0300 [thread overview]
Message-ID: <s2sc4ada2161004140130ve00e5873qc38aebaa842d3b6e@mail.gmail.com> (raw)
OS is CentOS 5.4
Kernel is 2.6.18-164
Sometimes my firewall blocks the internet. When I inspect I have seen:
- nat PREROUTING counters increase
- filter FORWARD counters do not increase
- nat POSTROUTING counters do not increase
According to the diagram of Engelhardt,
http://jengelh.medozas.de/images/nf-packet-flow.png, the problem
should be in Bridging Decision point or acc.to former diagrams in
Routing Decision point.
I have tried to flush routing cache by "ip ro fl ca".
Problem is recovered only after /etc/init.d/iptables stop / start
I need further cues for deepen the problem, or exact reasons for
updating/recompling to newer kernel/netfilter.
Best Regards,
Oguz.
next reply other threads:[~2010-04-14 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:30 Oguz Yilmaz [this message]
2010-04-14 9:59 ` Packets stops traversing after nat PREROUTING Jan Engelhardt
2010-04-14 20:09 ` Oguz Yilmaz
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=s2sc4ada2161004140130ve00e5873qc38aebaa842d3b6e@mail.gmail.com \
--to=oguzyilmazlist@gmail.com \
--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).