From: Ramunas Vabolis <ramuva@openoffice.lt>
To: netfilter@vger.kernel.org
Subject: Re: raw table and NOTRACK target
Date: Fri, 26 Jun 2009 11:20:58 +0300 [thread overview]
Message-ID: <20090626082058.GA15490@openoffice.lt> (raw)
In-Reply-To: <4A447E89.7020700@snapgear.com>
* Philip Craig <philipc@snapgear.com> [2009-06-26 10:54]:
> Ramunas Vabolis wrote:
> > running lynx http://any.host.com from real.ip
> >
> > running tcpdump on inner interface:
> > tcpdump -i ethlocal -n host real.ip and port 80
> >
> > does show connection attempts while
> > tcpdump -i ethoutside -n host real.ip and port 80
> > is silent.
> >
> > iptables -t raw -vxnL shows that first rule is hit couple times, the
> > second rule is never hit.
>
> Then the problem is not in the raw table. Something else is dropping
> the first syn packet after it has been through the raw table.
> You should see an outgoing syn packet before you start worrying
> about the second rule being hit.
That's why I'm asking for advice :)
iptables -n -L |grep DROP -> is empty. I'd paste entire iptables
output, but it is quite biggie (There are quite a lot of chains which do
nothing but ACCEPT packets - for iptables based traffic accounting
solution). I've flushed all FORWARD chain just in case, but it did not
had any influence as I've suspected.
What else can be done to pinpoint the problem?
next prev parent reply other threads:[~2009-06-26 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 13:05 raw table and NOTRACK target Ramunas Vabolis
2009-06-26 7:08 ` Покотиленко Костик
2009-06-26 7:43 ` Ramunas Vabolis
2009-06-26 7:53 ` Philip Craig
2009-06-26 8:20 ` Ramunas Vabolis [this message]
2009-06-26 12:52 ` Покотиленко Костик
2009-06-26 13:09 ` Ramunas Vabolis
2009-06-26 13:31 ` Покотиленко Костик
2009-06-29 7:33 ` Ramunas Vabolis
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=20090626082058.GA15490@openoffice.lt \
--to=ramuva@openoffice.lt \
--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