[feature]: Show the VRF that the listener is bound to

[frantathefranta]

Problem / Use Case

Hi, I've been using snitch for a few weeks now and I'm a big fan. I have found that I'm missing a functionality that I can see in something like ss, that is showing which VRF a listener is bound to. Example from ss -puta:

$ ss -puta
Netid      State       Recv-Q      Send-Q                            Local Address:Port                                     Peer Address:Port      Process
udp        UNCONN      0           0                                  0.0.0.0%dn42:bfd-control                                   0.0.0.0:*
udp        UNCONN      0           0                                  0.0.0.0%dn42:bfd-multi-ctl                                 0.0.0.0:*
udp        UNCONN      0           0                                     [::]%dn42:bfd-control                                      [::]:*
udp        UNCONN      0           0                                     [::]%dn42:bfd-multi-ctl                                    [::]:*
[...]

AFAICT this isn't visible in snitch for now, I'd imagine it'd be somewhere like here:

  connection details
  ────────────────────────────────────────

  process  –
  cmdline  –
  cwd  –
  pid  –
  user  –
  protocol  udp
  state  LISTEN
  local  *:3784
  remote  *:0
  interface  –
  inode  375772192

  press esc to close

I don't know if it's possible to query VRF information from /proc/net though. I'd like to contribute but I don't have enough experience with querying information from low-level interfaces (like /proc/net).

Proposed Solution

It'd be nice if VRF information was shown.

Alternatives Considered

No response

Area

TUI (interactive mode)

Additional Context

It'd be nice to implement it either like the ss output:

  state  LISTEN
  local  *%<vrf>:3784
  remote  *:0
  interface  –

Or another detail like this:

  state  LISTEN
  local  *:3784
  vrf: <vrf>
  remote  *:0
  interface  –

Contribution

• I'd be willing to submit a PR for this feature

[karol-broda]

interesting, i didnt know about vrf binding info in proc. will look into whether its available from /proc/net or if it needs netlink. if you want to take a stab at it the pr is welcome :)