I would like to see what settings mudfish is using for the preconfigured items. For example, I would like to know if the Apex Legends item also includes the r5apex_dx12.exe variant when using WFP.
Is there any way to check this?
Okay, I see now that this is visible in the WFP Proxy process logs. That’s good.
However I am now unsure how exactly WFP mode works. I have configured both Apex Legends and FFXIV in WFP mode, so I expect that only those two applications are directed through mudfish. However I see that the system routing tables are still modified, and if I try e.g. a tracert to FFXIV servers it still goes through mudfish.
Does this not defeat the purpose of WFP, since we still have system routes that can consume traffic via other applications (the Twitch, CDN, etc. problem)?
Likewise, if I set up a custom item for FFXIV that attempts to use just the process name without any routes, it does not appear to have any effect. So is WFP mode simply not working for me? Tested again and the custom item seems to work. So why does the preconfigured item always add system routes?
Yes. WFP Proxy log should include all information it handled including the process name and the traffic usage per a connection.
Could you please show me the output of “ROUTE PRINT” command from Command Prompt after the configuration is done? I’m also curious full command of tracert you used.
This action (adding the system routes) is to measure the RTT (ping) graph correctly.
In the mudfish, measuring the ping between user’s PC and the game server is being performed by using ICMP or TCP protocol. But WFP feature could not handle ICMP protocol so it means the realtime RTT graph could not be calculated. To overcome this limication, the preconfigured game item adds a routing table per destinations.
Could you please show me the output of “ROUTE PRINT” command from Command Prompt after the configuration is done? I’m also curious full command of tracert you used.
Mudfish adds these route entries when I enable FFXIV against the Oceanic/Materia servers:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
[snipped other routes to local/work networks]
10.192.0.0 255.192.0.0 10.254.9.1 10.254.9.43 26
10.254.9.0 255.255.255.0 On-link 10.254.9.43 281
10.254.9.43 255.255.255.255 On-link 10.254.9.43 281
10.254.9.255 255.255.255.255 On-link 10.254.9.43 281
27.100.36.143 255.255.255.255 192.168.2.1 192.168.2.44 25
80.239.145.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
103.25.58.148 255.255.255.255 192.168.2.1 192.168.2.44 25
119.252.36.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
119.252.37.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
153.254.80.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
162.14.156.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
183.111.191.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
202.67.52.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
204.2.29.0 255.255.255.0 10.254.9.1 10.254.9.43 5256
224.0.0.0 240.0.0.0 On-link 10.254.9.43 281
255.255.255.255 255.255.255.255 On-link 10.254.9.43 281
I run a raw tracert 153.254.80.81 command. This goes over the Mudfish routes, as expected given what you say about adding system routes to measure RTT.
C:\Windows\System32>tracert 153.254.80.81
Tracing route to 153.254.80.81 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.254.9.1
2 8 ms 13 ms 8 ms 10.254.254.1
3 8 ms 8 ms 7 ms 10.255.249.110
4 8 ms 9 ms 8 ms 103.216.222.47
5 8 ms 8 ms 7 ms core-a.sy3.nsw.au.hostuniversal.com.au [103.216.222.45]
6 8 ms 7 ms 8 ms core-a.sy4.nsw.au.hostuniversal.com.au [103.216.222.3]
7 8 ms 9 ms 8 ms ce-2-0-0.a00.sydnau05.au.bb.gin.ntt.net [202.68.65.108]
8 8 ms 8 ms 8 ms ae-5.r21.sydnau06.au.bb.gin.ntt.net [129.250.7.48]
9 22 ms 10 ms 9 ms ae-0.a00.sydnau06.au.bb.gin.ntt.net [129.250.3.159]
10 8 ms 9 ms 9 ms 199.245.24.25
11 9 ms 8 ms 9 ms 202.68.69.101
12 8 ms 9 ms 7 ms 153.254.80.81
This is a bit unfortunate since I wanted to use WFP mode to reduce the possibility of other non-game connections going through these routes (I also play Apex, which I understand is likely to cause problems with credit usage with Twitch etc streams). Or does WFP mode filter out other applications and the only reason I see these is because I’m doing ICMP traces?
In the meantime I have set up custom items using the process name/WFP only, which seem to work well without adding any system routes. I suppose this might break RTT tracking but otherwise I am pretty happy with the results, it was just unexpected to me that the preconfigured items will say “WFP mode supported” but then add those routes anyway.
Yes. 153.254.80.81 IP should go through Mudfish because the game item of mudfish includes 153.254.80.0/24 routing table in the game item when WFP item mode is enabled.
As mentioned at the above comment, it’s for calculating the realtime ping via ICMP because WFP (Windows Filtering Platform) driver doesn’t support ICMP.
And in my opinion, the custom item will be best fit for your needs.