Re: error: unable to ioctl device socket

On Sat, Jul 20, 2002 at 08:25:15PM -0400, [email protected] said:
> Hi,
> 
> Two problems, possibly related:
> 
>  1) When I quit dstumbler I get an error message at the
> bottom of the screen:
>  "error: unable to ioctl device socket: Invalid argument"

I got that error a while back, and after I applied the source mods, rebuilt
my kernel and rebooted, it stopped.

>  2) I can't seem to detect a simple WLAN consisting of two
> PCs in Ad-Hoc mode, with 40-bit WEP. The dstumbler screen
> stays blank. Yes, I understand that dstumbler relies on AP
> broadcasts and Station discovery requests, but should it not
> see some sort of activity?  (tcpdump works)

dstumbler sniffs the 802.11 radio frames directly; IIRC it does not rely on
broadcasts or discovery requests. If dstumbler is working properly, you
_should_ get some visible activity from any active AP or node in range of
your sniffing card.

> IBM thinkpad A21e,
> OpenBSD 3.1-current GENERIC (dmesg below)
> BAT built from ports.

Use the current cvs version; the version in ports may not work properly with
3.1 (especially 3.1-current).
-- 
-= Scott Francis || darkuncle (at) darkuncle (dot) net =-
  GPG key CB33CCA7 has been revoked; I am now 5537F527
        illum oportet crescere me autem minui

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9O1gYWaB7jFU39ScRAgM6AJ4/BfTwspmZ9emwSQK9aUY3/p4h4wCgrivf
i61W/r9aTufh/aLwpIIYhTw=
=gvtv
-----END PGP SIGNATURE-----