Hi there, I am on cachyOS. I have managed to sucessfully (as far as I am aware) install mudfish version 6.6.0. To start the server I either start the program through the taskbar → Mudfish → use my admin password, or I have to run sudo /opt/mufdish/6.6.0/bin/mudrun. If using the second option I get a few warnings, but the service starts and I can access it on 127.0.0.1:8282. These are the warnings:
(mudrun:19833): libayatana-appindicator-WARNING **: 20:44:32.623: libayatana-appindicator is deprecated. Please use
libayatana-appindicator-glib in newly written code.
(mudrun:19833): libayatana-appindicator-WARNING **: 20:44:32.627: Unable to get the session bus: Error spawning comm
and line “dbus-launch --autolaunch=ab2eb6f1b467455bb89b57d7374420e4 --binary-syntax --close-stderr”: Child process e
xited with code 1
(mudrun:19833): LIBDBUSMENU-GLIB-WARNING **: 20:44:32.627: Unable to get session bus: Error spawning command line “d
bus-launch --autolaunch=ab2eb6f1b467455bb89b57d7374420e4 --binary-syntax --close-stderr”: Child process exited with
code 1
AFter logging in with my mudfish account, I click on the big green Connect button. Mudfish loads up until 52% on the self-configuration, but the throw 2 errors:
Tue, 20 Oct 2026 23:45:19 GMT [34.850760] MUDEC_00044: The client isn’t ready yet
and
Tue, 20 Oct 2026 23:45:49 GMT [64.851538] MUDEC_00045: The client doesn’t response with DHCP protocol
And then that is it, no further luck getting it to work. What I realise is that running “ip address show” the interface created by mudfish is there, but it is DOWN:
Tue, 20 Oct 2026 23:45:49 GMT [64.851538] MUDEC_00045: The client doesn’t response with DHCP protocol
So I don´t know if its some conflict of mudfsih not being able to handle my OS network interfaces or what, any help would be appreciated
Hi! These errors mean TAP DHCP setup isn’t completing. Mudfish uses NetworkManager when nmcli is installed.
While stuck, run nmcli device status and sudo nmcli con up mudfish-tap. If TAP shows unmanaged, run sudo nmcli device set tap0 managed yes (replace tap0 with its actual name), then retry the connection command.
If it still fails, please send the command errors and a Problem Report: set Setup → Program → Launcher → debugging level to TRACE, reproduce, then use Support → Problem Report.
I got it to work, the problem was 2 part solution:
I had a configuration file making the tap0 interface non-manageable, and because of that I think I wasnt being able to run sudo nmcli device set tap0 managed yes . After deleting the file and rebooting networkmanager I got the interface up and running with your guidance!
My main goal was to play wow:forever beta, and I thought I would need to add a custom game and use the process capture to capture it P:wowB but turns out the regular item pre-configured to WoW (the released version/.retail) was working to capture the beta aswell, even though they are different processes. I am guessing it caputres the destination address to check if packets should be coordinated by Mudfish.
Anyway ty for your help! On a quick question, how much usages should I expect to have using Mudfish only to play WoW (if you have an idea)
Glad it’s working, and thank you for your purchase! I don’t have a reliable WoW beta MB/hour estimate; usage varies with activity.
For your own estimate, note your credit balance, play WoW for one hour, then exit Mudfish and wait up to 2 hours before comparing. Multiply that deduction by your monthly play hours.
Billing is based on traffic, not time; both incoming and outgoing traffic at the node count. Keep Full VPN off and exit Mudfish during patches/downloads.