dwepdump, no output and "-a" problem
"" <[email protected]> Sun, 20 Apr 2003 21:28:24 -0700
| Newsgroups | gmane.network.wireless.bsd.airtools |
|---|---|
| Message-ID | <[email protected]> |
h1kari, Thanks for the very quick response time. I've done more testing based on your suggestions I think you're right in suspecting a problem with the driver of maybe the pccard setup. I tried the same two Prism cards in another FreeBSD 4.7 machine and prism2dump and dstumbler -o work just fine. So I know my Prism2 hardware (Netgear MA401 and Dlink DWL-650) are fine. It must be something in the wi driver or pccard setup on this particular FreeBSD machine. In reading my dmesg for wi0 I noticed something odd, I see this: "wi0 watchdog timeout". Here's the dmesg for wi0 after starting and stopping prism2dump in port mode 5: (using Netgear MA401) wi0 at port 0x280-0x2bf irq 5 slot 1 on pccard1 wi0: 802.11 address: 00:30:ab:00:00:00 wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163-SST-flash wi0: Intersil Firmware: Primary 0.03.00, Station 1.03.04 wi0: promiscuous mode enabled wi0: watchdog timeout wi0: watchdog timeout wi0: promiscuous mode disabled I'm guessing the watchdog timeout is going to lead me to my problem but I'm not sure where to look next. I've started trying to compare the configs between the two FBSD 4.7 machines. So far I can see the wi0 pccards are using different resources. working machine: wi0 at port 0x240-0x27f irq 3 slot 0 on pccard0 non-working "watchdog timeout" machine: wi0 at port 0x280-0x2bf irq 5 slot 1 on pccard1 p.s. Can you tell me what "-F 1" in wicontrol does? I don't see it in the man for wicontrol. Do you have any more suggestions? Thanks, Al.