MDK4 not installing to proper directory on Pineapple enterprise

[DrSKiZZ]

The pineapple MDK4 module installs correctly with its dependancies but when you perform an attack you get an '[Errno 2] No such file or directory: 'mdk4'' no matter the atack you run.

[urmel1960]

After installing the module, the necessary dependencies are installed. The module itself contains only the GUI. The program mdk4 is needed - this is installed as dependency after the module is installed.

Unfortunately the package (ipk) in the enterprise repository of HAK5 is broken - it does not contain the executable program.

opkg itself accepts this without error message and reports mdk4 as installed, although in fact the binary is missing.

You can easily check this by downloading the package and looking inside.
opkg update
opkg install mdk4 --download-only

Now you just have to find someone who can compile mdk4 for the wifi pineapple enterprise architecture ...

I have already submitted a ticket to HAK5 - they obviously don't want to deal with the issue there. So much for the "enterprise" product ....

[bad-antics]

The MDK4 module expects the binary at a specific path but opkg installs it elsewhere on the Pineapple Enterprise/MK7.

Quick fix — create a symlink:

ssh root@172.16.42.1

# Find where mdk4 was actually installed
which mdk4 || find / -name "mdk4" 2>/dev/null

# Common locations:
# /usr/sbin/mdk4 or /sd/usr/sbin/mdk4

# Create symlink to where the module expects it
ln -sf $(which mdk4 || echo /usr/sbin/mdk4) /usr/bin/mdk4

If mdk4 isn't installed at all:

opkg update
opkg install mdk4

# If storage is full, install to SD:
opkg install -d sd mdk4
ln -sf /sd/usr/sbin/mdk4 /usr/bin/mdk4

Root cause: The module's Python backend likely calls subprocess.run(['mdk4', ...]) which relies on PATH, but the error message [Errno 2] No such file or directory: 'mdk4' indicates it's doing a direct path lookup. The symlink fixes both cases.

If neither works, you can edit the module source directly:

# Find the module source
find /pineapple -name "*.py" | xargs grep -l "mdk4"
# Then update the binary path in the source

[noshitsecurity]

This has been resolved.

https://forums.hak5.org/topic/53112-module-mdk4/#findComment-373891