Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Did anyone already figured out how to put the bcm4313 in monitor mode ?

First I tried the new brcm43xx open source driver. This driver is working and puts the 4313 in monitor mode, but monitor programs like kismet do not recieve any packets. No errors from kismet so I think this is driver related (still under development). The new driver does work with normal connections.

Second thing I tried was installing the b43 kernel driver. Using b43-fwcutter I installed the firmware, but when I modprobe b43 the driver gets loaded but I do not get an interface. Also dmesg and messages give no error related messages.

So I am looking for anyone who succesfully put the bcm4313 in monitor mode to use programs like kismet.

yes I did this back in 2004 read up on it we do not discus this type of subject in this forum. There has been many patches for this. But we do not discuss kismet in this format. if you Google are about ethical hacking then you will get close.

yes I did this back in 2004 read up on it we do not discus this type of subject in this forum. There has been many patches for this. But we do not discuss kismet in this format. if you Google are about ethical hacking then you will get close.

I am not discussing kismet here I am posting a question why the b43 driver does not detect my broadcom adapter when documentation tells me it should. Since this is the hardware forum I thought this would be the place to post such questions. And since I want to use monitor mode for legitimate purposes from a security point perspective, I don't understand what ethical hacking has to do with that.

I am not discussing kismet here I am posting a question why the b43 driver does not detect my broadcom adapter when documentation tells me it should. Since this is the hardware forum I thought this would be the place to post such questions. And since I want to use monitor mode for legitimate purposes from a security point perspective, I don't understand what ethical hacking has to do with that.

Hoping to see some usefull help.

That's not how you presented the original question. You stated 'kismet' and monitor mode.

Now you want to get the adapter functional. Which is it? We will not assist when it comes to kismet or other penetration methodology or potential monitor activities that can get information illegally or does involve potential illegal activities.

If you understood the reasoning or use for kismet then getting the adapter to work should be a cake walk.

Thanks for your more constructive response Gary. My question stated that I could not get my card into monitor mode so I could use programs "like" kismet or fyi any other use of the rfmon functionality from a wireless card. Article 10 of the european convention on human rights says that it is allowed to recieve ether signals. So nothing illegal about that.

Quote:

Now you want to get the adapter functional. Which is it?

I hoped my topic title and lspci contents were clear enough on the adapter specification

Quote:

You could do a LQ Search as the subject of getting a Broadcom chipset adapter working has been covered so many times.

No need to tell me this when I already wrote that the adapter is working in normal mode (with a closed source proprietary driver or a new open source driver that is still under development and unstable).

I did not see any restrictions in the rules section about posting on anything security related.

Anyway since people already make conclusions before asking I will try my luck elsewhere.

It did come across as such. As for your rights, we to have the right to state what was stated as your post(s) really didn't provide enough information. I'll be glad to assist as long as things are not to be done that will harm others.

Sniffing and getting others information that is private to begin with is not something I nor other LQ members get involved with because of the LQ Rules.

Again, do that search as Broadcom has been covered many times here on LQ. Sure, you presented material related to the Broadcom. But you did not define or explain things so we would have a clear picture. My money is on : You don't have the firmware in place since your kernel supports the chipset.

I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information in a manner that will aid us in diagnosis of the problem or query.

If that is needed I really want to provide additional information, but I can only respond on helpfull answers and not on people replying without helping. You suggest me to look at 'How to Ask Questions the Smart Way' I suggest you 'How to Read Questions the Smart Way' since you did not read that the chip I was talking about was the BCM 4313 which could be seen in the thread title and from the lspci output. If I didn't do a search I wouldn't post this question. There is only one topic on this chip that ends with the proprietary broadcom driver and my question was about the b43 or new brcm43xx driver.

I also wrote (maybe you missed it) that I used the firmware package installer and offcourse verified that it installed the firmware files in the right place. The chip is simply not detected and even if it was then various dmesg or other logs would show any error or other information about it and they simply don't. Do a google search on b43 and bcm 4313 and you will see a lot more people having trouble on the b43/bcm4313 combination. So my question was plain and simple if anyone succeeded to get this chip in rfom mode wich can only be done with b43 or brcm43xx.

So I really appreciate the help, but try to be constructive without judging someones intentions. Kismet or any other rfmon program can also be used for legit purposes to find out channel occupation, signal strength and interference from other stations. Wich I need for network testing purposes.

in order for me to answer your message I would be breaking policy. and yes that chip will go to rfom mode just like I taught my students and like any other simple Google will get you there. If time is a problem buy a different card. I already pointed you in the direction to look but you just could not read go back and read my first reply.
patch the kernel module and google.

in order for me to answer your message I would be breaking policy. and yes that chip will go to rfom mode just like I taught my students and like any other simple Google will get you there. If time is a problem buy a different card. I already pointed you in the direction to look but you just could not read go back and read my first reply.
patch the kernel module and google.

Your reply was that you did it back in 2004 on a chip that is produced around 2009/2010 so I don't see a reason to do a google search on that. Believe me I googled a lot on my problem...