I don’t have /dev/net/tun nor do I run a DHCP client, is it possible to use mudfish?
If I add /dev/net/tun (to prevent the ODR_open_tuntapdev error) and connect via dhcpcd/wpa_supplicant on my wireless interface I’m still getting MUDEC_00044 followed by MUDEC_00045.
I think normally /dev/net/tun is created by systemd/udev, so if there is no systemd/udev it isn’t there and apps that need it should create it themselves.
I’m testing on two systems, both are normal Arch Linux, one without systemd/udev and one with, so on one without I have to create /dev/net/tun manually.
Then on both systems I’m getting MUDEC_00044/MUDEC_00045 (DHCP related) errors when trying with 1) static IP setup (to WiFi router, with wpa_supplicant), 2) dhcpcd/wpa_supplicant, 3) NetworkManager.
This is not true because /dev/net/tun is created by tun(4) kernel driver. So if you can’t see it under /dev/net directory, it means that your kernel doesn’t be built in tun(4) driver.
Please try to run mudfish binary manually if you’re familiar with the terminal. For example:
net-tools (for route) and dhclient packages (as evident from running mudfish directly, it was missing those) on both systems (on Arch net-tools is deprecated in favor of iproute2 and I had dhcpcd instead of dhclient).