WLAN0 Starting in master mode when system boots up.

I’m facing the following problem when i boot my system with the network card being in master mode when the OS boots up, does anyone know how to fix this problem any help much appreciated.

I know how to take the card out of monitor mode it’s just a nuisance to need to do this every time especially when i forgot why my internet isn’t working.

Searched online can’t seem to find a solution.

┌─[sub8zero@parrot]─[~]
└──╼ $iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 Mode:Master Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

┌─[sub8zero@parrot]─[~]
└──╼ $systemctl restart network
Failed to restart network.service: Unit network.service not found.
┌─[✗]─[sub8zero@parrot]─[~]
└──╼ $SYSTEMCTL restart network
bash: SYSTEMCTL: command not found
┌─[✗]─[sub8zero@parrot]─[~]
└──╼ $systemctl
UNIT >
proc-sys-fs-binfmt_misc.automount >
sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backlig>
sys-devices-pci0000:00-0000:00:13.0-\x7b33AECD58\x2dB679\x2d4E54\x2d9BD9\x2dA>
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda->
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda->
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda->
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda.>
sys-devices-pci0000:00-0000:00:1c.2-0000:04:00.0-net-wlan0.device >
sys-devices-pci0000:00-0000:00:1f.3-sound-card0-controlC0.device >
sys-devices-pci0000:00-0000:00:1f.6-net-eth0.device >
sys-devices-platform-serial8250-tty-ttyS0.device >
sys-devices-platform-serial8250-tty-ttyS1.device >
sys-devices-platform-serial8250-tty-ttyS2.device >
sys-devices-platform-serial8250-tty-ttyS3.device >
sys-devices-platform-thinkpad_acpi-leds-tpacpi::kbd_backlight.device >
sys-devices-virtual-block-dm\x2d0.device >
sys-devices-virtual-block-dm\x2d1.device >
sys-devices-virtual-block-dm\x2d2.device >
sys-devices-virtual-misc-rfkill.device >
sys-module-configfs.device >
sys-module-fuse.device >
sys-subsystem-net-devices-eth0.device >
lines 1-23…skipping…
UNIT LOAD ACTIVE SUB >
proc-sys-fs-binfmt_misc.automount loaded active running >
sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backlight.device loaded active plugged >
sys-devices-pci0000:00-0000:00:13.0-\x7b33AECD58\x2dB679\x2d4E54\x2d9BD9\x2dA04D34F0C226\x7d-001F:8086:0001.0001-HID\x2dSENSOR\x2d200073.5.auto-iio:device0.device loaded active plugged >
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda1.device loaded active plugged >
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda2.device loaded active plugged >
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda5.device loaded active plugged >
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda.device loaded active plugged >
sys-devices-pci0000:00-0000:00:1c.2-0000:04:00.0-net-wlan0.device loaded active plugged >
sys-devices-pci0000:00-0000:00:1f.3-sound-card0-controlC0.device loaded active plugged >
sys-devices-pci0000:00-0000:00:1f.6-net-eth0.device loaded active plugged >
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged >
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged >
sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged >
sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged >
sys-devices-platform-thinkpad_acpi-leds-tpacpi::kbd_backlight.device loaded active plugged >
sys-devices-virtual-block-dm\x2d0.device loaded active plugged >
sys-devices-virtual-block-dm\x2d1.device loaded active plugged >
sys-devices-virtual-block-dm\x2d2.device loaded active plugged >
sys-devices-virtual-misc-rfkill.device loaded active plugged >
sys-module-configfs.device loaded active plugged >
sys-module-fuse.device loaded active plugged >
sys-subsystem-net-devices-eth0.device loaded active plugged >
sys-subsystem-net-devices-wlan0.device loaded active plugged >
-.mount loaded active mounted >
boot.mount loaded active mounted >
dev-hugepages.mount loaded active mounted >
dev-mqueue.mount loaded active mounted >
proc-sys-fs-binfmt_misc.mount loaded active mounted >
run-user-1000.mount loaded active mounted >
sys-fs-fuse-connections.mount loaded active mounted >
sys-kernel-config.mount loaded active mounted >
sys-kernel-debug.mount loaded active mounted >
sys-kernel-tracing.mount loaded active mounted >
systemd-ask-password-plymouth.path loaded active waiting >
systemd-ask-password-wall.path loaded active waiting >
init.scope loaded active running >
session-3.scope loaded active running >
accounts-daemon.service loaded active running >
alsa-restore.service loaded active exited >
apparmor.service loaded active exited >
arpwatch.service loaded active exited >
● beef-xss.service loaded failed failed >

[1]+ Stopped systemctl
┌─[✗]─[sub8zero@parrot]─[~]
└──╼ $system ctl start network manager
bash: system: command not found
┌─[✗]─[sub8zero@parrot]─[~]
└──╼ $systemctl start network manager
Failed to start network.service: Unit network.service not found.
Failed to start manager.service: Unit manager.service not found.
┌─[✗]─[sub8zero@parrot]─[~]
└──╼ $iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 Mode:Master Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

┌─[sub8zero@parrot]─[~]
└──╼ $sudo iwconfig wlan0 mode monitor
[sudo] password for sub8zero:
Error for wireless request “Set Mode” (8B06) :
SET failed on device wlan0 ; Device or resource busy.
┌─[✗]─[sub8zero@parrot]─[~]
└──╼ $iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

┌─[sub8zero@parrot]─[~]
└──╼ $

Are you having trouble with NetworkManager?

Master mode is for access points. Unless you started hostapd or a pentest tool for false access points, not sure where this is coming from.

Strange. Have you done anything access point related recently?

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