Username - liljaeger2k
Device: Samsung Galaxy S24 Ultra (One UI 8.5)
Game Title: eFootball Mobile
Summary of Issue:
I recently added credit to my Mudfish account specifically to optimize latency for eFootball Mobile. However, matchmaking fails completely whenever any Mudfish tunnel is active. The queue searches indefinitely and never pairs with an opponent. The moment Mudfish is disconnected, the game finds matches instantly on the raw ISP network.
I am writing to see if your team can inspect this behavior, identify if specific server IP ranges or STUN/signaling ports are being dropped, or provide an updated routing configuration to resolve this.
Troubleshooting Steps Already Completed:
Modes Tested: Both dedicated Game Item mode and Full VPN Mode.
Nodes & Providers Tested: All available regional nodes in India (Mumbai, Delhi) and Singapore across various providers (AWS, Google Cloud, Linode, and smaller hostings).
Protocols & Ports: Tested both UDP and TCP modes across available default and alternate ports (including port 10008 and port 443).
MTU Adjustments: Adjusted MTU values systematically across the full range (tested 575, 1000, 1350, and 1500).
Routing Path Configurations: Tested Basic, Advanced, and Multi-path configurations.
In-Game Settings: Tested with matchmaking set to both “Search Nearby” and “Gradually Increase Search Area.”
Observed Behavior:
Because raw ISP connections match immediately while all Mudfish nodes hang indefinitely, it appears that either:
Konami’s mobile matchmaking coordinator is silently rejecting sessions originating from cloud/datacenter ASNs, or
Crucial UDP signaling/STUN packets required for peer handshake negotiation are being dropped or misrouted by the Android VPN tunnel layer.
Could you please advise if there is an updated routing item, custom IP table, or proxy configuration available that allows eFootball Mobile to properly negotiate matchmaking sessions?
Thank you for your time and assistance.
Sincerely,
Liljaeger2k