Error enabling monitor mode using airmon-ngLinux access point (airmon-ng/airmon-ng) not workingHow to make...
How do I get my neighbour to stop disturbing with loud music?
Is there anything in the universe that cannot be compressed?
A word for the urge to do the opposite
Turn off Google Chrome's Notification for "Flash Player will no longer be supported after December 2020."
Is Borg adaptation only temporary?
Heavy Box Stacking
Necessity of tenure for lifetime academic research
How can I improve my formal definitions?
Could a simple hospital oxygen mask protect from aerosol poison?
Am I required to correct my opponent's assumptions about my morph creatures?
Given a specific computer system, is it possible to estimate the actual precise run time of a piece of Assembly code
Where should I draw the line on follow up questions from previous employer
My colleague treats me like he's my boss, yet we're on the same level
When you have to wait for a short time
German equivalent to "going down the rabbit hole"
Moscow SVO airport, how to avoid scam taxis without pre-booking?
In Toy Story, are toys the only inanimate objects that become alive? And if so, why?
Colored grid with coordinates on all sides?
Why do presidential pardons exist in a country having a clear separation of powers?
'spazieren' - walking in a silly and affected manner?
Properly unlinking hard links
Does using composite keys violate 2NF
Can authors email you PDFs of their textbook for free?
Can the inductive kick be discharged without a freewheeling diode, in this example?
Error enabling monitor mode using airmon-ng
Linux access point (airmon-ng/airmon-ng) not workingHow to make Linux use the right driver (lshw)Wifite Issue, “enabling monitor mode on phy3.”wifi keeps disconnecting when using aircrack/airmonairmon ng ls: cannot access '/sys/class/ieee80211/': No such file or directorySSID of hostapd is not visible
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
When I try to start monitor mode on my laptop, it just returns this:
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
549 avahi-daemon
614 avahi-daemon
790 wpa_supplicant
792 NetworkManager
1163 dhclient
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
So then I use the check kill command like it suggests
sudo airmmon-ng check kill
Killing these processes:
PID Name
790 wpa_supplicant
17141 avahi-daemon
17144 avahi-daemon
Then I will try and use the airmon-ng start wlp2s0 command.
sudo airmon-ng start wlp2s0
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
17176 avahi-daemon
17182 avahi-daemon
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
However, my card is still not put into monitor mode.
I've updated my OS using
sudo apt update
and
sudo apt upgrade
but it still refuses to enable monitor mode.
I have been able to start monitor mode before and haven't installed anything new or tried any other methods other than airmon-ng so I don't know what could have changed enough to cause these issues.
I've also never seen this before but I don't understand what it means and have a feeling that it's trying to tell me what the issue is:
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
I have a Samsung Q330 running Ubuntu 18.04
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
My network card in the laptop is
wlp2s0 IEEE 802.11 ESSID:"[REDACTED]"
Mode:Managed Frequency:2.432 GHz Access Point: AA:BB:CC:DD:EE:FF
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
prism0 no wireless extensions.
lo no wireless extensions.
enp6s0 no wireless extensions.
docker0 no wireless extensions.
EDIT
Sorry, I used the wrong command for my network card
Here's the actual card information using lshw -C network
*-network
description: Wireless interface
product: BCM4313 802.11bgn Wireless Network Adapter
vendor: Broadcom Inc. and subsidiaries
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 01
serial: e8:39:df:26:dd:c5
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) ip=172.20.8.105 latency=0 multicast=yes wireless=IEEE 802.11
resources: irq:16 memory:fc500000-fc503fff
*-network
description: Ethernet interface
product: 88E8040 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: enp6s0
version: 00
serial: 00:24:54:ac:a3:c1
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair
resources: irq:24 memory:fc600000-fc603fff ioport:4000(size=256)
*-network
description: Ethernet interface
physical id: 4
logical name: docker0
serial: 02:42:bc:20:12:22
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes
linux ubuntu airmon-ng aircrack-ng
New contributor
add a comment |
When I try to start monitor mode on my laptop, it just returns this:
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
549 avahi-daemon
614 avahi-daemon
790 wpa_supplicant
792 NetworkManager
1163 dhclient
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
So then I use the check kill command like it suggests
sudo airmmon-ng check kill
Killing these processes:
PID Name
790 wpa_supplicant
17141 avahi-daemon
17144 avahi-daemon
Then I will try and use the airmon-ng start wlp2s0 command.
sudo airmon-ng start wlp2s0
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
17176 avahi-daemon
17182 avahi-daemon
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
However, my card is still not put into monitor mode.
I've updated my OS using
sudo apt update
and
sudo apt upgrade
but it still refuses to enable monitor mode.
I have been able to start monitor mode before and haven't installed anything new or tried any other methods other than airmon-ng so I don't know what could have changed enough to cause these issues.
I've also never seen this before but I don't understand what it means and have a feeling that it's trying to tell me what the issue is:
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
I have a Samsung Q330 running Ubuntu 18.04
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
My network card in the laptop is
wlp2s0 IEEE 802.11 ESSID:"[REDACTED]"
Mode:Managed Frequency:2.432 GHz Access Point: AA:BB:CC:DD:EE:FF
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
prism0 no wireless extensions.
lo no wireless extensions.
enp6s0 no wireless extensions.
docker0 no wireless extensions.
EDIT
Sorry, I used the wrong command for my network card
Here's the actual card information using lshw -C network
*-network
description: Wireless interface
product: BCM4313 802.11bgn Wireless Network Adapter
vendor: Broadcom Inc. and subsidiaries
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 01
serial: e8:39:df:26:dd:c5
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) ip=172.20.8.105 latency=0 multicast=yes wireless=IEEE 802.11
resources: irq:16 memory:fc500000-fc503fff
*-network
description: Ethernet interface
product: 88E8040 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: enp6s0
version: 00
serial: 00:24:54:ac:a3:c1
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair
resources: irq:24 memory:fc600000-fc603fff ioport:4000(size=256)
*-network
description: Ethernet interface
physical id: 4
logical name: docker0
serial: 02:42:bc:20:12:22
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes
linux ubuntu airmon-ng aircrack-ng
New contributor
add a comment |
When I try to start monitor mode on my laptop, it just returns this:
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
549 avahi-daemon
614 avahi-daemon
790 wpa_supplicant
792 NetworkManager
1163 dhclient
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
So then I use the check kill command like it suggests
sudo airmmon-ng check kill
Killing these processes:
PID Name
790 wpa_supplicant
17141 avahi-daemon
17144 avahi-daemon
Then I will try and use the airmon-ng start wlp2s0 command.
sudo airmon-ng start wlp2s0
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
17176 avahi-daemon
17182 avahi-daemon
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
However, my card is still not put into monitor mode.
I've updated my OS using
sudo apt update
and
sudo apt upgrade
but it still refuses to enable monitor mode.
I have been able to start monitor mode before and haven't installed anything new or tried any other methods other than airmon-ng so I don't know what could have changed enough to cause these issues.
I've also never seen this before but I don't understand what it means and have a feeling that it's trying to tell me what the issue is:
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
I have a Samsung Q330 running Ubuntu 18.04
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
My network card in the laptop is
wlp2s0 IEEE 802.11 ESSID:"[REDACTED]"
Mode:Managed Frequency:2.432 GHz Access Point: AA:BB:CC:DD:EE:FF
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
prism0 no wireless extensions.
lo no wireless extensions.
enp6s0 no wireless extensions.
docker0 no wireless extensions.
EDIT
Sorry, I used the wrong command for my network card
Here's the actual card information using lshw -C network
*-network
description: Wireless interface
product: BCM4313 802.11bgn Wireless Network Adapter
vendor: Broadcom Inc. and subsidiaries
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 01
serial: e8:39:df:26:dd:c5
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) ip=172.20.8.105 latency=0 multicast=yes wireless=IEEE 802.11
resources: irq:16 memory:fc500000-fc503fff
*-network
description: Ethernet interface
product: 88E8040 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: enp6s0
version: 00
serial: 00:24:54:ac:a3:c1
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair
resources: irq:24 memory:fc600000-fc603fff ioport:4000(size=256)
*-network
description: Ethernet interface
physical id: 4
logical name: docker0
serial: 02:42:bc:20:12:22
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes
linux ubuntu airmon-ng aircrack-ng
New contributor
When I try to start monitor mode on my laptop, it just returns this:
Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
549 avahi-daemon
614 avahi-daemon
790 wpa_supplicant
792 NetworkManager
1163 dhclient
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
So then I use the check kill command like it suggests
sudo airmmon-ng check kill
Killing these processes:
PID Name
790 wpa_supplicant
17141 avahi-daemon
17144 avahi-daemon
Then I will try and use the airmon-ng start wlp2s0 command.
sudo airmon-ng start wlp2s0
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'
PID Name
17176 avahi-daemon
17182 avahi-daemon
PHY Interface Driver Chipset
phy0 wlp2s0 wl Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
However, my card is still not put into monitor mode.
I've updated my OS using
sudo apt update
and
sudo apt upgrade
but it still refuses to enable monitor mode.
I have been able to start monitor mode before and haven't installed anything new or tried any other methods other than airmon-ng so I don't know what could have changed enough to cause these issues.
I've also never seen this before but I don't understand what it means and have a feeling that it's trying to tell me what the issue is:
(experimental wl monitor mode vif already enabled for [phy0]wlp2s0 on [phy0]prism0)
I have a Samsung Q330 running Ubuntu 18.04
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
My network card in the laptop is
wlp2s0 IEEE 802.11 ESSID:"[REDACTED]"
Mode:Managed Frequency:2.432 GHz Access Point: AA:BB:CC:DD:EE:FF
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
prism0 no wireless extensions.
lo no wireless extensions.
enp6s0 no wireless extensions.
docker0 no wireless extensions.
EDIT
Sorry, I used the wrong command for my network card
Here's the actual card information using lshw -C network
*-network
description: Wireless interface
product: BCM4313 802.11bgn Wireless Network Adapter
vendor: Broadcom Inc. and subsidiaries
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 01
serial: e8:39:df:26:dd:c5
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) ip=172.20.8.105 latency=0 multicast=yes wireless=IEEE 802.11
resources: irq:16 memory:fc500000-fc503fff
*-network
description: Ethernet interface
product: 88E8040 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: enp6s0
version: 00
serial: 00:24:54:ac:a3:c1
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair
resources: irq:24 memory:fc600000-fc603fff ioport:4000(size=256)
*-network
description: Ethernet interface
physical id: 4
logical name: docker0
serial: 02:42:bc:20:12:22
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes
linux ubuntu airmon-ng aircrack-ng
linux ubuntu airmon-ng aircrack-ng
New contributor
New contributor
edited 1 hour ago
Skroppo
New contributor
asked 1 hour ago
SkroppoSkroppo
12 bronze badges
12 bronze badges
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Skroppo is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f538532%2ferror-enabling-monitor-mode-using-airmon-ng%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Skroppo is a new contributor. Be nice, and check out our Code of Conduct.
Skroppo is a new contributor. Be nice, and check out our Code of Conduct.
Skroppo is a new contributor. Be nice, and check out our Code of Conduct.
Skroppo is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f538532%2ferror-enabling-monitor-mode-using-airmon-ng%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown