netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Shuklin <george.shuklin@gmail.com>
To: nicolas.dichtel@6wind.com, netdev@vger.kernel.org
Subject: Re: Bug in netlink monitor
Date: Wed, 26 Oct 2022 15:41:42 +0300	[thread overview]
Message-ID: <9753a024-5499-af09-ccc2-21c3c614ea64@gmail.com> (raw)
In-Reply-To: <037d30a7-15e3-34c7-8fdd-2cf356430355@6wind.com>

On 26/10/2022 11:34, Nicolas Dichtel wrote:
> 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
>
Oh, I missed that.

But I think it's making things a bit odd, because there are network 
events in the system which are not visible in `ip monitor` (no matter 
what options are set).

Are there a way to see _all_ network events?



  reply	other threads:[~2022-10-26 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 11:18 Bug in netlink monitor George Shuklin
2022-10-26  8:34 ` Nicolas Dichtel
2022-10-26 12:41   ` George Shuklin [this message]
2022-10-26 13:31     ` Nicolas Dichtel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9753a024-5499-af09-ccc2-21c3c614ea64@gmail.com \
    --to=george.shuklin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).