Monitor Mode doesn't work in Kali 2.0
up vote
1
down vote
favorite
For the last year or so I have been using this exact setup with Kali 1.0. Everything worked fine with Wireshark. Now, when I am connected to a Wi-Fi access point my card REFUSES to stay in monitor mode. I have tried the following.
Scenario 1:
- Live boot Kali 2.0
- Open terminal
- $airmon-ng start wlan1 (a USB wireless adapter I have used for sniffing in the past)
- output is now wlan1mon (I understand why it outputs this I read the Kali docs)
- Connect to my home network
- Open Wireshark and listen to wlan1mon
- I only see Broadcast ARP requests and traffic from my machine
Scenario 2:
- Live boot Kali 2.0
- Open terminal
- ifconfig wlan1 down
- iwconfig wlan1 mode monitor
- ifconfig wlan1 up
- Connect to my home network
- Open wireshark and listen to wlan1
- I only see Broadcast ARP requests and traffic from my machine
I'm not sure what it's problem is.
linux wireshark kali-linux
migrated from security.stackexchange.com Aug 30 '15 at 22:50
This question came from our site for information security professionals.
add a comment |
up vote
1
down vote
favorite
For the last year or so I have been using this exact setup with Kali 1.0. Everything worked fine with Wireshark. Now, when I am connected to a Wi-Fi access point my card REFUSES to stay in monitor mode. I have tried the following.
Scenario 1:
- Live boot Kali 2.0
- Open terminal
- $airmon-ng start wlan1 (a USB wireless adapter I have used for sniffing in the past)
- output is now wlan1mon (I understand why it outputs this I read the Kali docs)
- Connect to my home network
- Open Wireshark and listen to wlan1mon
- I only see Broadcast ARP requests and traffic from my machine
Scenario 2:
- Live boot Kali 2.0
- Open terminal
- ifconfig wlan1 down
- iwconfig wlan1 mode monitor
- ifconfig wlan1 up
- Connect to my home network
- Open wireshark and listen to wlan1
- I only see Broadcast ARP requests and traffic from my machine
I'm not sure what it's problem is.
linux wireshark kali-linux
migrated from security.stackexchange.com Aug 30 '15 at 22:50
This question came from our site for information security professionals.
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
For the last year or so I have been using this exact setup with Kali 1.0. Everything worked fine with Wireshark. Now, when I am connected to a Wi-Fi access point my card REFUSES to stay in monitor mode. I have tried the following.
Scenario 1:
- Live boot Kali 2.0
- Open terminal
- $airmon-ng start wlan1 (a USB wireless adapter I have used for sniffing in the past)
- output is now wlan1mon (I understand why it outputs this I read the Kali docs)
- Connect to my home network
- Open Wireshark and listen to wlan1mon
- I only see Broadcast ARP requests and traffic from my machine
Scenario 2:
- Live boot Kali 2.0
- Open terminal
- ifconfig wlan1 down
- iwconfig wlan1 mode monitor
- ifconfig wlan1 up
- Connect to my home network
- Open wireshark and listen to wlan1
- I only see Broadcast ARP requests and traffic from my machine
I'm not sure what it's problem is.
linux wireshark kali-linux
For the last year or so I have been using this exact setup with Kali 1.0. Everything worked fine with Wireshark. Now, when I am connected to a Wi-Fi access point my card REFUSES to stay in monitor mode. I have tried the following.
Scenario 1:
- Live boot Kali 2.0
- Open terminal
- $airmon-ng start wlan1 (a USB wireless adapter I have used for sniffing in the past)
- output is now wlan1mon (I understand why it outputs this I read the Kali docs)
- Connect to my home network
- Open Wireshark and listen to wlan1mon
- I only see Broadcast ARP requests and traffic from my machine
Scenario 2:
- Live boot Kali 2.0
- Open terminal
- ifconfig wlan1 down
- iwconfig wlan1 mode monitor
- ifconfig wlan1 up
- Connect to my home network
- Open wireshark and listen to wlan1
- I only see Broadcast ARP requests and traffic from my machine
I'm not sure what it's problem is.
linux wireshark kali-linux
linux wireshark kali-linux
asked Aug 30 '15 at 21:42
Anthony Russell
1421311
1421311
migrated from security.stackexchange.com Aug 30 '15 at 22:50
This question came from our site for information security professionals.
migrated from security.stackexchange.com Aug 30 '15 at 22:50
This question came from our site for information security professionals.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
In scenario 1, after 4th point:
try these:
ifconfig wlan1mon down
iwconfig wlan1mon0 mode monitor
ifconfig wlan1mon up
Then to test and sniff the network:
airodump-ng wlan1mon
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
add a comment |
up vote
-1
down vote
after starting monitor the system it will suggest some process that may cause troubles...try killing them...and using monitor and connecting to a network may cause troubles...
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
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
In scenario 1, after 4th point:
try these:
ifconfig wlan1mon down
iwconfig wlan1mon0 mode monitor
ifconfig wlan1mon up
Then to test and sniff the network:
airodump-ng wlan1mon
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
add a comment |
up vote
0
down vote
In scenario 1, after 4th point:
try these:
ifconfig wlan1mon down
iwconfig wlan1mon0 mode monitor
ifconfig wlan1mon up
Then to test and sniff the network:
airodump-ng wlan1mon
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
add a comment |
up vote
0
down vote
up vote
0
down vote
In scenario 1, after 4th point:
try these:
ifconfig wlan1mon down
iwconfig wlan1mon0 mode monitor
ifconfig wlan1mon up
Then to test and sniff the network:
airodump-ng wlan1mon
In scenario 1, after 4th point:
try these:
ifconfig wlan1mon down
iwconfig wlan1mon0 mode monitor
ifconfig wlan1mon up
Then to test and sniff the network:
airodump-ng wlan1mon
answered Sep 6 '15 at 7:59
Yatin Mehandiratta
12416
12416
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
add a comment |
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
I will attempt this the next time I have that system booted. Have you tried this yet? It seems suspect that it would work. wlan1mon is the name of the interface not wlan1mon0. I think this will result in a interface not found error.
– Anthony Russell
Sep 6 '15 at 15:39
add a comment |
up vote
-1
down vote
after starting monitor the system it will suggest some process that may cause troubles...try killing them...and using monitor and connecting to a network may cause troubles...
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
add a comment |
up vote
-1
down vote
after starting monitor the system it will suggest some process that may cause troubles...try killing them...and using monitor and connecting to a network may cause troubles...
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
add a comment |
up vote
-1
down vote
up vote
-1
down vote
after starting monitor the system it will suggest some process that may cause troubles...try killing them...and using monitor and connecting to a network may cause troubles...
after starting monitor the system it will suggest some process that may cause troubles...try killing them...and using monitor and connecting to a network may cause troubles...
answered Aug 30 '15 at 22:26
EHY
315
315
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
add a comment |
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
There are no processes conflicting. Using monitor mode while connected to a network is the only way to see packets from other machines...
– Anthony Russell
Aug 30 '15 at 22:31
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
did u search if ur the only one having this problem?
– EHY
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
Ehhh yeah... Kali 2.0 released this month... Not a ton of documentation on fringe cases just yet... All I know is that I have been using the same tools AND process on Kali 1.0 and all was fine...
– Anthony Russell
Aug 30 '15 at 22:36
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
could be the programmers fault?
– EHY
Aug 30 '15 at 22:42
add a comment |
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%2fsuperuser.com%2fquestions%2f965023%2fmonitor-mode-doesnt-work-in-kali-2-0%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