Various problems with Mudfish

This has been happening for over two months.


First of all, launching Mudfish kills my internet connection for some time.
I have been tried all the solutions for errors like changing nodes, starting the program with -t and/or -o parameters, cheked my firewall, av, updates, drivers, etc…
My provider (Mobile TeleSystems Open Joint Stock Company) tells there is no problem on their end.

some logs:
[STDOUT]
[0.008995] [INFO] mudfish v5.4.3 (for x86_64)
[0.010993] [INFO] Timestamp: Tue May 4 22:19:29 2021

[0.011993] [INFO] Connection protocol: tcp
[0.012992] [INFO] Authenticating…
[0.631717] [INFO] Fetching the static nodes…
[2.961056] [INFO] Fetched 528 static nodes from the master.
[2.968051] [INFO] TAP-Win32 Driver GUID {CBFAB21C-27F9-4CAD-8168-FCD6B2A12ABD}
[2.968051] [INFO] TAP-Win32 Driver Version 9.9
[2.968051] [INFO] TAP-Win32 Driver MTU 1500
[2.969049] [INFO] Setting TAP-Win32 Adapter v9’s MTU to 1400
��.

[3.030498] [INFO] TAP-Win32 Driver TcpNoDelay diabled
[3.031501] [INFO] TAP-Win32 Driver TcpAckFrequency 1
[3.031501] [INFO] TAP-Win32 Driver TCPNoDelay 1
[3.039493] [INFO] Uses the macaddr for msk(4) (cached).
[3.086464] [INFO] Ready
[3.089461] [INFO] udp_relay: listening on 0.0.0.0:1 (fd 0)
[3.089461] [INFO] tcp_relay: listening on 0.0.0.0:1 (fd 0)
[3.094459] [INFO] Waiting until the client’s ready to handle the routing path list.
[3.180404] [INFO] Listening the management console at 127.0.0.1:52205
[6.072663] [INFO] DHCP request for 00:ff:cb:fa:b2:1c (Notebook) from interface
[6.115631] [INFO] Waiting until the client’s ready to handle the routing path list.
[6.125625] [INFO] DHCP discover for 00:ff:cb:fa:b2:1c (Notebook) from interface
[6.142614] [INFO] DHCP request for 00:ff:cb:fa:b2:1c (Notebook) from interface
[6.142614] [INFO] DHCP Client got IPv4 address now
[6.760496] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[6.761497] [INFO] TCP relay from the client (10.254.41.92:53731) to the backend ((null):(null)) failed.
[6.763492] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[6.764490] [INFO] TCP relay from the client (10.254.41.92:63211) to the backend ((null):(null)) failed.
[6.971760] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[6.972752] [INFO] TCP relay from the client (10.254.41.92:63211) to the backend ((null):(null)) failed.
[6.975850] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[6.975850] [INFO] TCP relay from the client (10.254.41.92:53803) to the backend ((null):(null)) failed.
[7.187981] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[7.187981] [INFO] TCP relay from the client (10.254.41.92:63211) to the backend ((null):(null)) failed.
[7.189916] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[7.189916] [INFO] TCP relay from the client (10.254.41.92:63333) to the backend ((null):(null)) failed.
[7.406055] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[7.406055] [INFO] TCP relay from the client (10.254.41.92:57865) to the backend ((null):(null)) failed.
[7.407058] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[7.407058] [INFO] TCP relay from the client (10.254.41.92:59767) to the backend ((null):(null)) failed.
[7.612098] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[7.612098] [INFO] TCP relay from the client (10.254.41.92:63357) to the backend ((null):(null)) failed.
[7.615102] [INFO] tcprelay: Failed to find SID for destination 192.168.8.1.
[7.616102] [INFO] TCP relay from the client (10.254.41.92:49628) to the backend ((null):(null)) failed.
[9.118281] [INFO] MFP 0 RouteAdd - 109.244.5.0 255.255.255.0 170 102 0 n -1
[9.119282] [INFO] Fetching new static node SID 170…
[10.021692] [INFO] re121: Associating with ip 46.101.236.104 port 10008
[10.022688] [INFO] MFP 0 RouteAdd - 124.150.157.0 255.255.255.0 170 102 0 n -1
[10.023689] [INFO] MFP 0 RouteAdd - 183.111.189.0 255.255.255.0 170 102 0 n -1
[10.023689] [INFO] MFP 0 RouteAdd - 195.82.50.0 255.255.255.0 170 102 0 n -1
[10.024688] [INFO] MFP 0 RouteAdd - 204.2.229.0 255.255.255.0 170 102 0 n -1
[10.026686] [INFO] MFP 562 FishInterfaceBind - 170
[10.026686] [INFO] MFP 564 FishInterfaceBind - 170
[10.027686] [INFO] MFP 566 FishInterfaceBind - 170
[10.027686] [INFO] MFP 568 FishInterfaceBind - 170
[10.027686] [INFO] MFP 570 FishInterfaceBind - 170
[10.027686] [INFO] MFP 572 FishInterfaceBind - 170
[10.027686] [INFO] MFP 0 FlowMTU - 14.63.214.216 1500
[10.117320] [INFO] re121: Connected to 46.101.236.104:10008 (TCP)
[STDERR]
Empty file.

@dmitrykotov93 First sorry for this inconvenience. For these errors, please check Error Code Reference. It looks most of issues are happening between your desktop and mudfish nodes.

And at the second screenshot, it shows packet losses to many mudfish nodes. It means it’s happening between your desktop and mudfish node.

Please try to test your network status from your desktop to 46.101.228.155 (DE Europe (Germany - DigitalOcean)) using How to use WinMTR link.

I think this result shows you where this issue is from.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.