lkml.org 
[lkml]   [2017]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] netlink: Add netns check on taps
From
Date
On 12/06/2017 08:40 PM, David Miller wrote:
> From: Kevin Cernekee <cernekee@chromium.org>
> Date: Tue, 5 Dec 2017 14:46:22 -0800
>
>> Currently, a nlmon link inside a child namespace can observe systemwide
>> netlink activity. Filter the traffic so that in a non-init netns,
>> nlmon can only sniff netlink messages from its own netns.
>>
>> Test case:
>>
>> vpnns -- bash -c "ip link add nlmon0 type nlmon; \
>> ip link set nlmon0 up; \
>> tcpdump -i nlmon0 -q -w /tmp/nlmon.pcap -U" &
>> sudo ip xfrm state add src 10.1.1.1 dst 10.1.1.2 proto esp \
>> spi 0x1 mode transport \
>> auth sha1 0x6162633132330000000000000000000000000000 \
>> enc aes 0x00000000000000000000000000000000
>> grep abc123 /tmp/nlmon.pcap
>>
>> Signed-off-by: Kevin Cernekee <cernekee@chromium.org>
>
> Daniel, what behavior did you intend this to have?
>
> Taps can see their own namespace only, or init_net is special
> and can see all netlink activity.
>
> I think letting init_net see everything could be confusing,
> because there is no way to distinguish netlink events by
> namespace just by looking at the messages that arrive at
> the tap right?

Yeah, only snooping from own netns makes sense, lets limit
it to this.

\
 
 \ /
  Last update: 2017-12-06 21:52    [W:0.149 / U:0.892 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site