It seems like it only connects to Battle.net over the VPN, and directly connects to D3 game servers. This seems to be a configuration error with mudfish :(

It means that some of IPv4 addresses are missing on game item. To address this problem, I need your help to update the game item. If you don't mind, you can send me a packet dump with referring Packet Capture with Mudfish link. Or you can use TCPView (https://technet.microsoft.com/en-us/sysinternals/tcpview.aspx) to know IP address information used by diablo3.exe process.

Sorry I was not able to figure out how to make a packet dump. I used TCPview and saw that Diablo iii.exe was connecting to 24.105.17.167 via my normal connection. I restarted the game several times and I also connected to 24.105.16.53 and 24.105.17.43, so it appears to be several IPs in the 24.105.16.x and 24.105.17.x range. I am not sure if you need anything else

After using TCPview I am also curious why mudfish has so many open connections to so many IP addresses? I am wondering how secure my data is...

Okay I'd updated the game item so please retest with it.

Regarding to your questions, here are my answers:

* When mudfish booted up on your desktop, it associates the connection with all mudfish nodes (might be around 100 TCP or UDP connections) to reduce the configuration setup time (e.g. changing the mudfish node to another or setting server-chain modes) When very first time Mudfish was implemented, there are very few number of mudfish nodes so it was not a problem. However nowadays I agree that it becomes larger and larger and at some points I need to re-design the internal of mudfish cores.

* Regarding to security, please be aware that Mudfish *doesn't* encrypt your data at all to minimalize the crypto latency. It means that mudfish depends on your application-level encryption (e.g. end-to-end method such as SSL or SSH). So your game client or site uses the encrytion at application level, your data must be safe from end to end. However your game or application doesn't encrypt the data I couldn't gurantee its safety.

Thank you, it appears to be fixed and working well now

Good to hear. :-) If your issue happens again, please let me know.