Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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"
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?
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.