On 2015-05-13 at 11:54:01 +0200, Vadim Kochan vadi...@gmail.com wrote:
On Wed, May 13, 2015 at 11:45:16AM +0200, Daniel Borkmann wrote:
On 05/13/2015 11:31 AM, Vadim Kochan wrote:
On Wed, May 13, 2015 at 11:24:11AM +0200, Daniel Borkmann wrote:
On 05/13/2015 11:21 AM, Vadim Kochan wrote:
On 2015-05-20 at 16:34:44 +0200, Vadim Kochan vadi...@gmail.com wrote:
On Wed, May 20, 2015 at 04:30:30PM +0200, Tobias Klauser wrote:
On 2015-05-13 at 11:54:01 +0200, Vadim Kochan vadi...@gmail.com wrote:
On Wed, May 13, 2015 at 11:45:16AM +0200, Daniel Borkmann wrote:
On 05/13/2015
On Wed, May 13, 2015 at 11:08:01AM +0200, Daniel Borkmann wrote:
On 05/10/2015 02:37 PM, Vadim Kochan wrote:
From: Vadim Kochan vadi...@gmail.com
Since Netlink messages are written in default pcap format there is no
way to identify Netlink family by socket protocol number, so
use pcap
On Wed, May 13, 2015 at 12:18:37PM +0300, Vadim Kochan wrote:
On Wed, May 13, 2015 at 11:08:01AM +0200, Daniel Borkmann wrote:
On 05/10/2015 02:37 PM, Vadim Kochan wrote:
From: Vadim Kochan vadi...@gmail.com
Since Netlink messages are written in default pcap format there is no
way to
On 05/10/2015 02:37 PM, Vadim Kochan wrote:
From: Vadim Kochan vadi...@gmail.com
Since Netlink messages are written in default pcap format there is no
way to identify Netlink family by socket protocol number, so
use pcap cooked header for Netlink messages as described here:
