I’d performed a Emergency Maintenance for current issues and monitoring mudfish nodes. However to prevent this service outage, it requires to do a patch to mudfish code daemon so it’ll happen soon. At this moment, all nodes should be fine.
Thank you.
@BloodStone OMG
@BloodStone Thank you and appreciate your comment. 
However any problems?
That error means that MTU (maximum transmission unit) between AU Oceania (Sydney - Amazon EC2) mudfish node and your desktop is small without IP fragmentation. To address this issue fundamentaly, you should fix your MTU value of TAP-Win32 adapter v9 network driver being lower. For workaround you can
* downgrade to v4.3.10 which is available at http://mudfish.net/releases/ link.
* upgrade to v4.3.13 which isn’t officially released yet. It’s also there at above link.
However with workaround, please note that mudfish is performing inefficient packet deliver to mudfish node.
Unless Full VPN mode is on, definitely not.
Thanks.
No problem. :-) If there are other questions, please let me know.
Thank you for this packet dump. When I looked into this packet file, it seems the game IP is already one of registered ranges. However did you try to specify a mudfish node for DirtyBorm game item instead of “Auto Selection” mode?