Re: [tipc-discussion] TIPC Packet statistics

[Jon M. <jm...@re...>]

On 12/13/22 02:30, Harish Chandrasekaran wrote:
> Hello all,
>
> I'm looking for a utility/command to get the tipc packet/connection
> information while running the client and server within the same
> card/kernel.
>
> The "tipc link statistics show" gives some insights regarding the packets
> across the bearers
> Link <10300411:BEARER1-10300431:BEARER-2>
>    ACTIVE  MTU:14000  Priority:10  Tolerance:1500 ms  Window:50 packets
>    RX packets:9013188 fragments:0/0 bundles:0/0
>    TX packets:9430977 fragments:760/190 bundles:0/0
>    TX profile sample:613736 packets average:42 octets
>    0-64:93% -256:7% -1024:0% -4096:0% -16384:0% -32768:0% -66000:0%
>    RX states:2155490 probes:423110 naks:8365 defs:11806 dups:11875
>    TX states:2199617 probes:413191 naks:11866 acks:290 retrans:8371
>    Congestion link:0  Send queue max:0 avg:0
>
>
> I'm looking for something similar to the above or something similar to what
> netstat provides for tcp packets/connections with in the same card/machine
>
> netstat -s
> Tcp:
>      1312727 active connection openings
>      325217 passive connection openings
>      987300 failed connection attempts
>      9 connection resets received
>      41 connections established
>      84939296 segments received
>      86976822 segments sent out
>      985790 segments retransmitted
>      0 bad segments received
>      1821 resets sent
>
> Eg: The  hello_server and hello_client run on the same machine. I would
> like to check if there are any naks or duplicates or packet drops or if
> there are any connection resets or failed connection attempts.
>
> I tried to check if *netstat statistics *captures TIPC connection related
> information but it doesn't seem to capture the TIPC related info.
>
> Kindly let me know if there are any utilities or TIPC commands which I can
> use to gather such information?
>
> Would greatly appreciate any help.
>
> Sincerely,
> Harish

Hi,
Sorry for a late answer.
It is actually possible to observe node internal traffic with 
tcpdump/wireshark
if  you activate network taps for the loopback device.
The following commit explains it:

commit 6c9081a3915dc0782a8f1424343b794f2cf53d9c
Author: John Rutherford <joh...@de...>
Date:   Wed Aug 7 12:52:29 2019 +1000

     tipc: add loopback device tracking

     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 <joh...@de...>
     Acked-by: Jon Maloy <jon...@er...>
     Acked-by: Ying Xue <yin...@wi...>
     Signed-off-by: David S. Miller <da...@da...>


Thanks
///jon


>
> _______________________________________________
> tipc-discussion mailing list
> tip...@li...
> https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>