Kismet Wireless

Kismet Forums

 

Posted by:algol
Subject:Odd SSID issue
Date:14:10:18 30/06/2011

Is there a workaround on the server side now or do we need to wait for new drone code? I am using openwrt on a Netgear 3700v2 for the drone side and BT5 for the server side and seeing this issue.

> >
> > I have followed your suggestion for validatefcs=true but it doesn't seem to have made any difference, that we can tell anyway:
> >
> > ncsource=wlan0:type=ath9k,validatefcs=true
> >
>
> the drone capture side will not do fcs validation, because it never looks that deep into the packet. it decaps the per-packet headers (which are os/source specific) and pops them into the drone format, then sends it on unmolested.
>
> I'm 99% sure that the drone comms don't have a field for the FCS and that it's not transferred. Adding that won't be terribly difficult, I'll post here when I've got it in SVN, but you'll have to update the drone side of things.
>
> I'll look a little more at what is being transferred, but I'm not sure you can even kluge the server end to do fcs w/ the current drone code.


Reply to this message