linux-kernel - ipt_MARK/xt_MARK usage problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Aug 2006 08:21:40 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	netfilter@...ts.netfilter.org
Subject: ipt_MARK/xt_MARK usage problem

Hello,

kernel 2.6.17 ships with xt_MARK, but iptables 1.3.5 still uses ipt_MARK. 
In essence, I cannot use `iptables -j MARK` giving me 

# iptables -A INPUT -j MARK --set-mark 1
iptables: Unknown error 4294967295

I have seen this before and the problem behind this strange error (-1) is 
that the .targetsize/.matchsize variables in the kernel modules do not 
match their userspace parts.

However, this time it seems to be something different:

# iptables -t mangle -A INPUT -j MARK --set-mark 1

Works without problems. Am I missing something?
How do I get MARK back to work in -t filter -- possibly without hacking in 
xt_MARK.c?

Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/