Kismet Wireless

Kismet Forums


Posted by:dom123
Subject:Odd SSID issue
Date:10:00:36 13/05/2011

> >
> > 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.

I upgraded the server to 2010.01.R1 and the drone to 2010-07-R1-1 but we're still seeing the scrambled SSIDs:

<essid cloaked="false">TcMKTALK-BCDC53</essid>
<essid cloaked="false">BTHomeHub2-2SF2</essid>
<essid cloaked="false">BTHomeHub2\2456SF2</essid>
<essid cloaked="false">BTHomeHubr\211k\033)\217</essid>

This sounds like the same issue:

Would you agree? I think the next step is to try applying that patch that Cutter409 created.

Reply to this message