I have been using Mudfish to route Dead by Daylight match server traffic to ap-southeast-1 using CIDR ranges, but due to an AWS change, it seems that this is no longer possible.
Previously, identifying the IP ranges was straightforward:
- Pull https://ip-ranges.amazonaws.com/ip-ranges.json
- Filter by ap-southeast-1
- Item > Setup > Modify > Routing Path > Modify.
However, the majority of match servers now listen on IPs in 54.115.0.0/16 from a “region”: “GLOBAL” CIDR range regardless of physical region.
Routing by Process is also not a viable option for two reasons:
- Dead by Daylight game startup is incredibly slow if routed through a remote region.
- Dead by Daylight will delete all purchased in-game currency if ever started while routed through Japan (which is my fastest option for routing to ap-southeast-1). See https://www.reddit.com/r/deadbydaylight/comments/1wrzgdg/dont_login_with_vpns/
One final constraint is that I do not want to route my native region traffic (us-east-1) through Mudfish since there are no benefits to doing so.
I know that match server traffic happens on UDP 7777-7820. One possible workaround would be to direct Mudfish to route only that match server traffic through the VPN. This would avoid the startup problems. However, there appears to be no way to configure Mudfish to route by destination port as of Mudfish version 6.5.5.
Alternatively, if there were a way to connect to the Mudfish network via Wireguard or OpenVPN with pay-per-traffic, I could handle all of the routing in my UniFi router.
Unfortunately, I will have to stop using Mudfish until a solution is found. Are there any options that I overlooked?