This commit fixed the problem. Thanks!
| CVSROOT: /cvs
| Module name: src
| Changes by: dam...@cvs.openbsd.org 2011/01/11 14:04:46
|
| Modified files:
| sys/dev/usb: if_urtw.c
|
| Log message:
| use ic-ic_ibss_chan instead of ic-ic_bss-ni_chan for Rx radiotap
| since the
I was not sure if I mistyped usbtask and made this note to check the sources
as soon as the machine comes back up. This was not meant to be sent this via
this report, I simply forgot to edit it out again. Sorry for that.
You did not mistype usbtask. usbatsk stands for usb abort task.
Probably
If I run kismet this (handwritten transcript) happens:
# kismet
[some kismet initialization output]
Gathering packets...
[from now on text is white on blue]
uvm_fault(0xd0a26a60, 0xf000, 0, 1) - e
kernel: page fault trap, code=0
Stopped at urtw_rxeof+0x215: movzwl 0(%eax),%eax
ddb{0} trace
On Tuesday 11 January 2011 15:14:50 Benjamin Nadland wrote:
[...]
+source=radiotap_bsd_ab,urtw0,radiotap_bsd_ab
Why radiotap_bsd_ab? urtw(4) is an 802.11b/g only device and does not
support 802.11a operation. This still doesn't explain your crash as
kismet_server should receive an error and
On Tue, Jan 11, 2011 at 03:46:46PM +, Pedro la Peu wrote:
On Tuesday 11 January 2011 15:14:50 Benjamin Nadland wrote:
[...]
+source=radiotap_bsd_ab,urtw0,radiotap_bsd_ab
Why radiotap_bsd_ab?
Probably mindless copying from an old config where I had a rum(4) device.
urtw(4) is an
On Tuesday 11 January 2011 16:29:07 Benjamin Nadland wrote:
Just tested with radiotap_bsd_b and I get the same crash with the same
traces.
There is nothing that kismet_server does with the device that cannot be
replicated with ifconfig(8) and tcpdump(8). If you can reproduce the
crash with
On Tue, Jan 11, 2011 at 04:14:50PM +0100, Benjamin Nadland wrote:
If I run kismet this (handwritten transcript) happens:
# kismet
[some kismet initialization output]
Gathering packets...
[from now on text is white on blue]
uvm_fault(0xd0a26a60, 0xf000, 0, 1) - e
kernel: page fault trap,
7 matches
Mail list logo
