From: Liping Zhang
First, log prefix will be truncated to NF_LOG_PREFIXLEN-1, i.e. 127,
at nf_log_packet(), so the extra part is useless.
Second, after adding a log rule with a very very long prefix, we will
fail to dump the nft rules after this _special_ one, but acctually,
they do exist. For e
On 20 January 2017 at 13:02, Arturo Borrero Gonzalez
wrote:
> From: Arturo Borrero Gonzalez
>
duplicated, sorry.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
Hi experts,
I am new to netlink sockets.
In my app , I am getting EPOLLERR in epoll_wait() on netlink socket
continuously.
epoll just notifies that there is a read event on socket (it does not
tell if it is read or epollerr).
What could be cause of this and what EPOLLERR on memory mapped netlink
s
On 2017-01-21 20:12, Patrick PIGNOL wrote:
> Hi all,
>
> I just writen that because I read
>
> "
>
> Determining the pid/subj of a packet is notoriously
> difficult/impossible in netfilter so let's drop that; with proper
> policy/rules you should be able to match proto/port with a given
> proces