LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   "r8169" Realtek problem Kismet (https://www.linuxquestions.org/questions/linux-software-2/r8169-realtek-problem-kismet-720717/)

White Sun 04-21-2009 01:04 PM

"r8169" Realtek problem Kismet
 
I wanted to say Hello(!) to everybody on the forum as i'm new here.

I also have a problem:
Im running Ubuntu 8.10 and im trying to configure Kismet and I've been fixing the configuring files with my user and network card info and capturing interface (r8169 ,wlan0 ,Ws) with the last being my user. But when i run Kismet ("sudo Kismet") i get the error :

Launching kismet_server: //usr/bin/kismet_server
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
Enabling channel hopping.
Enabling channel splitting.
FATAL: Unknown capture source type 'r8169 ' in source 'r8169 ,wlan0 ,Ws'
Done.

As Kismet does not recognize my capture source (r8169) so I have to download new driver or something?
My network card is called: "RTL8101E/RTL8102E PCI Express Fast Ethernet controller"

I appreciate any help i can get, Thank you.

hurry_hui 04-22-2009 01:09 AM

First, I think you need to post output of:
Code:

lspci | grep -i network
Since you have not given us info about your wireless device. For kismet, we use network controller, not ethernet controller.

White Sun 04-22-2009 09:46 AM

Oh sorry,
Well this is the output I get from "lspci | grep -i network":
04:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100

hurry_hui 04-23-2009 03:24 AM

Ok. you need to edit your /etc/kismet.conf as follows:
Code:

suiduser=<your normal user, not root>
This suiduser setting might not work well in Ubuntu, just try.

You need to set source as follows:

Code:

source=iwlagn,wlan0,Intel
CMIIW.

White Sun 04-24-2009 02:02 AM

Hey, I get the same error when I change the code to "source= iwlagn, wlan0,Intel"
After I got the error I searched the internet for problems with iwlagn and it seems like some of them referred me to the driver iwl4965 instead, so i now tried to configure my file once again so it looks like: "source= iwl4965, wlan0, Intel".
When I then run "sudo kismet", It works!
Although... after playing around with it for a while (everything works perfectly, I get the packages sent and received and all that both from my own network and from my neighbours.

But then when i tried to access the internet, it dosen't work! I check my network status and it says im still connected to my wireless networik. I tried to close down kismet but it still wont work, and ive tried multiple internet programs all on different ports. I've also tried to restart my computer but to no use.

I guess i'll have to rewrite /etc/kismet.conf again so i dont get the right driver and then restart my computer but does anyone know why this happens?

hurry_hui 04-24-2009 10:56 AM

Kismet locks your wireless device in monitor mode (sometimes, it cannot revert it back for common use).

If you want to use wireless for other uses, you need to modprobe -r iwlagn / iwl4965 and then modprobe iwlagn / iwl4965 again. (You need to choose one, I don't know which one). This will reset your wireless to managed state.

Maybe you want to use two devices; one for monitoring, another for regular use.

CMIIW.

h2osmack 07-03-2009 11:34 AM

Just letting you know I have a wifi 5100 intel using the iwlagn driver.
I went into the kismet.conf file and changed the source to:

source=iwl4965,wlan0,wifiKis #instead of iwlagn,wlan,wifiKis

It ran straight away, even though i'm a bit confused that I don't have that driver installed.
In order to reconnect the Internet after your done using Kismet (in Ubuntu 9.04 at least), make sure the program is properly stopped first.
Then right click your network manager and disable wireless. Then re-enable it and voila, it should reconnect to your access point.


All times are GMT -5. The time now is 07:51 AM.