> -----Original Message-----
> From: netdev-ow...@vger.kernel.org <netdev-ow...@vger.kernel.org> On
> Behalf Of David Miller
> Sent: 24-Jun-19 10:29
> To: John Rutherford <john.rutherf...@dektech.com.au>
> Cc: netdev@vger.kernel.org
> Subject: Re: [net-next v2] tipc: add loopback device tracking
>
> 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 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 turned on/off by enabling/disabling the loopback "bearer"
> > "eth:lo".
> >
> > Acked-by: Jon Maloy <jon.ma...@ericsson.com>
> > Signed-off-by: John Rutherford <john.rutherf...@dektech.com.au>
>
> What a waste, just clone the packet, attach loopback to it, and go:
>
> if (dev_nit_active(loopback_dev))
> dev_queue_xmit_nit(skb, loopback_dev);
I was never quite happy with this patch, so thank you for the feedback!
///jon
