Hell Let Loose traffic not going through mudfish

Technical Support
#1

Just installed mudfish today, attempting to test it to a North America East Hell Let Loose server 192.169.89.18.

I’ve tested Full VPN mode, WFP Mode, and Non-WFP mode - All traffic to 192.169.89.18 still goes across my default interface, without going through mudfish. I’ve verified this with wireshark, the default main interface still sees traffic 192.168.1.3 (internal) <-> 192.169.89.18 (HLL Miami)… This is very surprising in full vpn mode.

I thought it might have been something funky with ipv6, I’ve disabled my IPV6 drivers. I set the mudfish server to South Africa to get higher pings for testing. The server browser in HLL does show the expected high ping, but when I connect in game the ping goes to normal and I see traffic on the default interface in wireshark.

Windows 11 Pro for workstations, 22H2

I’ve uploaded a packet dump here, full VPN mode https://mudfish.net/forums/7/topics/83449 while running the game. At the time of this test only mudfish is running, no other VPNs or network programs are active. There is a install of speedify on the machine, but it is disabled.

Abridged route print output below

PS C:\WINDOWS\system32> route print  | more
=
Interface List
 25...00 15 5d fe 37 90 ......Hyper-V Virtual Ethernet Adapter
  5...00 ff 24 bc b7 21 ......Speedify Virtual Adapter
 17...00 ff c7 67 1e c0 ......TAP-Win32 Adapter V9
  1...........................Software Loopback Interface 1
  3...18 c0 4d a5 aa 91 ......Realtek Gaming 2.5GbE Family Controller
=
IPv4 Route Table
=
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1      192.168.1.3    351
          0.0.0.0          0.0.0.0     10.254.199.1   10.254.199.114     55
          0.0.0.0        128.0.0.0     10.254.199.1   10.254.199.114     56
    1.201.137.100  255.255.255.255      192.168.1.1      192.168.1.3    351
...
     10.254.199.0    255.255.255.0         On-link    10.254.199.114    311
   10.254.199.114  255.255.255.255         On-link    10.254.199.114    311
   10.254.199.255  255.255.255.255         On-link    10.254.199.114    311
...
      172.27.80.0    255.255.240.0         On-link       172.27.80.1    271
      172.27.80.1  255.255.255.255         On-link       172.27.80.1    271
    172.27.95.255  255.255.255.255         On-link       172.27.80.1    271
...
   192.73.235.191  255.255.255.255      192.168.1.1      192.168.1.3    351
    192.81.214.55  255.255.255.255      192.168.1.1      192.168.1.3    351
   192.138.210.36  255.255.255.255      192.168.1.1      192.168.1.3    351
      192.168.1.0    255.255.255.0         On-link       192.168.1.3    351
      192.168.1.3  255.255.255.255         On-link       192.168.1.3    351
    192.168.1.255  255.255.255.255         On-link       192.168.1.3    351
   192.184.90.194  255.255.255.255      192.168.1.1      192.168.1.3    351
   192.241.188.38  255.255.255.255      192.168.1.1      192.168.1.3    351
  192.241.195.105  255.255.255.255      192.168.1.1      192.168.1.3    351
...
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link    10.254.199.114    311
        224.0.0.0        240.0.0.0         On-link       192.168.1.3    351
        224.0.0.0        240.0.0.0         On-link       172.27.80.1    271
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link    10.254.199.114    311
  255.255.255.255  255.255.255.255         On-link       192.168.1.3    351
  255.255.255.255  255.255.255.255         On-link       172.27.80.1    271
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      192.168.1.1  Default
=
IPv6 Route Table
=
Active Routes:
 If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
 17    311 fe80::/64                On-link
 25    271 fe80::/64                On-link
 25    271 fe80::6a6f:4167:66d7:7eda/128
                                    On-link
 17    311 fe80::c039:31d2:467a:b35b/128
                                    On-link
  1    331 ff00::/8                 On-link
 17    311 ff00::/8                 On-link
 25    271 ff00::/8                 On-link
=
Persistent Routes:
  None
#2

Okay. In my opinion, this issue is not easy to solve because it looks like that the game client explicitly specify (bind) the network interface for the socket connection. If I know correctly, Windows supports Strong E/S(End System) for the routing selection. So if the game client specifies the network interface using bind() call, Mudfish can’t catch the packets.

And when I reviewed the output of ROUTE PRINT command, it looks fine for Full VPN mode settings.

However did you try to test with Full VPN mode + WFP Item mode combination?

#3

I’ve tested FULL VPN + WFP and HLL still bypasses mudfish.

I’ve also tested with Speedify, and Mullvad (wireguard) - And HLL does NOT bypass those networks.

I have a openwrt device I could put in front of the gaming computer, to connect with mudfish. I was hoping to take advantage of the multihop overlay routing to play on the miami servers, so I’m willing to put in some elbow grease.

#4

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.