> > : dstumbler breaks; on startup it reports
> > : "unable to ioctl device socket: Input/output error".
> >
> > As root or no?
>
> I have a rebuilt system finally that I could test this against and I'm
> actually getting a different error message on startup of dstumbler:
>
> error: unable to ioctl device socket: Invalid argument
>
> From ktrace:
>
> 43042 dstumbler CALL sigaction(0x12,0x280b5850,0)
> 43042 dstumbler RET sigaction 0
> 43042 dstumbler CALL socket(0x2,0x2,0)
> 43042 dstumbler RET socket 3
> 43042 dstumbler CALL ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0)
> 43042 dstumbler RET ioctl 0
> 43042 dstumbler CALL ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0)
> 43042 dstumbler RET ioctl 0
> 43042 dstumbler CALL ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0)
> 43042 dstumbler RET ioctl 0
> 43042 dstumbler CALL ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0)
> 43042 dstumbler RET ioctl -1 errno 22 Invalid argument
> 43042 dstumbler CALL sigaction(0x12,0x280b5838,0x280b5850)
> 43042 dstumbler RET sigaction 0
> 43042 dstumbler CALL poll(0xbfbff3e8,0x1,0)
> 43042 dstumbler RET poll 0
> 43042 dstumbler CALL poll(0xbfbff3e8,0x1,0)
> 43042 dstumbler RET poll 0
> 43042 dstumbler CALL write(0x1,0x8060000,0x5e)
> 43042 dstumbler GIO fd 1 wrote 94 bytes
> "\^[[52;22H\^[[34m\^[[1m[\^[[31m error: unable to ioctl device
socket: \
> Invalid argument \^[[C\^[[39;49m\^[[m\^O"
>
dstumbler uses WI_RID_SCAN_REQ to initiate a scan for AP's. This required
the application know whether it was talking to a prims/wavelan/symbol card
so was replaced by WI_RID_SCAN_APS which provides a device-independent
interface. I changed wicontrol to deal with this; it would be good if
dstumbler did likewise. Otherwise I can look at adding a backwards
compatibility entry for WI_RID_SCAN_REQ.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
