netdev - Re: Bug in netlink monitor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 26 Oct 2022 10:34:20 +0200
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     George Shuklin <george.shuklin@...il.com>, netdev@...r.kernel.org
Subject: Re: Bug in netlink monitor

Le 25/10/2022 à 13:18, George Shuklin a écrit :
> I found that if veth interface is created in a namespace using netns option for
> ip, no events are logged in `ip monitor all-nsid`.
> 
> Steps to reproduce:
> 
> 
> (console1)
> 
> ip monitor all-nsid
> 
> 
> (console 2)
> 
> ip net add foobar
> 
> ip link add netns foobar type veth
> 
> 
> Expected results:
> 
> Output in `ip monitor`. Actual result: no output, (but there are two new veth
> interaces in foobar namespace).
> 
> Additional observation: namespace 'foobar' does not have id in output of `ip net`:
This is why.
https://man7.org/linux/man-pages/man8/ip-monitor.8.html

"       If the all-nsid option is set, the program listens to all network
       namespaces that have a nsid assigned into the network namespace
       were the program is running"

You can assign one with:
ip netns set foobar auto

Regards,
Nicolas

> 
> # ip net
> foobar
> test (id: 0)
> test2 (id: 1)
>