Why can't I put the interface into monitor mode?

Viewed 20

I have a USB modem WL-167G V3. I want to switch to monitoring mode through airmon-ng, but it gives out that I need to kill the processes. The problem is that I want to leave the second interface connected to wifi, so you can't kill processes. But, even if I kill, the problem does not go away.

sudo airmon-ng start wlxf46d048b73f2

Found 2 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

    PID Name
    651 NetworkManager
    667 wpa_supplicant

PHY Interface   Driver      Chipset

phy0    wlo1        iwlwifi     Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30)
null    wlxf46d048b73f2 r8712u      ASUSTek Computer, Inc. WL-167G v3 802.11n Adapter [Realtek RTL8188SU]


┌─[dgdays@dgdays-parrot-notebook]─[~]
└──╼ $sudo airmon-ng start wlxf46d048b73f2


PHY Interface   Driver      Chipset

phy0    wlo1        iwlwifi     Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30)
null    wlxf46d048b73f2 r8712u      ASUSTek Computer, Inc. WL-167G v3 802.11n Adapter [Realtek RTL8188SU]

┌─[dgdays@dgdays-parrot-notebook]─[~]
└──╼ $ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether d8:f2:ca:c4:2e:99 brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
3: wlxf46d048b73f2: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether f4:6d:04:8b:73:f2 brd ff:ff:ff:ff:ff:ff
0 Answers
Related