Sorry for this inconvenience. According to mudfish logs, I can see some following logs:

[1293.111640] [ERROR] MUDEC_00031: TOL_connect(10.251.96.1, 8081) failed: 60 Operation timed out

It means that Mudfish client couldn't communicate with mudfish nodes properly. However are you under network firewall? It seems your connection sometimes blocked by network firewall or censorship.

I have my firewall turned on all the time and Mudfish previously allows me to connect just fine before without random disconnects.

And note that on my antivirus firewall I have allowed all the mudfish applications to run through it (Net Guard Off). So I think it's just your unstable nodes and not an error of my side unless I'm getting things wrong.

> And note that on my antivirus firewall I have allowed all the mudfish applications to run through it (Net Guard Off). So I think it's just your unstable nodes and not an error of my side unless I'm getting things wrong.

Nop. I didn't mean your personal firewall. I meant network firewall at ISP level. If you don't mind, please send me Problem Report to see more detailed status.

I submitted one and the error codes I have encountered was a lot of MUDEC_00031 and one time MUDEC_00059. My browser still works whenever I get dc'd out of game so yeah it might be something to do with my ISP not being friendly with mudfish but I have no idea how to resolve this from my side.

Kay another one just occurred what the hell. c'mon It was real fine previously, now the last several days I keep getting at least one disconnect per day it's so annoying.

> I submitted one and the error codes I have encountered was a lot of MUDEC_00031 and one time MUDEC_00059.

I answered to your problem report. :-) Thank you for this problem report. And 00031 and 00059 errors are very normal which kind of disconnection happens. And INFO level 000310 and 00059 errors aren't important at all because it doesn't affect your connection.

> My browser still works whenever I get dc'd out of game so yeah it might be something to do with my ISP not being friendly with mudfish but I have no idea how to resolve this from my side.

:-) You should understand this difference between long-alive connection and short-alive connection. Most of browser's connections are short-alive connection. So even if any kind of disconnection happens it doesn't affect your browsing because browser silently reconnect to the server.

However long-alive connection affected by this disconnection issue. It means one of NAT routers are reset or rebooted, definitely your connection are aborted.

> Kay another one just occurred what the hell. c'mon It was real fine previously, now the last several days I keep getting at least one disconnect per day it's so annoying.

As mentionted at your problem report's topic, this isn't mudfish issues, it's more related with your ISP level because your connection are wrapped by multiple NAT-ings.

Yeah thank you for the technicalities but nothing literally have changed in condition nor placement from my side in the past month unless it's some complicated IT stuff from my ISP which I have totally no control over so I reckon I have to just suck it up eh.

Yes. I agree with you. This is one out of control thing from you and mudfish. If you change your ISP to other vendor who provide a public IP to user, the story could be different. If not, yep it's out of our hands.