Re: bug in iptables

[justin joseph <justin.cok@gmail.com>]

Patrick McHardy wrote:
> justin joseph wrote:
>>
>>
>> justin joseph wrote:
>>> Hi,
>>
>>
>>> It seems to be there in iptables as well.
>>
>> To be specific I am able to add a rule thus:
>>
>> iptables -t mangle -A tcpost -i lan1 -s 192.168.10.10 -o wan1 -p tcp 
>> --dport 22 -j CLASSIFY --set-class 1:11
> 
> 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:~#