[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.01.1206301512520.27385@frira.zrqbmnf.qr>
Date: Sat, 30 Jun 2012 15:17:55 +0200 (CEST)
From: Jan Engelhardt <jengelh@...i.de>
To: Andreas Henriksson <andreas@...al.se>
cc: shemminger@...tta.com,
Linux Networking Developer Mailing List
<netdev@...r.kernel.org>, YANG Zhe <yangzhe1990@...il.com>
Subject: Re: problems with iproute2 m_xt again...
On Saturday 2012-06-30 14:09, Andreas Henriksson wrote:
>Hello!
>
>Mailing you in hope that you could help out with the xt module of iproute2 tc
>once more, as you've done in the past.... It seems to be broken again. sigh.
>
>amd64:~# iptables -nL | grep test
>Chain test (0 references)
>amd64:~# tc filter add dev fon parent ffff: protocol ip prio 10 u32 action xt -j test
> failed to find target test
>
>bad action parsing
>parse_action: bad value (3:xt)!
>Illegal "action"
>amd64:~#
Looks more like a syntax error. I don't see any functions of m_xt.so
being ever called (and it only has two).
>And maybe even more interesting is when I try to use a built-in chain
>like DROP:
DROP is not a chain, but a verdict.
>amd64:~# tc filter add dev fon parent ffff: protocol ip prio 10 u32
>action xt -j DROP
>tablename: mangle hook: NF_IP_PRE_ROUTING
>Segmentation fault
Rather than a segfault, this gets me "bad action parsing" in
iproute2-3.4.0 as well.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists