netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: justin joseph <justin.cok@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: bug in iptables
Date: Fri, 22 Feb 2008 15:08:26 +0100	[thread overview]
Message-ID: <47BED75A.9090204@trash.net> (raw)
In-Reply-To: <47BE7917.1030301@gmail.com>

justin joseph wrote:
> Patrick McHardy wrote:
>> Your example doesn't contain the rule jumping to "tcpost", so
>> its not clear whether this really is a bug. Please post all
>> four rules (tcpost and -j tcpost) and the kernel version you're
>> using.
>>
> 
> Chain POSTROUTING (policy ACCEPT 2263 packets, 528K bytes)
>  pkts bytes target     prot opt in     out     source               
> destination
>  2227  523K MARK       all  --  any    any     anywhere             
> anywhere            MARK and 0xff
>  2227  523K tcpost     all  --  any    any     anywhere             
> anywhere
> 
> Chain tcfor (1 references)
>  pkts bytes target     prot opt in     out     source               
> destination
> 
> Chain tcout (1 references)
>  pkts bytes target     prot opt in     out     source               
> destination
> 
> Chain tcpost (1 references)
>  pkts bytes target     prot opt in     out     source               
> destination
>     0     0 CLASSIFY   tcp  --  lan1   wan1    anywhere             
> anywhere            tcp dpt:ssh CLASSIFY set 1:11
>     0     0 CLASSIFY   all  --  any    wan1    anywhere             
> anywhere            MARK match 0x1/0xff CLASSIFY set 1:11
>     0     0 CLASSIFY   all  --  any    wan1    anywhere             
> anywhere            MARK match 0xfe/0xff CLASSIFY set 1:1254
> 
> 
> root@hq.enpaq:~# uname -r
> 2.6.15-29-386
> root@hq.enpaq:~#


Thanks, I can reproduce it on current -git. I'll look into it.


  reply	other threads:[~2008-02-22 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 18:38 bug in iptables justin joseph
2008-02-15  6:50 ` justin joseph
2008-02-19 12:28   ` Patrick McHardy
2008-02-22  7:26     ` justin joseph
2008-02-22 14:08       ` Patrick McHardy [this message]
2008-02-22 14:47         ` Patrick McHardy
2008-02-27 12:07           ` Patrick McHardy

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=47BED75A.9090204@trash.net \
    --to=kaber@trash.net \
    --cc=justin.cok@gmail.com \
    --cc=netfilter-devel@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).