Hey Loxch! Just checking up if

Technical Support
1

Hey Loxch! Just checking up if the Advanced mode (2-node) settings are broken? Ever since I re-installed Windows 7 and upgraded to v4.4.5 of mudfish, my routes will only ever go through the first selected Node. FastConnect is off as well, so I don’t think that’s the issue.

How I confirmed it:
My ping to the game server through SG Asia (OneAsiaHost 2) is ~250.
My ping to the game server through SG Asia (OneAsiaHost2) > AU Oceania (Sydney - HostUS) should be ~450-500 or higher.
However, no matter what node I select as my second node, my in-game ping will always be 250 (as if only routed through the first node, oneasiahost2 singapore). My latency without mudfish is about 360.

Also, is it possible to update the IP of the Warmane Server Location? They host with OVH and their IP is: 79.137.41.100. It is located in Gravelines, France.

Thanks Loxch! Sorry for the wall of text, if you need me to provide any more info please let me know!

EDIT: Just some extra: Every two-node path that is detected and recommended by Mudfish gives me the wrong ping ingame. However every single-node path shows the correct latency in-game.

2

Hey again Loxch, here are my results!

When I use your testing method with “Whats My IP” site testing, it says it’s working and it indeed shows the right server. However, on WoW, it still doesn’t give me the correct latency (according to the routes). In my example below, I’m going from Home > MY Asia (Kuala Lumpur - Piradius) > DE Europe (Germany - IdealHosting) > Game Server.
Here are some screenshots explaining what I mean:

This is the best possible route that mudfish shows me: http://image.mudfish.net/i/j0I2IW

This is my latency according to mudfish:
http://image.mudfish.net/i/cG81DS

This is my actual latency in-game:
http://image.mudfish.net/i/qC2dUX

This is my latency on resource-monitor:
http://image.mudfish.net/i/K1siEL

Unfortunately, it is different to what Mudfish says it is. However, I believe mudfish is showing me the correct ping and that the issue is either the advanced chaining or the WoW France (Warmane) Item in general. This is why:

My ping to MY Asia (Kuala Lumpur - Piradius):
http://image.mudfish.net/i/uUa123

The ping from MY Asia (Kuala Lumpur - Piradius) to DE Europe (Germany - IdealHosting):
http://image.mudfish.net/i/aDTMWD

The ping from DE Europe (Germany - IdealHosting) to the Game Server:
http://image.mudfish.net/i/WZp9HQ

The total should be 59+162+3 = 224 ping (Which is what mudfish says it is). The reason why I think the second node/advanced mode isn’t working is because this is the ping from MY Asia (Kuala Lumpur - Piradius) to the game server: http://image.mudfish.net/i/SEjkRh

That is 215+59 = 274 (which is what resource monitor + my ingame shows), which makes it seem like I’m only being routed through the first node, in MY Asia.

I hope this information helps, and I apologize once again for the wall of text! If I can format it any better, please let me know >~< I really love mudfish and ever since I’ve started using it, the game just feels so bad without it. I hope we can get to the root of the issue soon!

Thank you, Ryan.

3

:slight_smile: I think this issue is from the difference of RTT calculation because you’re testing to 79.137.41.100 IP but in a mudfish, for Europe (France - Warmane) destination, 37.187.171.135 IP is used. So testing to different network results in this.

However are there multiple game servers? Now I’d updated it to 79.137.41.100 based. I think now the result would be more closer to your RTT.

4

Thanks Loxch! I see… that makes a lot of sense! Warmane hosts 7 servers. However, their most popular one (with 12000 players) is the one I play on - Icecrown. It uses the IP 79.137.41.100. However, apparently 37.187.171.135 is also a server/IP hosted by OVH in France, Paris (Same as 79.137.41.100), so I think routes are the same.

Thank you for updating it! I’ll give it a shot and I’ll make sure to report back when I’m done.

EDIT 3: Alright nevermind, Auto path update/RTT Finder is working again, but the “Realtime RTT” box still shows 3000 constantly. Unfortunately this didn’t fix it for me and the latency is still as if I’m being only routed through the first node… I think I have more proof here:

This is the tracert of routing through two nodes (shown at the top):
http://image.mudfish.net/i/txGEYH

This is the tracert of routing through only the first node (shown at the top):
http://image.mudfish.net/i/CoQuXo

As you can see, both tracerts are the same… even though the first picture should have me routed through two nodes and according to mudfish, have only 226 ms latency.

If there is nothing wrong that you can find on your end, do you think it’s something on my end? Like maybe because I’m on Windows 7?

Thank you and sorry again for all the trouble.

5

Why does mudfish now randomly spike/show me 3000 ping and I get dc’d
from the game? Is it one of the settings or issues on my end again?
< Thanks!

In mudfish, 3000 ms means the packet loss. So it means that your connection between your desktop and mudfish node you’d picked isn’t stable. Please try to change a mudfish node to another. And please check http://ko.loxch.com/userrtt/?uid=108872 link too for your RTT information. If you can see high RTT stddev values to all mudfish nodes, it indicates that your ISP has an issue.