• Diff for "Amazon EC2, Twitch and Mudfish"
Last updated at 2024-05-01 01:53:04
Differences between revisions 1 and 2
Revision 1 as of 2017-07-17 02:47:11
Size: 1707
Editor: loxch
Comment:
Revision 2 as of 2017-07-17 02:47:19
Size: 1706
Editor: loxch
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Amazon EC2, Twitch and Mudfish =  = Amazon EC2, Twitch and Mudfish =

Amazon EC2, Twitch and Mudfish

Sometimes some users of mudfish report a problem regarding to mudfish traffics graph while watching Twitch because it consumes mudfish credit even if they are not using Full VPN mode.

When I checked and analyzed this issue deepyly, most of these cases are related with AWS (Amazon Web Services) because Twitch is owned by Amazon and operating on Amazon network.

Linking with Twitch

Some popular games are running on Amazone EC2 cloud to publish their games. So in a view of Mudfish, it's almost impossible to distinguish whether these traffics go to Twitch and the game server running on Amazon EC2 because Mudfish is implemented based on the routing table of OS.

Known problems

Due to above reason, sometimes mudfish credits could be consumed if you tried to download or do streaming while Mudfish is running even if you're not using Full VPN mode.

And without luck some, normal HTTP requests (no relations to the game) could go through mudfish nodes because the DNS server of CDN company responses with the same IP of cache servers.

Known items

The following game items have an issue:

  • Overwatch
  • Tree of Savior

How to avoid

  1. Because the mudfish works based on the OS's routing table rather than hooking OS's internal APIs, this issue could happen. If your game is working fine with Proxifier, I think you can check Mudfish with Proxifier.

  2. Or please stop to watch Twitch while you're playing the game with Mudfish.

Amazon EC2, Twitch and Mudfish (last edited 2024-05-01 01:53:04 by loxch)