Problem / Use Case
Hi, have you ever thought about adding more TCP stats to the details view, like ss -i -t does?
ESTAB 0 0 [2a02:aaaa:bba:cccc::1]:35290 [2001:dddd:dddd:4::1]:imaps
cubic wscale:7,10 rto:229 rtt:28.311/7.017 ato:40 mss:1428 pmtu:1500 rcvmss:1428 advmss:1428 cwnd:10 bytes_sent:13820 bytes_acked:13821 bytes_received:33477 segs_out:521 segs_in:406 data_segs_out:296 data_segs_in:350 send 4.04Mbps lastsnd:112832 lastrcv:112804 lastack:12320 pacing_rate 8.07Mbps delivery_rate 860kbps delivered:297 app_limited busy:9124ms rcv_space:14280 rcv_ssthresh:91993 minrtt:16.201 snd_wnd:64128 rcv_wnd:92160
Unfortunately these informations are not available via /proc/net/tcp, but only via netlinks INET_DIAG_INFO. I have no clue how these things works on macOS.
Proposed Solution
I vibe coded a implementation which works fine for me at https://github.com/Worty/snitch/tree/tcp-details , but wanted to ask if you like the idea before I put more effort in it for a PR.
There are some other interesting fields, such as app_limited busy, send/receive windows (scale) and pmtu, but I haven't added them yet.
If you want, I can open a draft PR.
Alternatives Considered
No response
Area
TUI (interactive mode)
Additional Context
No response
Contribution
Problem / Use Case
Hi, have you ever thought about adding more TCP stats to the details view, like
ss -i -tdoes?Unfortunately these informations are not available via
/proc/net/tcp, but only via netlinksINET_DIAG_INFO. I have no clue how these things works on macOS.Proposed Solution
I vibe coded a implementation which works fine for me at https://github.com/Worty/snitch/tree/tcp-details , but wanted to ask if you like the idea before I put more effort in it for a PR.
There are some other interesting fields, such as app_limited busy, send/receive windows (scale) and pmtu, but I haven't added them yet.
If you want, I can open a draft PR.
Alternatives Considered
No response
Area
TUI (interactive mode)
Additional Context
No response
Contribution