Upload page content

You can upload content for the page named below. If you change the page name, you can also upload content for another page. If the page name is empty, we derive the page name from the file name.

File to load page content from
Page name
Comment

Revision 1 as of 2019-12-27 04:23:18

Connecting Mudfish in China

As of December 23, 2019, Mudfish program does not work properly in China because GWF blocks public IPs and domains of Mudfish. This article will explain how to bypass this issue. You will need to check the following requirements.

Step 1: Bypass DNS poisoning

If you downloaded the Mudfish v5 version from https://mudfish.net/releases/, you'll need to bypass DNS poisoning first. This is because the Great Wall Firewall blocked domains such as mudfish.net and api.mudfish.net.

  • Install Machine DNS Client and change your computer's DNS address or use another DNS poisoning bypass method.

Currently, due to GWF block it returns a wrong IP when it resolves the mudfish domains in China. Normally mudfish IP addresses start with 14.64.X.Y.

C: \ Users \ mudfish> nslookup api.mudfish.net
Server: 2.56.168.192.in-addr.arpa
Address: 192.168.0.2
Name: api.mudfish.net.localdomain
Addresses: 31.13.73.23
          31.13.73.23
C: \ Users \ mudfish> ping api.mudfish.net
Ping api.mudfish.net [31.13.73.23] uses 32 byte data:
Control-c

31.13.73.23 is Facebook's IP, which means that GWF sends an incorrect IP in DNS response, and that IP is also blocked in GWF.

Step 2: Using Mudfish v5.0.9 or Later

First check the "Checklist" below to make sure your loach is ready to run.

Check Points

Make sure the following items are set correctly.

  • Have you checked whether the SMHNR feature is properly turned off?
  • Did you flush the DNS cache?

Running Mudfish

Please try running Mudfish v5.0.9 or higher. This version contains some code to bypass the issue.

Known Issues

I'm getting MUDEC_00016 or MUDEC_00320 errors.

In that case, please try again after exiting the program completely.

' 'Give up to wait the snode backed for SID XXX error keeps coming up.

The error seems to simply be ignored for now. The issue will be resolved in the next version.