RE: [net-next v2] tipc: add loopback device tracking

2019-06-24 Thread Jon Maloy
> -Original Message- > From: netdev-ow...@vger.kernel.org On > Behalf Of David Miller > Sent: 24-Jun-19 10:29 > To: John Rutherford > Cc: netdev@vger.kernel.org > Subject: Re: [net-next v2] tipc: add loopback device tracking > > From: john.rutherf...@dek

Re: [net-next v2] tipc: add loopback device tracking

2019-06-24 Thread David Miller
From: john.rutherf...@dektech.com.au Date: Mon, 24 Jun 2019 16:44:35 +1000 > Since node internal messages are passed directly to socket it is not > possible to observe this message exchange via tcpdump or wireshark. > > We now remedy this by making it possible to clone such messages and send > th

[net-next v2] tipc: add loopback device tracking

2019-06-23 Thread john . rutherford
Since node internal messages are passed directly to socket it is not possible to observe this message exchange 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 f