Hey, I am trying to get mudfish to keep low ping to both Singapore and Sydney in order to reduce Overwatch queuetimes by giving me access to more than one server. I live in Perth and therefore with proper routing can get ~60 ms to both. If I could somehow fix this ping, I could try to simultaneously fix ping to other parts of the region too, giving me access to an even larger pool of players.
On my non-vpned routes I get decent ping to Sydney (60 ms), but terrible ping to Singapore (160 ms). If I use the Overwatch item, it does the reverse and basically gives me 160+ ping to Sydney and 60 ping to Singapore. My goal is to get good ping to both so I can queue in to games in both areas, as my queue time is currently massive.
My current approach is that I would go to the custom game browser, find an ip like 35.185.184.115, then make a custom item using what I could glean on your tutorial on CIDR notation, type 35.185.184.0/24 and then redirect the routes. I would then hunt for different overwatch singapore servers and repeat. The problem is that Blizzard continually shift around their ips, so while I might collect a large list of ips, the next week or so they shift it about, and suddenly my table becomes useless.
I notice however if I am to use the Overwatch Singapore item, I can always fix my ping to Singapore, so clearly there’s a notation to refer to the google hosted Singapore servers. I was wondering how I do this?
The goal eventually is to have a single custom item that fixes Perth to Singapore ping, doesn’t ruin Perth to Sydney ping, and maybe with luck fixes Perth to Korea ping and maybe fixes Perth to Taiwan ping as well.
Blizzard is constantly ruining routing to their servers recently, so if I was able to fix routing to as many servers as possible, then maybe I could fix queuetimes enough to make the game playable.
TLDR: What do I need to put in to a custom item to refer to an entire google overwatch server ip range like is shown in your fixed overwatch item?
As you might see, Overwatch item of mudfish uses a more wilder IP range using CIDR syntax. So I think it’s a reason why it works but more easier to encounter Amazon EC2, Twitch and Mudfish or CDN and Mudfish issue.
Yes, I noticed while using the overwatch item that google/youtube gets confused about my location which I guess is related to the issue you mentioned.
Forgive me, because my only understanding is from your help file, but I take it there’s no way to get the format of the ip/netmask format directly in to a custom item right, it only supports hostname, process and CIDR?
"ip": "34.64.0.0",
"netmask": "255.192.0.0"
So to get it working, I’d have to go through the list of Singapore ips (which I believe is the ips beginning with 34 and 35 above), and convert all those ips and netmasks into CIDR notation to give their IP ranges?
Edit:
So apparently subnet masks just relate directly to a CIDR suffix, which is nice I guess. So I just found an online calculator which helped me convert it. I am just going to try to use the below ranges.
For some reason though it now thinks that 24.105.0.0/18 is local for the matchmaker even though for some reason it’s in NA. However the ping of everything else is fixed.
I hope now everything goes well with mudfish. Please let me know if there are any other problems.