From: David Miller <davem@davemloft.net>
To: john.rutherford@dektech.com.au
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [net-next v3] tipc: add loopback device tracking
Date: Thu, 08 Aug 2019 22:11:50 -0700 (PDT) [thread overview]
Message-ID: <20190808.221150.639978383290842870.davem@davemloft.net> (raw)
In-Reply-To: <20190807025229.1599-1-john.rutherford@dektech.com.au>
From: john.rutherford@dektech.com.au
Date: Wed, 7 Aug 2019 12:52:29 +1000
> From: John Rutherford <john.rutherford@dektech.com.au>
>
> Since node internal messages are passed directly to the socket, it is not
> possible to observe those messages via tcpdump or wireshark.
>
> We now remedy this by making it possible to clone such messages and send
> the clones to the loopback interface. The clones are dropped at reception
> and have no functional role except making the traffic visible.
>
> The feature is enabled if network taps are active for the loopback device.
> pcap filtering restrictions require the messages to be presented to the
> receiving side of the loopback device.
>
> v3 - Function dev_nit_active used to check for network taps.
> - Procedure netif_rx_ni used to send cloned messages to loopback device.
>
> Signed-off-by: John Rutherford <john.rutherford@dektech.com.au>
> Acked-by: Jon Maloy <jon.maloy@ericsson.com>
> Acked-by: Ying Xue <ying.xue@windriver.com>
Applied, thank you.
prev parent reply other threads:[~2019-08-09 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 2:52 [net-next v3] tipc: add loopback device tracking john.rutherford
2019-08-09 5:11 ` David Miller [this message]
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=20190808.221150.639978383290842870.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=john.rutherford@dektech.com.au \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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