Hi,

W dniu 31.05.2013 09:29, Andreas Henriksson napisał(a):
My recommendation, if you need the ipt/xt module is that you try
two things:

Easiest thing to test first:
use "xt" instead of "ipt".... the ipt module is obsolete and
just a compat symlink to "xt" nowadays....

After reverting iproute to stable:

tc filter add dev eth1 parent ffff: protocol ip prio 10 u32 match u32 0 0 flowid 1:1 action xt -j MARK --set-mark 1 action mirred egress redirect dev ifb0
xt: unrecognized option '--set-mark'
Naruszenie ochrony pamięci
#(eng: Segfault)

tc filter add dev eth1 parent ffff: protocol ip prio 10 u32 match u32 0 0 flowid 1:1 action xt -j CONNMARK action mirred egress redirect dev ifb0
tablename: mangle hook: NF_IP_PRE_ROUTING
        target:  CONNMARK and 0x0 index 0
RTNETLINK answers: No such file or directory
We have an error talking to the kernel

More likely to fix the problem:
Rebuild (any version of) the iproute(2) package on YOUR system.
This means it will definitely be built against the version
of iptables/libxtables on your installation!

Make sure you have deb-src lines in your /etc/apt/sources.list(.d/*)
apt-get update

apt-get build-dep iproute
cd /tmp
apt-get source iproute
cd iproute*
dpkg-buildpackage -uc -us
dpkg -i ../iproute*.deb

After building (20120521-3 / wheezy stable), installing and rebooting:

tc filter add dev eth1 parent ffff: protocol ip prio 10 u32 match u32 0 0 flowid 1:1 action xt -j MARK --set-mark 1 action mirred egress redirect dev ifb0
xt: unrecognized option '--set-mark'
Naruszenie ochrony pamięci
#(eng: Segfault)

tc filter add dev eth1 parent ffff: protocol ip prio 10 u32 match u32 0 0 flowid 1:1 action xt -j CONNMARK --restore-mark action mirred egress redirect dev ifb0
xt: unrecognized option '--restore-mark'
Naruszenie ochrony pamięci
#(eng: Segfault)

Please report back if any of the above was successful or not!

Should I try rebuilding any other packages (like iptables)?

Cheers,
--
Piotr Janusz


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to