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
Relevant "shorewall show mangle" output is:
Chain tcpost (1 references)
pkts bytes target prot opt in out source destination
0 0 CLASSIFY tcp -- lan1 wan1 192.168.10.10 0.0.0.0/0 tcp dpt:22
CLASSIFY set 1:11
0 0 CLASSIFY all -- * wan1 0.0.0.0/0 0.0.0.0/0 MARK match
0x1/0xff CLASSIFY set 1:11
0 0 CLASSIFY all -- * wan1 0.0.0.0/0 0.0.0.0/0 MARK match
0xfe/0xff CLASSIFY set 1:1254
Man iptables says:
-i, --in-interface [!] name
Name of an interface via which a packet was received (only for packets entering the
INPUT, FORWARD and PREROUTING chains). When the "!" argument is used before the interface
name, the sense is inverted. If the interface name ends in a "+", then any interface which
begins with this name will match. If this option is omitted, any interface name will match.
But iptables is taking the -i option in case of POSTROUTING as well. In my case, I were trying to
classify traffic coming from lan1:192.168.10.10 and although this rule was taken it was not being
hit because I understand from what Tom Eastep said, "It is because packets in the Postrouting chain
are not guaranteed to even have an input chain"
-justin
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
