Hi Mudfish team,
I use Mudfish 2.7.10 on a GL.iNet Flint GL-AX1800 with an Xbox Series S. I’m tuning a custom Titanfall 2 item so match traffic goes through a Mudfish node and multiplayer lobby traffic goes directly to the game server.
My workflow is to leave a monitor open while I’m in the lobby. If game traffic starts going through the relay, I want an indicator to light up within a few seconds. That tells me when to start a LAN packet capture, identify the destination IP and port, and verify whether the new lobby address should be added to Exclude Custom Traffic .
In one test, I confirmed that traffic to 54.115.53.182:38116/UDP went directly through the WAN with the exclusion active. Realtime Traffic Usage still increased. The dashboard reads its Input and Output totals from /do/status/netstat/msk , which makes the local counter difficult to use as a trigger.
Could you add a live Idle / Relaying game traffic indicator or a relay-only byte or packet rate that updates every 3–5 seconds? Ideally, it would show application traffic after exclusion rules are applied, with direct traffic, keepalives, and RTT probes tracked separately. A per-item view would be especially useful when several items share a node.
A “Tunnel traffic only” option for the existing Realtime Traffic Usage counter would also work for me. In that mode, Input and Output would count only traffic forwarded through Mudfish nodes. Traffic sent directly because it matches an Exclude Custom Traffic rule would be left out of those totals.
If the router build already exposes this through a dashboard view, CLI command, or read-only local API, could you share how to access it and what it counts? A documented local API would also let me build the indicator on a separate device.
Thanks.