Dear friend,
My name is Mr.Payton Rupali. I am working with one of the prime banks in
Burkina Faso. Here in this bank existed a dormant account for many years, which
belong to one of our late foreign customer. The amount in this account stands
at $13,300,000.00 (Thirteen Million Three Hundred
This is a partial revert of commit 7462e4aa757dc28e74b4a731b3ee13079b04ef23
("iptables-compat: Keep xtables-config and xtables-events out from tree")
and re-adds xtables-events under a new name, with a few enhancements,
this is --trace mode, which replaces printk-based tracing, and an
imroved
nft meta expr enables the nfnetlink based trace infrastruvture, so
prefer to use that rather than xt_TRACE.
Signed-off-by: Florian Westphal
---
iptables/nft-shared.c | 65 +--
iptables/nft-shared.h | 5
iptables/nft.c| 25 +
needed to get the TRACE definition.
Signed-off-by: Florian Westphal
---
include/linux/netfilter.h | 15 +-
include/linux/netfilter/nf_tables.h | 680 +++-
include/linux/netfilter/nfnetlink.h | 16 +
3 files changed, 703 insertions(+), 8 deletions(-)
diff
On 17 June 2018 at 13:30, Arturo Borrero Gonzalez wrote:
> On 17 June 2018 at 09:22, Phil Sutter wrote:
>> With libnftables documentation being upstream and one confirmed external
>> user (nftlb), time to break the API!
>>
>> First of all, the command buffer passed to nft_run_cmd_from_buffer may
On 17 June 2018 at 09:22, Phil Sutter wrote:
> With libnftables documentation being upstream and one confirmed external
> user (nftlb), time to break the API!
>
> First of all, the command buffer passed to nft_run_cmd_from_buffer may
> (and should) be const. One should consider it a bug if that
With libnftables documentation being upstream and one confirmed external
user (nftlb), time to break the API!
First of all, the command buffer passed to nft_run_cmd_from_buffer may
(and should) be const. One should consider it a bug if that function
ever changed it's content.
On the other hand,
