My problem with the Socket card is that although I can run the kismet GUI fine; it doesn't show any activity most of the time. This occurs even though I'm standing next to an access point. Occassionally, it shows a few packets then seems to stop. Dmesg doesn't offer any relevant info. My SMC 2642w card works fine with my configuration. In RC-3 I had similar problem but it worked 30-50% of the time, seems to have gotten worse. Any ideas would be appreciated.
Jerry
Full Version: Kismet & Socket CF
I have got kismet to only show 1 router it's rather annoying 
someone should compile wellenreiterII for rc5 that would make me happy 
someone should compile wellenreiterII for rc5 that would make me happy
The normal socket driver cannot put the card into monitor mode. When using the driver with monitor patches it works well.
QUOTE(tz @ Oct 21 2004, 12:55 PM)
The normal socket driver cannot put the card into monitor mode. When using the driver with monitor patches it works well.
@Tz
Ok, how do I patch the drivers?
@Laze - can the patch for the socket driver be included in the next release?
Cheers,
Jerry
Can anyone please tell me how I apply this patch? I also have this Socket CF W-lan card, and I'm experiencing the same problem.
I'm having the same problem with a Symbol CF and I can't seem to patch the drivers myself or find pre-patched versions. Anyone have prepatched versions of Socket drivers they can make available?
Thanks,
NXK
Update: Duh, the Wiki points us here:
Getting your Socket...
Right under our noses...
Thanks,
NXK
Update: Duh, the Wiki points us here:
Getting your Socket...
Right under our noses...
QUOTE(NXK @ Feb 26 2005, 04:24 PM)
I'm having the same problem with a Symbol CF and I can't seem to patch the drivers myself or find pre-patched versions. Anyone have prepatched versions of Socket drivers they can make available?
Thanks,
NXK
Update: Duh, the Wiki points us here:
Getting your Socket...
Right under our noses...
Thanks,
NXK
Update: Duh, the Wiki points us here:
Getting your Socket...
Right under our noses...
If you're using RC9 or 9 or 9.1 the patch has already been applied. The problem I was having was turned out not to be drivers in the kernel but the version of kismet in the feed. My problem was fixed by installing the kismet ipk from the kismet site it works fine. See here
Cheers,
Jerry
I havent been in any high traffic areas sniffing for wifi, but kismet seems to work just fine. Airsnort also works, just have to make an icon for it as the ipk only installs the binary.
Please excuse the lack of punctuation, this post brought to you by my C860 and Socket wireless card.
Please excuse the lack of punctuation, this post brought to you by my C860 and Socket wireless card.
QUOTE(jerrybme @ Feb 8 2005, 04:26 PM)
I finally have gotten Kismet to work on RC9. Although I don't think it's a ROM issue. As stated in my above post, my problem was that while Kismet would run it wouldn't channel hop. It would stop on channel 1.
To solve this I installed the ipk from the Kismet site here It is version 2005-01-R1. Scroll down the page & look for the ARM Binary section.
It installed fine but didn't like being on the SD so I had to install on /
This release seems to play much better with the Socket cards. I've been running for several days now without problems.
Cheers,
Jerry
To solve this I installed the ipk from the Kismet site here It is version 2005-01-R1. Scroll down the page & look for the ARM Binary section.
It installed fine but didn't like being on the SD so I had to install on /
This release seems to play much better with the Socket cards. I've been running for several days now without problems.
Cheers,
Jerry
I tried installing this version, but when I want to start Kismet, I get the following error: "Error opening terminal: xterm."
If I use the same kismet.conf and kismet_ui.conf files in the Kismet version from the RC9 feed, it freezes at channel hopping, but doesn't show an error.
Is there anyone else who got the same error, or does anyone know how to fix this?
QUOTE(Ferdy @ Mar 2 2005, 10:19 AM)
I tried installing this version, but when I want to start Kismet, I get the following error: "Error opening terminal: xterm."
If I use the same kismet.conf and kismet_ui.conf files in the Kismet version from the RC9 feed, it freezes at channel hopping, but doesn't show an error.
Is there anyone else who got the same error, or does anyone know how to fix this?
If I use the same kismet.conf and kismet_ui.conf files in the Kismet version from the RC9 feed, it freezes at channel hopping, but doesn't show an error.
Is there anyone else who got the same error, or does anyone know how to fix this?
Do you have
CODE
export TERMINFO=/usr/share/terminfo
export TERM=xterm-color
export TERM=xterm-color
in your .bashrc file?
I believe I got this error too at first but the above fixed it.
Jerry
QUOTE(jerrybme @ Mar 2 2005, 04:40 PM)
QUOTE(Ferdy @ Mar 2 2005, 10:19 AM)
I tried installing this version, but when I want to start Kismet, I get the following error: "Error opening terminal: xterm."
If I use the same kismet.conf and kismet_ui.conf files in the Kismet version from the RC9 feed, it freezes at channel hopping, but doesn't show an error.
Is there anyone else who got the same error, or does anyone know how to fix this?
Do you have
CODE
export TERMINFO=/usr/share/terminfo
export TERM=xterm-color
export TERM=xterm-color
in your .bashrc file?
I believe I got this error too at first but the above fixed it.
Jerry
Thanks for the quick reply! Kismet works great now!
Did you-all get Kismet to start from the GUI? It works great for me, but I must launch it from the terminal, and then start the kismet_qt GUI.
QUOTE(rjohnson1969 @ Apr 27 2005, 10:13 AM)
Did you-all get Kismet to start from the GUI? It works great for me, but I must launch it from the terminal, and then start the kismet_qt GUI.
Um, based on the info in your sig, you may have posted in the wrong forum, this thread is about using kismet with pdaxrom & the socket lowpower card. Run from the terminal in pdaxrom, it starts it's own terminal based gui. No qt involved.
Glad you got it work tho
Which driver should I be using under kismet.conf with my Socket CF card? I have tried numerous combinations to no success.
QUOTE(Foxdie @ May 2 2005, 01:34 AM)
Which driver should I be using under kismet.conf with my Socket CF card? I have tried numerous combinations to no success.
Hi Foxdie:
CODE
source=orinoco, eth0, orinocosource
is what's uncommented in my kismet.conf file. Which version of kismet are you using?
Has anyone been able to successfully determine WEP keys based on packet dumps from Kismet? I am getting "no valid packets" error from bsdairtools/dwepcrack, but have yet to try airsnort.
I am using a Linksys WCF12 CF card and the orinoco driver (which could well be the problem).
I am using a Linksys WCF12 CF card and the orinoco driver (which could well be the problem).
The right souce would have no space between commas.
I don't really understand the dump file. It doesn't show me anything useful.
CODE
source=orinoco,eth0,orinocosource
QUOTE
Has anyone been able to successfully determine WEP keys based on packet dumps from Kismet? I am getting "no valid packets" error from bsdairtools/dwepcrack, but have yet to try airsnort.
I don't really understand the dump file. It doesn't show me anything useful.
switching to the hostap driver solved it.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.