Re: Kismet on OSX 10.5.1 Leopard

2008-03-17 Thread Ben Greenfield 


On Mar 17, 2008, at 8:03 PM, Walt Scrivens wrote:

No, it was only working in active mode.  I passive mode it runs for  
a few seconds and dies.  It also leaves the AirPort disconnected.   
Here's teh dump file it created - I don't know if that will help  
anyone.


I have .21a rev.242 running on a macbook air in passive and active  
mode. I had to set my bpf device in advanced preferences to match my  
airport card.


I'm using Apple Airport Extreme card, passive mode driver.




Model: MacBookPro1,1, BootROM MBP11.0055.B08, 2 processors, Intel  
Core Duo, 2.16 GHz, 2 GB
Graphics: kHW_ATIr520Item, ATY,RadeonX1600, spdisplays_pcie_device,  
256 MB

Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C,  
0x86), 1.3.2
Bluetooth: Version 2.1.0f14, 2 service, 1 devices, 1 incoming serial  
ports

Network Service: Parallels NAT, Ethernet, en3
Network Service: Parallels Host-Guest, Ethernet, en4
Serial ATA Device: ST9100824AS, 93.16 GB
Parallel ATA Device: MATSHITADVD-R   UJ-857
USB Device: Built-in iSight, Micron, high_speed, 500 mA
USB Device: iPod, Apple, high_speed, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer,  
full_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed,  
500 mA

USB Device: IR Receiver, Apple Computer, Inc., full_speed, 500 mA

On the whole I'm pretty discouraged with KisMac and would rather use  
plain vanilla kismet, except that does not work either.  From what I  
read it's all Apple's fault and I don't know if there will ever be a  
workaround.


I have read this and wordered since it does work for me.

Ben




Fortunately I have a Zaurus and a Nokia 800, both of which run  
kismet just fine.  I can take the files created by either to the Mac  
for analysis with Wireshark.  (Now if CACE Technologies would come  
out with a Mac version of AirPcap and their channel-hopping  
modification of wireshark)


Walt


On Mar 17, 2008, at 7:32 PM, [EMAIL PROTECTED] wrote:


did you get it working on leopard??
i got a macbook pro core duo (july 2006) running leopard (10.5.1),  
and can't get it working in passive mode.

did you get it working in passive?
Searching at google, I haven't seen anybody that has got it working  
in passive mode on leopard...


Please explain how you did it!

thanks
walts wrote:


That worked!  I have only my own home network to look at here - will
have to wait until I get to work tomorrow where I have a more robust
test environment to really give this a workout, but it looks
promising.  Thanks for the help!

Walt

On Mar 16, 2008, at 6:26 PM, paul beard wrote:


[SNIP]
Hmm, I have r239 . . . it seems to work just fine. latest version
seems to be 242.

[SNIP]
--
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


-
MacBook Pro (Intel) with 2GB RAM
Leopard (10.5.1)
BootCamp with Windows XP Pro


Quoted from:
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tp13843207p16085962.html



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-17 Thread Walt Scrivens 
No, it was only working in active mode.  I passive mode it runs for a  
few seconds and dies.  It also leaves the AirPort disconnected.   
Here's teh dump file it created - I don't know if that will help anyone.


Model: MacBookPro1,1, BootROM MBP11.0055.B08, 2 processors, Intel Core  
Duo, 2.16 GHz, 2 GB
Graphics: kHW_ATIr520Item, ATY,RadeonX1600, spdisplays_pcie_device,  
256 MB

Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86),  
1.3.2
Bluetooth: Version 2.1.0f14, 2 service, 1 devices, 1 incoming serial  
ports

Network Service: Parallels NAT, Ethernet, en3
Network Service: Parallels Host-Guest, Ethernet, en4
Serial ATA Device: ST9100824AS, 93.16 GB
Parallel ATA Device: MATSHITADVD-R   UJ-857
USB Device: Built-in iSight, Micron, high_speed, 500 mA
USB Device: iPod, Apple, high_speed, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer,  
full_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed,  
500 mA

USB Device: IR Receiver, Apple Computer, Inc., full_speed, 500 mA

On the whole I'm pretty discouraged with KisMac and would rather use  
plain vanilla kismet, except that does not work either.  From what I  
read it's all Apple's fault and I don't know if there will ever be a  
workaround.


Fortunately I have a Zaurus and a Nokia 800, both of which run kismet  
just fine.  I can take the files created by either to the Mac for  
analysis with Wireshark.  (Now if CACE Technologies would come out  
with a Mac version of AirPcap and their channel-hopping modification  
of wireshark)


Walt


On Mar 17, 2008, at 7:32 PM, [EMAIL PROTECTED] wrote:


did you get it working on leopard??
i got a macbook pro core duo (july 2006) running leopard (10.5.1),  
and can't get it working in passive mode.

did you get it working in passive?
Searching at google, I haven't seen anybody that has got it working  
in passive mode on leopard...


Please explain how you did it!

thanks
walts wrote:


That worked!  I have only my own home network to look at here - will
have to wait until I get to work tomorrow where I have a more robust
test environment to really give this a workout, but it looks
promising.  Thanks for the help!

Walt

On Mar 16, 2008, at 6:26 PM, paul beard wrote:


[SNIP]
Hmm, I have r239 . . . it seems to work just fine. latest version
seems to be 242.

[SNIP]
--
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


-
MacBook Pro (Intel) with 2GB RAM
Leopard (10.5.1)
BootCamp with Windows XP Pro


Quoted from:
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tp13843207p16085962.html



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-17 Thread Eric Cronin 
As you noticed in the Kismet notes this is a known issue...  Bumping  
Kismet to a macports hosted svn snapshot is on my todo list (Mike says  
an official one or release isn't in the works until a number of other  
bugs get sorted out), but I've been hoping pcap would do an update  
also.  Since pcap is a dependency for a number of things I'm a little  
less excited about making that track cvs...


Thanks,
Eric


njstaticuser wrote:


libpcap is in charge of creating the wlt1 device. Since leopard  
changed

the way it handled its hardware since Tiger, you MUST have the latest
version of libpcap, which I believe is dated December of 2007.


[SNIP]

-
MacBook Pro (Intel) with 2GB RAM
Leopard (10.5.1)
BootCamp with Windows XP Pro
--
View this message in context: 
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tp13843207p16092237.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-17 Thread Daniel J. Luke 

On Mar 17, 2008, at 10:36 AM, Walt Scrivens wrote:
What is the deal here?  I can submit freely to this list, and my  
messages get cross-posted to Nabble, but I can't answer them there?



Maybe you should ask Nabble?

I don't know who set up the bridge from the mailing list to that web  
forum, but as far as I know, it's not something that the project  
specifically set up or supports.

--
Daniel J. Luke
++
| * [EMAIL PROTECTED] * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-17 Thread Walt Scrivens 
I don't understand what's happening here.  Yesterday I got a message  
that there was a reply to a message I had posted on this mailing list,  
from "njstaticuser" on the Nabble forum.  The message did NOT appear  
in my mailbox from MacPorts Users.  I logged in to the Nabble forum  
and submitted a reply, which is shown below.  Then a few hours later I  
got a message that the moderator was refusing to post my message.


What is the deal here?  I can submit freely to this list, and my  
messages get cross-posted to Nabble, but I can't answer them there?


Walt

===

Message submitted to Nabble follows:



njstaticuser wrote:
libpcap is in charge of creating the wlt1 device. Since leopard  
changed the way it handled its hardware since Tiger, you MUST have the  
latest version of libpcap, which I believe is dated December of 2007.

[SNIP]

Thanks.
The version of libpcap I got from CVS had a VERSION file containing  
0.9-PRE-CVS.  The bulk of the "important" files (to my mind anyway)  
are dated March 13 and 14 2008.  In any event it works with KisMac but  
not with the command-line kismet.


I'm confused about that - in the Linux installations of kismet that  
I'm familiar with, there is a server piece and several clients ranging  
from a text-only display to varying degrees of GUI.  It looks like  
KisMac is a totally different package.


I'm also confused about this forum.  Your message came to me only from  
the Nabble forum, whereas the rest of the thread (and my replies) has  
been on the Mac Ports Users mailing list (macports-users@lists.macosforge.org 
).  what's the connection, and where should I be posting?


Walt

==


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-17 Thread walts 

Thanks.
The version of libpcap I got from CVS had a VERSION file containing
0.9-PRE-CVS.  The bulk of the "important" files (to my mind anyway) are
dated March 13 and 14 2008.  In any event it works with KisMac but not with
the command-line kismet.

I'm confused about that - in the Linux installations of kismet that I'm
familiar with, there is a server piece and several clients ranging from a
text-only display to varying degrees of GUI.  It looks like KisMac is a
totally different package. 

I'm also confused about this forum.  Your message came to me only from the
Nabble forum, whereas the rest of the thread (and my replies) has been on
the Mac Ports Users mailing list (macports-users@lists.macosforge.org). 
what's the connection, and where should I be posting?

Walt




njstaticuser wrote:
> 
> libpcap is in charge of creating the wlt1 device. Since leopard changed
> the way it handled its hardware since Tiger, you MUST have the latest
> version of libpcap, which I believe is dated December of 2007.
> 
[SNIP]

-
MacBook Pro (Intel) with 2GB RAM
Leopard (10.5.1)
BootCamp with Windows XP Pro
-- 
View this message in context: 
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tp13843207p16092237.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-16 Thread paul beard 
On Sun, Mar 16, 2008 at 4:49 PM, Walt Scrivens <[EMAIL PROTECTED]> wrote:

> That worked!  I have only my own home network to look at here - will have
> to wait until I get to work tomorrow where I have a more robust test
> environment to really give this a workout, but it looks promising.  Thanks
> for the help!
>
>
No problem. A walk around the block can be informative as well (I think I
counted 30-something networks last time I tried it).
-- 
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-16 Thread Walt Scrivens 
That worked!  I have only my own home network to look at here - will  
have to wait until I get to work tomorrow where I have a more robust  
test environment to really give this a workout, but it looks  
promising.  Thanks for the help!


Walt

On Mar 16, 2008, at 6:26 PM, paul beard wrote:


[SNIP]
Hmm, I have r239 . . . it seems to work just fine. latest version  
seems to be 242.


[SNIP]
--
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-16 Thread paul beard 
On Sun, Mar 16, 2008 at 2:22 PM, Walt Scrivens <[EMAIL PROTECTED]> wrote:

> I'm pretty comfortable with command-line and green-screen interfaces so I
> haven't tried it so far.
>

Me too, but sometimes it's worth trying a known-good solution to isolate
problems.

> I just downloaded and installed R65 (there are several versions shown in
> my google search and that seemed to be the highest number).
>

Hmm, I have r239 . . . it seems to work just fine. latest version seems to
be 242 .


> In any event, here is the error I got:
>
> KisMAC is not able to load the Apple Airport driver, if you killed it by
> loading the Viha driver. Try restarting KisMAC.
>
> The error dialog box kept on popping up over and over, so I force-quit
> Kismac and restarted it, with the same result.
>

I have never had a problem with it (late 2003 iBook, Airport Extreme card,
10.4.11).

-- 
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-16 Thread Walt Scrivens 
I'm pretty comfortable with command-line and green-screen interfaces  
so I haven't tried it so far.
I just downloaded and installed R65 (there are several versions shown  
in my google search and that seemed to be the highest number).

In any event, here is the error I got:

KisMAC is not able to load the Apple Airport driver, if you killed it  
by loading the Viha driver. Try restarting KisMAC.


The error dialog box kept on popping up over and over, so I force-quit  
Kismac and restarted it, with the same result.


The KisMac forum is definitely unfriendly, so I haven't posted any  
request for help there, but the consensus seems to be that the Air  
Port Extreme with the Atheros chipset won't work with KisMac anyway.   
I have Kismet on other devices so it's not a crisis, just that I would  
rather not lug around so much equipment :-)


Walt



On Mar 16, 2008, at 5:04 PM, paul beard wrote:




On Sun, Mar 16, 2008 at 1:26 PM, walts <[EMAIL PROTECTED]> wrote:

I followed the instructions and did not notice any errors in setting  
up

libpcap.  Here's what I get:

does the Kismac binary work with 10.5.x?
--
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-16 Thread paul beard 
On Sun, Mar 16, 2008 at 1:26 PM, walts <[EMAIL PROTECTED]> wrote:

>
> I followed the instructions and did not notice any errors in setting up
> libpcap.  Here's what I get:
>

does the Kismac binary work with 10.5.x?
-- 
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-03-16 Thread walts 

I followed the instructions and did not notice any errors in setting up
libpcap.  Here's what I get:


Macintosh:libpcap walts$ sudo kismet
Launching kismet_server: /opt/local/bin/kismet_server
Will drop privs to walts (501) gid 501
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.
INFO:  wlt1 looks like an Atheros card running under Darwin.
Source 0 (airport_extreme): Enabling monitor mode for darwin source
interface en1 channel 6...
Source 0 (airport_extreme): Opening darwin source interface wlt1...
FATAL: BIOCSETIF: wlt1: Device not configured
Done.
Macintosh:libpcap walts$ 

I have the source set in kismet.conf:
source=darwin,en1,airport_extreme
and it looks like it's opening that correctly, but then it stumbles on wlt1
(which does not exist in kismet.conf).  I'm not sure what to do at this
point.

Walt

njstaticuser wrote:
> 
> What you need to do is to get the latest libpcap. You can get it through
> CVS current:
> 
> cvs -d :pserver:[EMAIL PROTECTED]:/tcpdump/master login
> 
> cvs -d :pserver:[EMAIL PROTECTED]:/tcpdump/master checkout libpcap
> tcpdump
> cd libpcap
> ./configure
> make
> sudo make install
> 
> then try running kismet again and it should work fine.
> hope that helps.
> 
> 
> 


-
MacBook Pro (Intel) with 2GB RAM
Leopard (10.5.1)
BootCamp with Windows XP Pro
-- 
View this message in context: 
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tp13843207p16083591.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2008-01-02 Thread caliel 
Paul,

Sorry for the delayed response, but I wanted to make sure that the thread
is complete for others who are researching. From the KisMAC faq
(http://kismac.macpirate.ch/wiki/doku.php?id=faq) 

-
If you've updated to OS 10.4.10, you MUST use r239. OS 10.5 (Leopard)
breaks AirPort Extreme passive mode support again, but shouldn't break
support for other devices (USB and PCMCIA).
-

This is what the Kismet team told me they are also facing.  I assume both
parties are working on the issue, but it seems to be a communication
problem between Apple developers and Kis[Mm]?? developers. Naturally, the
proper solution is to use 1.4.10, then I could use either of them.
Pioneers, as they say, take the arrows :)

--caliel


On Sat, 8 Dec 2007 19:33:00 -0800, "paul beard" <[EMAIL PROTECTED]>
wrote:
> On 11/28/07, caliel <[EMAIL PROTECTED]> wrote:
>>
>> I have returned home from my holiday travels with eager anticipation to
>> try
>> kismet with my ralink USB Wi-Fi card.  Just as I plugged it in, I
> realized
>> .. .. darwin and viha are the only valid capture sources for
> OSX!
>>
> 
> Any reason not to use KisMac?
> 
> 
> 
> --
> Paul Beard / www.paulbeard.org/
> <[EMAIL PROTECTED]/[EMAIL PROTECTED]>

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2007-12-08 Thread paul beard 
On 11/28/07, caliel <[EMAIL PROTECTED]> wrote:
>
> I have returned home from my holiday travels with eager anticipation to
> try
> kismet with my ralink USB Wi-Fi card.  Just as I plugged it in, I realized
> .. .. darwin and viha are the only valid capture sources for OSX!
>

Any reason not to use KisMac?



-- 
Paul Beard / www.paulbeard.org/
<[EMAIL PROTECTED]/[EMAIL PROTECTED]>
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2007-12-08 Thread caliel 
UPDATE: The kismet team is having trouble getting info on how to set RFMon
in the Airport drivers that ship with Leopard.  So we must wait.

On Wed, 28 Nov 2007 09:36:40 -0500, caliel <[EMAIL PROTECTED]> wrote:
> I have returned home from my holiday travels with eager anticipation to
try
> kismet with my ralink USB Wi-Fi card.  Just as I plugged it in, I
realized
> .. .. darwin and viha are the only valid capture sources for OSX!
> In my shame and desperation I was heard to utter several words, of which
> my
> mother would NOT approve.  Now I am back to square one with kismet.  Is
it
> my karma keeping kismet from working? or is there another answer to this
> problem?
> 
> Actually, I am not exactly back at square one.  I accidentally left the
> capture source in kismet.conf as "darwin" and changed the interface to
> "en2" which is the ralink.   I got the same output as below, even to the
> point that it indicated the en2 appeared to be a broadcom that already
had
> rfmon set.
> 
> --caliel
> 
> On Thu, 22 Nov 2007 15:03:00 -0800 (PST), caliel
<[EMAIL PROTECTED]>
> wrote:
>>
>> I am away from access to alternate hardware, please let me know what you
>> find.  I have not found a resolution as yet.  I saw you also responded
> to
>> a
>> post at the Kismet site, perhaps one of the 3 of us will find a
> solution.
>>
>> --C
>>
>> trolley wrote:
>>>
>>>
>>> caliel wrote:
>>>>
>>>>
>>>> Kismet fails as follows.
>>>>
>>>>  Yliakum:~ caliel$ sudo kismet
>>>>  Password:
>>>>  Launching kismet_server: /opt/local/bin/kismet_server
>>>>  Will drop privs to caliel (502) gid 20
>>>>  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.
>>>>  INFO:  wlt1 looks like a Broadcom card running under Darwin.
>>>>  Source 0 (airport_extreme): Enabling monitor mode for darwin
>> source
>>>> interface en1 channel 6...
>>>>  î|07-11-19 14:00:48.175 kismet_server[3092:10b] †
>>>>  INFO: en1 looks like a Broadcom card running under Darwin and
>>>> already
>>>> has monitor mode enabled in the kernel.
>>>>  Source 0 (airport_extreme): Opening darwin source interface
>> wlt1...
>>>>  FATAL: BIOCSETIF: wlt1: Device not configured
>>>>  Done.
>>>>
>>>>
>>>
>>> I'm getting the same error on a Powerbook G4. Did you figure anything
>> out?
>>> I'm going to try it with a Ralink USB dongle and see if I have any more
>>> luck.
>>>
>>
>> --
>> View this message in context:
>>
>
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tf4838737.html#a13904713
>> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>>
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo/macports-users
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users
> )

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2007-11-28 Thread caliel 
I have returned home from my holiday travels with eager anticipation to try
kismet with my ralink USB Wi-Fi card.  Just as I plugged it in, I realized
.. .. darwin and viha are the only valid capture sources for OSX! 
In my shame and desperation I was heard to utter several words, of which my
mother would NOT approve.  Now I am back to square one with kismet.  Is it
my karma keeping kismet from working? or is there another answer to this
problem?

Actually, I am not exactly back at square one.  I accidentally left the
capture source in kismet.conf as "darwin" and changed the interface to
"en2" which is the ralink.   I got the same output as below, even to the
point that it indicated the en2 appeared to be a broadcom that already had
rfmon set.

--caliel

On Thu, 22 Nov 2007 15:03:00 -0800 (PST), caliel <[EMAIL PROTECTED]>
wrote:
> 
> I am away from access to alternate hardware, please let me know what you
> find.  I have not found a resolution as yet.  I saw you also responded to
> a
> post at the Kismet site, perhaps one of the 3 of us will find a solution.
> 
> --C
> 
> trolley wrote:
>> 
>> 
>> caliel wrote:
>>> 
>>> 
>>> Kismet fails as follows.
>>> 
>>>  Yliakum:~ caliel$ sudo kismet
>>>  Password:
>>>  Launching kismet_server: /opt/local/bin/kismet_server
>>>  Will drop privs to caliel (502) gid 20
>>>  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.
>>>  INFO:  wlt1 looks like a Broadcom card running under Darwin.
>>>  Source 0 (airport_extreme): Enabling monitor mode for darwin
> source
>>> interface en1 channel 6...
>>>  î|07-11-19 14:00:48.175 kismet_server[3092:10b] †
>>>  INFO: en1 looks like a Broadcom card running under Darwin and
>>> already
>>> has monitor mode enabled in the kernel.
>>>  Source 0 (airport_extreme): Opening darwin source interface
> wlt1...
>>>  FATAL: BIOCSETIF: wlt1: Device not configured
>>>      Done.
>>> 
>>> 
>> 
>> I'm getting the same error on a Powerbook G4. Did you figure anything
> out?
>> I'm going to try it with a Ralink USB dongle and see if I have any more
>> luck.
>> 
> 
> -- 
> View this message in context:
>
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tf4838737.html#a13904713
> Sent from the MacPorts - Users mailing list archive at Nabble.com.
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2007-11-28 Thread caliel 
I have returned home from my holiday travels with eager anticipation to try
kismet with my ralink USB Wi-Fi card.  Just as I plugged it in, I realized
.. .. darwin and viha are the only valid capture sources for OSX! 
In my shame and desperation I was heard to utter several words, of which my
mother would NOT approve.  Now I am back to square one with kismet.  Is it
my karma keeping kismet from working? or is there another answer to this
problem?

Actually, I am not exactly back at square one.  I accidentally left the
capture source in kismet.conf as "darwin" and changed the interface to
"en2" which is the ralink.   I got the same output as below, even to the
point that it indicated the en2 appeared to be a broadcom that already had
rfmon set.

--caliel

On Thu, 22 Nov 2007 15:03:00 -0800 (PST), caliel <[EMAIL PROTECTED]>
wrote:
> 
> I am away from access to alternate hardware, please let me know what you
> find.  I have not found a resolution as yet.  I saw you also responded to
> a
> post at the Kismet site, perhaps one of the 3 of us will find a solution.
> 
> --C
> 
> trolley wrote:
>> 
>> 
>> caliel wrote:
>>> 
>>> 
>>> Kismet fails as follows.
>>> 
>>>  Yliakum:~ caliel$ sudo kismet
>>>  Password:
>>>  Launching kismet_server: /opt/local/bin/kismet_server
>>>  Will drop privs to caliel (502) gid 20
>>>  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.
>>>  INFO:  wlt1 looks like a Broadcom card running under Darwin.
>>>  Source 0 (airport_extreme): Enabling monitor mode for darwin
> source
>>> interface en1 channel 6...
>>>  î|07-11-19 14:00:48.175 kismet_server[3092:10b] †
>>>  INFO: en1 looks like a Broadcom card running under Darwin and
>>> already
>>> has monitor mode enabled in the kernel.
>>>  Source 0 (airport_extreme): Opening darwin source interface
> wlt1...
>>>  FATAL: BIOCSETIF: wlt1: Device not configured
>>>      Done.
>>> 
>>> 
>> 
>> I'm getting the same error on a Powerbook G4. Did you figure anything
> out?
>> I'm going to try it with a Ralink USB dongle and see if I have any more
>> luck.
>> 
> 
> -- 
> View this message in context:
>
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tf4838737.html#a13904713
> Sent from the MacPorts - Users mailing list archive at Nabble.com.
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Kismet on OSX 10.5.1 Leopard

2007-11-22 Thread caliel 

I am away from access to alternate hardware, please let me know what you
find.  I have not found a resolution as yet.  I saw you also responded to a
post at the Kismet site, perhaps one of the 3 of us will find a solution.

--C

trolley wrote:
> 
> 
> caliel wrote:
>> 
>> 
>> Kismet fails as follows.
>> 
>>  Yliakum:~ caliel$ sudo kismet
>>  Password:
>>  Launching kismet_server: /opt/local/bin/kismet_server
>>  Will drop privs to caliel (502) gid 20
>>  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.
>>  INFO:  wlt1 looks like a Broadcom card running under Darwin.
>>  Source 0 (airport_extreme): Enabling monitor mode for darwin source
>> interface en1 channel 6...
>>  î|07-11-19 14:00:48.175 kismet_server[3092:10b] †
>>  INFO: en1 looks like a Broadcom card running under Darwin and
>> already
>> has monitor mode enabled in the kernel.
>>  Source 0 (airport_extreme): Opening darwin source interface wlt1...
>>  FATAL: BIOCSETIF: wlt1: Device not configured
>>  Done.
>> 
>> 
> 
> I'm getting the same error on a Powerbook G4. Did you figure anything out?
> I'm going to try it with a Ralink USB dongle and see if I have any more
> luck.
> 

-- 
View this message in context: 
http://www.nabble.com/Kismet-on-OSX-10.5.1-Leopard-tf4838737.html#a13904713
Sent from the MacPorts - Users mailing list archive at Nabble.com.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Kismet on OSX 10.5.1 Leopard

2007-11-19 Thread caliel 
I am having trouble with kismet on leopard.  Details are as follows

 -- iBook G-4 1.2 GHz
 -- Broadcom BCM43xx 1.0 (4.170.25.8)
 -- MacPorts 1.520
 -- OSX 10.5.1
 -- Kismet 2007.10.R1


I made a backup of the original config file kismet.conf to kismet.conf.DIST
before changes were made. The results of a diff from the edited file to the
original file are as follows.


 Yliakum:~ caliel$ diff /opt/local/etc/kismet.conf
/opt/local/etc/kismet.conf.DIST 
 13c13
 < suiduser=caliel
 ---
 > suiduser=your_user_here
 27c27
 < source=darwin,en1,airport_extreme
 ---
 > source=none,none,addme

Kismet fails as follows.

 Yliakum:~ caliel$ sudo kismet
 Password:
 Launching kismet_server: /opt/local/bin/kismet_server
 Will drop privs to caliel (502) gid 20
 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.
 INFO:  wlt1 looks like a Broadcom card running under Darwin.
 Source 0 (airport_extreme): Enabling monitor mode for darwin source
interface en1 channel 6...
 î|07-11-19 14:00:48.175 kismet_server[3092:10b] †
 INFO: en1 looks like a Broadcom card running under Darwin and already
has monitor mode enabled in the kernel.
 Source 0 (airport_extreme): Opening darwin source interface wlt1...
 FATAL: BIOCSETIF: wlt1: Device not configured
 Done.

The README included with the install has the Airport Extreme (Broadcom and
Atheros) listed as supported by the "darwin" capture source.  Later in the
README the Airport Extreme (Broadcom) is listed in the section "Chipsets
known to NOT WORK"

Google indicates, using the search term: wlt1 "device not configured", that
at least one other person has observed this behavior.  

My question is obviously how do I get kismet working from here.  But I
would also like to know what wlt1 is.  Furthermore, why kismet is trying to
configure it as a capture source as well as en1?  I have tried to be
thorough in my description of the circumstances.  If any further
information is required to understand the situation, please let me know.

--Caliel

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users