[myth]

Kismet, aircrack, airsnort and many other programs and techniques need your wireless card to jump into monitor mode.

glitch:/home/brad# iwpriv eth1
eth1      Available private ioctl :
          force_reset      (8BE0) : set   0       & get   0
          card_reset       (8BE1) : set   0       & get   0
          set_port3        (8BE2) : set   1 int   & get   0
          get_port3        (8BE3) : set   0       & get   1 int
          set_preamble     (8BE4) : set   1 int   & get   0
          get_preamble     (8BE5) : set   0       & get   1 int
          set_ibssport     (8BE6) : set   1 int   & get   0
          get_ibssport     (8BE7) : set   0       & get   1 int
[B]     monitor          (8BE8) : set   2 int   & get   0[/B]
          dump_recs        (8BFF) : set   0       & get   0

Thats what we want in the end, just a useful tool to check if ya cards good or not.

Ok, im a low budget man, no James Bond M tools and whatnot, so heres some tips i wouldve loved when trying to get my Toshiba Satellite Pro 6100 card, with an Intel (well, windows drivers said that) but all that matters is it uses the Orinoco Drivers.

Couple things ive notice, PrismII-type cards are usually wlan0. Also, when it comes to PrismII Chipsets, everyone knows you want them, but there are MANY types of Prism cards, and im not sure exactly the chipsets to models.

OK, under normal use. Ie, default install of Debian of the 2.6.8 kernel, the orinoco drivers supplied could not get my card into monitor mode, think of the same output on the about screen but without the bolded text.

Now, because i wasnt sure exactly what i needed, looking over the many google queries never quite answering my general questions, and its probably not a great idea to start loading modules into the kernel w/o knowing how to reverese everything you've done.

http://www.linuxques...ons/answers/398 <- Those instructions worked for me...

Also, quick tip, Whoppic and Auditor, my wireless card would not work with the default Whoppix (2.6 - 2.7 wasnt tested, but may work), however, it worked with Auditor. As soon as kismet loaded successfully, fix config (/etc/kismet/kismet.conf) with below, and the iwpriv command showed monitor mode, i realised you dont need some fancy hardware.

source=orinoco,eth1,wifi

Also, if ya got a lappy, check your wireless card, because mines a PCI module thingo, i've got two wires just under my keyboard for my wireless antenna, gonna mod that to change antennas.

Hopefully i was some help for the orinoco newbies.... More comments would be great.

[myth]

myth, on Jun 23 2005, 02:06 PM, said:

Hopefully i was some help for the orinoco newbies.... More comments would be great.

Rofl,

my own comments helped me get my card back up and running :)

[darkside720]

Ok, I understand the basis for the kismet, but has anyoen ever tried installing it on a vmware and running the kismet there? I have it installed on a DELL D620 and Linux on the virtual machine with the network in the virtual machine running off of eth0. However, when I configured the kismet.conf file for

source=Broadcom,eth0,wifi, I get the following


FATAL: Unknown capture source type 'broadcom' in source 'broadcom,eth0,wifi'
Done.


I tried figuring out how or what is used from the virtual machine interface, but seems the source is incorrect... any idea's on this one?

[Glyph]

darkside720, on Aug 28 2008, 01:37 PM, said:

Ok, I understand the basis for the kismet, but has anyoen ever tried installing it on a vmware and running the kismet there? I have it installed on a DELL D620 and Linux on the virtual machine with the network in the virtual machine running off of eth0. However, when I configured the kismet.conf file for

source=Broadcom,eth0,wifi, I get the following


FATAL: Unknown capture source type 'broadcom' in source 'broadcom,eth0,wifi'
Done.


I tried figuring out how or what is used from the virtual machine interface, but seems the source is incorrect... any idea's on this one?

Not sure but depending on how you've set the VM up it may NOT be able to access the physical interfaces.
Try changing it to use the virtual interface instead in the config file.

[webdevil]

Firstly kismet is wireless, aint it?
How come eth0?
Well, if vmware makes your wifi card as an ethernet one, I dont think it will be capable to do the sniffing.

Whats the output of

Quote

lspci | grep "Network controller"
lspci | grep "Ethernet controller"

[mango1122]

If you bridge the virtual card and a real wireless card , vmware will bridge it with a virtual wired card.Hence it wont get detected.You can use a Wireless USB for this.

[darkside720]

Thanks for the input guys. I will try using a wireless usb and see how that works out. Will keep you guys posted.