On Wed, Apr 26, 2017 at 5:15 PM, Willem de Bruijn
wrote:
>>> The patch breaks backward/forward compatibility in a match/target.
>>>
>>> When the list of the revisions of a given match/target of iptables is not
>>> exactly the same as for the kernel counter part (when the kernel module
>>> supports
>> The patch breaks backward/forward compatibility in a match/target.
>>
>> When the list of the revisions of a given match/target of iptables is not
>> exactly the same as for the kernel counter part (when the kernel module
>> supports less revisions than iptables), then in spite of the supported
On 25 April 2017 at 15:18, Pablo Neira Ayuso wrote:
>>
>> Yes. The timer based approach is... timer based (async).
>>
>> It doesn't fit in an environment where you need to sync events as soon
>> as they happen.
>
> IIRC the timer based works like this:
>
> 1) If event occurs, sync message is send.
Print elements per line instead of all in a single line.
The elements which can be 'short' are printed 5 per line,
and others, like IPv4 addresses are printed 2 per line.
Example:
% nft list ruleset -nnn
table ip t {
set s {
type inet_service
elements = { 1
On 26 April 2017 at 00:00, Pablo M. Bermudo Garay wrote:
> 2017-04-25 14:35 GMT+02:00 Arturo Borrero Gonzalez :
>> Print elements per line instead of all in a single line.
>> The elements which can be 'short' are printed 5 per line,
>> and others, like IPv4 addresses are printed 2 per line.
>
> Th
