All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramunas Vabolis <ramuva@openoffice.lt>
To: netfilter@vger.kernel.org
Subject: Re: raw table and NOTRACK target
Date: Fri, 26 Jun 2009 10:43:17 +0300	[thread overview]
Message-ID: <20090626074317.GA11753@openoffice.lt> (raw)
In-Reply-To: <1246000121.3985.5.camel@casper.meteor.dp.ua>

> > 
> Pay attention to order. As far as I understood your rule order is like
> this:
> 
> -t raw -A PREROUTING -j NOTRACK
> -t raw -A PREROUTING -p tcp -s host.ip --dport 80 -j RETURN
> -t raw -A PREROUTING -p tcp -d host.ip --sport 80 -j RETURN
<skipped>
Thank you for pointing this out, but I already well aware of that.
That's why I'm using -I to prepend rules to begining of the chain.

The first rule is hit - I can verify that with iptables -t raw -vxnL.
But it seems if packet is RETURNed of ACCEPTed in raw chain it is
removed from further processing (I'm running tcpdump on my router and I
see packet entering in local interface but it does not appear in my
outgoing interface). 

So exact steps to replicate the behaviour:

iptables -t raw -A PREROUTING -p tcp -s real.ip --dport 80 -j RETURN
iptables -t raw -A PREROUTING -p tcp -d real.ip --sport 80 -j RETURN
iptables -t raw -A PREROUTING -j NOTRACK

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.

  reply	other threads:[~2009-06-26  7:43 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 [this message]
2009-06-26  7:53     ` Philip Craig
2009-06-26  8:20       ` Ramunas Vabolis
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=20090626074317.GA11753@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 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.