Kismet: "no networks seen"

[codename1]

Hi

The kismet said to me "no network seen". Not connected.

And when I use airodump - while scanning all the channel, or only to the particular one - didn't see anything, but in reality there are a bunch of AP around.

I try "wesside-ng", but not helped, it endless scan channels for AP.

So, if anoyone know where is the problem and how to solve it, please write it down.

Thank you

[Archangel-Amael]

Written down just for you, get your pen ready to copy.

You don't know what you are doing and have thus far refused to read and learn.
Instead you want us to guess what the problem is.
Well we don't read minds so if you want help you will need to be more specific after you do some research.

[Thorn]

So, if anoyone know where is the problem and how to solve it, please write it down.

The problem is your inability to clearly state what you have done, what you have observed, any attempted fixes, and/or any error messages. In short, the problem is YOU.

How To Ask Questions The Smart Way

[codename1]

Ok, I have not found a satisfactory answer anywhere.

From the beginning.

I put the card (external) in monitor mode.

Then I use "airodump-ng (int)" and I am getting no clients shown.

The CH number cycles and shows no Access points.

I hope that is enough precisely now.

[Thorn]

It's a step in the right direction.

First of all, are you literally typing "airodump-ng (int)" (as is indicated by your quote marks)? If so, that's you're problem. The "(int)" is the interface name argument. If so, this is a case of you needing to have a basic understanding of the Linux CLI and then RTFM.

Secondly, pertaining to kismet, you should be check to see if you're getting a sources error. This is probably the case, if you're doing something similar to using "(int)" for the interface name. Again, this is probably a case of you needing understand what you're doing in the CLI and then RTFM.

[gunrunr]

are you using kismet newcore as installed in bt4 final, if you start it it will prompt you for your wireless extension, such as wlan0, eth0 or whatever, you don't necessarily have to have it in mon mode because kismet attempts to do that on its own. DON'T forget if you are using a VM you need to have a USB wireless interface and it needs to be connected to the VM and not the host

[codename1]

Of course I'm not literally typing.

I don't use VM. When I start kismet, it says - started as root, something that is less secure for system, and mainly that is not connected, or "no networks seen".

[Thorn]

Of course I'm not literally typing.

This is starting to turn into another lesson in pulling teeth...

OK, so what exactly are you typing, and what exactly are the errors? If you cut and paste using the [code] function, those messages will help us determine your issues.

I don't use VM. When I start kismet, it says - started as root, something that is less secure for system, and mainly that is not connected, or "no networks seen".

Again, RTFM; here is the Kismet documentation. See: "4. Suidroot & Security"

[Barry]

This is starting to turn into another lesson in pulling teeth...

I feel a photochop brewing.....

[codename1]

brewing, photochop brewing







and this