tipc: add loopback device tracking
Subsystems (3)
PATCH v3 1/1 tipc: add loopback device tracking
From: John Rutherford <[email protected]>
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.
--- net/tipc/bcast.c | 4 +++- net/tipc/bearer.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ net/tipc/bearer.h | 10 +++++++++ net/tipc/core.c | 5 +++++ net/tipc/core.h | 3 +++ net/tipc/node.c | 1 + net/tipc/topsrv.c | 2 ++ 7 files changed, 88 insertions(+), 1 deletion(-)
net/tipc/bcast.c +3 -1
@@ -406,8 +406,10 @@ int tipc_mcast_xmit(struct net *net, struct sk_buff_head *pkts, rc =tipc_bcast_xmit (net, pkts, cong_link_cnt); } -if (dests->local) +if (dests->local) { +tipc_loopback_trace (net, &localq);tipc_sk_mcast_rcv (net, &localq, &inputq); + } exit:/* This queue should normally be empty by now */ __skb_queue_purge (pkts);
net/tipc/bearer.c +64 -0
76 lines not on this page · raw message
net/tipc/bearer.h +10 -0
@@ -232,6 +232,16 @@ void tipc_bearer_xmit(struct net *net, u32 bearer_id, struct tipc_media_addr *dst);void tipc_bearer_bc_xmit (struct net *net,u32 bearer_id,struct sk_buff_head *xmitq); +void tipc_clone_to_loopback (struct net *net,struct sk_buff_head *pkts); +int tipc_attach_loopback (struct net *net); +void tipc_detach_loopback (struct net *net); + +static inline void tipc_loopback_trace (struct net *net, +struct sk_buff_head *pkts) +{ +if (unlikely (dev_nit_active (net->loopback_dev))) +tipc_clone_to_loopback (net, pkts); +}/* check if device MTU is too low for tipc headers */ static inline bool tipc_mtu_bad (struct net_device *dev,unsigned int reserve)
net/tipc/core.c +5 -0
@@ -82,6 +82,10 @@ static int __net_init tipc_init_net(struct net *net)if (err) goto out_bclink; + err =tipc_attach_loopback (net); +if (err) + goto out_bclink; +return 0 ; out_bclink:
@@ -94,6 +98,7 @@ static int __net_init tipc_init_net(struct net *net) static void __net_exit tipc_exit_net(struct net *net) { +tipc_detach_loopback (net);tipc_net_stop (net);tipc_bcast_stop (net);tipc_nametbl_stop (net);
net/tipc/core.h +3 -0
@@ -125,6 +125,9 @@ struct tipc_net {/* Cluster capabilities */ u16 capabilities; + +/* Tracing of node internal messages */ +struct packet_type loopback_pt; };static inline struct tipc_net *tipc_net (struct net *net)
net/tipc/node.c +1 -0
@@ -1443,6 +1443,7 @@ int tipc_node_xmit(struct net *net, struct sk_buff_head *list,int rc;if (in_own_node (net, dnode)) { +tipc_loopback_trace (net, list);tipc_sk_rcv (net, list);return 0 ; }
net/tipc/topsrv.c +2 -0
@@ -40,6 +40,7 @@#include "socket.h" #include "addr.h" #include "msg.h" +#include "bearer.h" #include <net/sock.h> #include <linux/module.h>
@@ -608,6 +609,7 @@ static void tipc_topsrv_kern_evt(struct net *net, struct tipc_event *evt)memcpy (msg_data (buf_msg (skb)), evt,sizeof (*evt));skb_queue_head_init (&evtq);__skb_queue_tail (&evtq, skb); +tipc_loopback_trace (net, &evtq);tipc_sk_rcv (net, &evtq); }
Signature · 1 line
2.11.0
From: [email protected]
Date: Wed, 7 Aug 2019 12:52:29 +1000
Quoted 13 lines
From: John Rutherford <[email protected]>
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.
Quoted 6 lines
v3 - Function
dev_nit_activeused to check for network taps.
- Procedurenetif_rx_niused to send cloned messages to loopback device.Signed-off-by John Rutherford <[email protected]>Acked-by Jon Maloy <[email protected]>Acked-by Ying Xue <[email protected]>
Applied, thank you.