Re: dstumbler & mgmt beacons

h1kari <[email protected]> Mon, 17 Mar 2003 15:45:10 -0800
Newsgroups gmane.network.wireless.bsd.airtools
Message-ID <BA9B9E06.9AC7%[email protected]>
Good point... I'll add that to my todo list for the next release.

Thanks,
-h1kari

On 3/15/03 7:50, "Tye F. Hammerle" <[email protected]> wrote:

> I haven't used dstumbler much, mostly dwepdump and dwepcrack. In my test
> setup I have an access-point setup to not broadcast the SSID. I've
> noticed that dstumbler doesn't pick up the access-point for quite a long
> time. I seems that it only sees the access-point when a client associates.
> 
> In running prism2dump I see that the access-point sends out mgmt-beacon
> packets pretty regularly with "ssid: []" along with the channel info. It
> seems that dstumbler ignores these since when I see one it doesn't come
> up in dstumbler.
> 
> I'm wondering why dstumbler doesn't see these mgmt-beacons and display
> them? Why wait for a client association to grab the SSID? When the SSID
> is passed it can be matched to the access-points MAC address and the
> display updated.
> 
> Netstumbler seems to do the same thing. I've noticed it doesn't pick up
> access-points which don't broadcast the SSID.
> 
> Seems like an oversight. We should want to know when we see *any*
> beacons and keep track of them updating the available information as we go.
> 
> I'm running OpenBSD 3.2 with a PCM-11 Linksys card, a Cisco 340
> Access-point.
> 
> Tye
> 
> _______________________________________________
> Bat mailing list
> [email protected]
> http://lists.dachb0den.com/mailman/listinfo/bat
>