airmon-ng start wlan0 problems
up vote
0
down vote
favorite
I was trying to aircrack-ng, but the problem everytime I
airmon-ng start wlan0
prism0 shows up not mon0. What to do?
root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipset
phy0 wlan0 wl Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
(experimental wl monitor mode vif enabled for [phy0]wlan0 on [phy0]prism0)
kali-linux
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
asked Aug 16 '16 at 6:54
cedrick
11
add a comment |
up vote
0
down vote
favorite
I was trying to aircrack-ng, but the problem everytime I
airmon-ng start wlan0
prism0 shows up not mon0. What to do?
root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipset
phy0 wlan0 wl Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
(experimental wl monitor mode vif enabled for [phy0]wlan0 on [phy0]prism0)
kali-linux
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
asked Aug 16 '16 at 6:54
cedrick
11
Reposting the same thing ( unix.stackexchange.com/questions/303615/… ) won't bring you any positive attention and both questions will probably get closed for lack of details anyways. Focus on improving the question instead of repeating it.
– Julie Pelletier
Aug 16 '16 at 7:04
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was trying to aircrack-ng, but the problem everytime I
airmon-ng start wlan0
prism0 shows up not mon0. What to do?
root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipset
phy0 wlan0 wl Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
(experimental wl monitor mode vif enabled for [phy0]wlan0 on [phy0]prism0)
kali-linux
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
asked Aug 16 '16 at 6:54
cedrick
11
I was trying to aircrack-ng, but the problem everytime I
airmon-ng start wlan0
prism0 shows up not mon0. What to do?
root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipset
phy0 wlan0 wl Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
(experimental wl monitor mode vif enabled for [phy0]wlan0 on [phy0]prism0)
kali-linux
kali-linux
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
asked Aug 16 '16 at 6:54
cedrick
11
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
asked Aug 16 '16 at 6:54
cedrick
11
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
edited Aug 26 '16 at 3:27
HalosGhost
3,66592135
3,66592135
asked Aug 16 '16 at 6:54
cedrick
11
asked Aug 16 '16 at 6:54
cedrick
11
asked Aug 16 '16 at 6:54
cedrick
11
11
Reposting the same thing ( unix.stackexchange.com/questions/303615/… ) won't bring you any positive attention and both questions will probably get closed for lack of details anyways. Focus on improving the question instead of repeating it.
– Julie Pelletier
Aug 16 '16 at 7:04
add a comment |
Reposting the same thing ( unix.stackexchange.com/questions/303615/… ) won't bring you any positive attention and both questions will probably get closed for lack of details anyways. Focus on improving the question instead of repeating it.
– Julie Pelletier
Aug 16 '16 at 7:04
Reposting the same thing ( unix.stackexchange.com/questions/303615/… ) won't bring you any positive attention and both questions will probably get closed for lack of details anyways. Focus on improving the question instead of repeating it.
– Julie Pelletier
Aug 16 '16 at 7:04
Reposting the same thing ( unix.stackexchange.com/questions/303615/… ) won't bring you any positive attention and both questions will probably get closed for lack of details anyways. Focus on improving the question instead of repeating it.
– Julie Pelletier
Aug 16 '16 at 7:04
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
As long as wlan0 is put into monitor mode, it is working fine. It could be called wlan0mon or mon0 or prism0 as it is called here, just like how a Wi-Fi card could be called wlan0 or ath0, or almost anything else. Either I don't understand what you are asking or you don't have a problem. Just remember to use prism0 in future commands like airodump-ng.
answered Aug 23 '16 at 2:16
TGrossb
163
add a comment |
up vote
0
down vote
Overview
Although you can use airmon-ng to put an interface into monitor mode, you can also do it using iwconfig. Make sure you have root privilages!
Put wlan0 into monitor mode:
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
Kill process that could interfere:
airmon-ng check kill
Now you can run an airodump-ng scan with the interface into monitor mode by running the command airodump-ng wlan0
Put interface back into managed mode when finished:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
service network-manager restart
answered Jul 11 '17 at 23:29
iamr00t
6913
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As long as wlan0 is put into monitor mode, it is working fine. It could be called wlan0mon or mon0 or prism0 as it is called here, just like how a Wi-Fi card could be called wlan0 or ath0, or almost anything else. Either I don't understand what you are asking or you don't have a problem. Just remember to use prism0 in future commands like airodump-ng.
answered Aug 23 '16 at 2:16
TGrossb
163
add a comment |
up vote
0
down vote
As long as wlan0 is put into monitor mode, it is working fine. It could be called wlan0mon or mon0 or prism0 as it is called here, just like how a Wi-Fi card could be called wlan0 or ath0, or almost anything else. Either I don't understand what you are asking or you don't have a problem. Just remember to use prism0 in future commands like airodump-ng.
answered Aug 23 '16 at 2:16
TGrossb
163
add a comment |
up vote
0
down vote
up vote
0
down vote
As long as wlan0 is put into monitor mode, it is working fine. It could be called wlan0mon or mon0 or prism0 as it is called here, just like how a Wi-Fi card could be called wlan0 or ath0, or almost anything else. Either I don't understand what you are asking or you don't have a problem. Just remember to use prism0 in future commands like airodump-ng.
answered Aug 23 '16 at 2:16
TGrossb
163
As long as wlan0 is put into monitor mode, it is working fine. It could be called wlan0mon or mon0 or prism0 as it is called here, just like how a Wi-Fi card could be called wlan0 or ath0, or almost anything else. Either I don't understand what you are asking or you don't have a problem. Just remember to use prism0 in future commands like airodump-ng.
answered Aug 23 '16 at 2:16
TGrossb
163
answered Aug 23 '16 at 2:16
TGrossb
163
answered Aug 23 '16 at 2:16
TGrossb
163
answered Aug 23 '16 at 2:16
TGrossb
163
163
add a comment |
add a comment |
up vote
0
down vote
Overview
Although you can use airmon-ng to put an interface into monitor mode, you can also do it using iwconfig. Make sure you have root privilages!
Put wlan0 into monitor mode:
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
Kill process that could interfere:
airmon-ng check kill
Now you can run an airodump-ng scan with the interface into monitor mode by running the command airodump-ng wlan0
Put interface back into managed mode when finished:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
service network-manager restart
answered Jul 11 '17 at 23:29
iamr00t
6913
add a comment |
up vote
0
down vote
Overview
Although you can use airmon-ng to put an interface into monitor mode, you can also do it using iwconfig. Make sure you have root privilages!
Put wlan0 into monitor mode:
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
Kill process that could interfere:
airmon-ng check kill
Now you can run an airodump-ng scan with the interface into monitor mode by running the command airodump-ng wlan0
Put interface back into managed mode when finished:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
service network-manager restart
answered Jul 11 '17 at 23:29
iamr00t
6913
add a comment |
up vote
0
down vote
up vote
0
down vote
Overview
Although you can use airmon-ng to put an interface into monitor mode, you can also do it using iwconfig. Make sure you have root privilages!
Put wlan0 into monitor mode:
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
Kill process that could interfere:
airmon-ng check kill
Now you can run an airodump-ng scan with the interface into monitor mode by running the command airodump-ng wlan0
Put interface back into managed mode when finished:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
service network-manager restart
answered Jul 11 '17 at 23:29
iamr00t
6913
Overview
Although you can use airmon-ng to put an interface into monitor mode, you can also do it using iwconfig. Make sure you have root privilages!
Put wlan0 into monitor mode:
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
Kill process that could interfere:
airmon-ng check kill
Now you can run an airodump-ng scan with the interface into monitor mode by running the command airodump-ng wlan0
Put interface back into managed mode when finished:
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up
service network-manager restart
answered Jul 11 '17 at 23:29
iamr00t
6913
answered Jul 11 '17 at 23:29
iamr00t
6913
answered Jul 11 '17 at 23:29
iamr00t
6913
answered Jul 11 '17 at 23:29
iamr00t
6913
6913
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f303651%2fairmon-ng-start-wlan0-problems%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
Reposting the same thing ( unix.stackexchange.com/questions/303615/… ) won't bring you any positive attention and both questions will probably get closed for lack of details anyways. Focus on improving the question instead of repeating it.
– Julie Pelletier
Aug 16 '16 at 7:04