[FEATURE] Add an inbound user for Data usage

[tkkost]

Hello.
I think it would be logical to add a breakdown of data by inbound user. Due to NAT, different users can come from the same IP address. The same inbound user can also connect from different IP addresses.

[kunish]

Thanks for the suggestion — breaking traffic/data down by inbound user makes sense for multi-user setups behind NAT.

Feasibility note: the dashboard can only surface what the core exposes. Connections from the core's API do include metadata.inboundUser (the connections table already shows an "Inbound User" column), so per-user grouping of live connections is feasible. However, persistent cumulative data usage per inbound user would need the core to track and expose that over time — the clash API doesn't currently provide a per-user usage total.

So this likely splits into two parts:

1. Dashboard side: group / filter connections by inbound user (feasible today).
2. Core side: expose cumulative per-user data usage (needs a mihomo feature first — worth opening at https://github.com/MetaCubeX/mihomo).

Keeping this open as a feature discussion.

[github-actions]

This issue has been inactive for 30 days and is now marked as stale. It will be closed in 7 days if there is no further activity.