Re: [RFC PATCH iproute2] tc: let m_ipt work with new iptables API headers

2016-06-14 Thread Stephen Hemminger
On Sun, 29 May 2016 20:27:13 +0200 Alexander Aring wrote: > Since commit 5cd1adb ("Update to current iptables headers") the build > with m_ipt.o and the following config will fail: > > TC_CONFIG_XT:=n > TC_CONFIG_XT_OLD:=n > TC_CONFIG_XT_OLD_H:=n > > This patch renames "iptables_target" to "xta

Re: [RFC PATCH iproute2] tc: let m_ipt work with new iptables API headers

2016-06-12 Thread Alexander Aring
Hi, On 05/29/2016 08:27 PM, Alexander Aring wrote: > Since commit 5cd1adb ("Update to current iptables headers") the build > with m_ipt.o and the following config will fail: > > TC_CONFIG_XT:=n > TC_CONFIG_XT_OLD:=n > TC_CONFIG_XT_OLD_H:=n > > This patch renames "iptables_target" to "xtables_ta

[RFC PATCH iproute2] tc: let m_ipt work with new iptables API headers

2016-05-29 Thread Alexander Aring
Since commit 5cd1adb ("Update to current iptables headers") the build with m_ipt.o and the following config will fail: TC_CONFIG_XT:=n TC_CONFIG_XT_OLD:=n TC_CONFIG_XT_OLD_H:=n This patch renames "iptables_target" to "xtables_target" and some other things which gets renamed and I noticed while re