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
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
with these it would aid debugging.
I don't have a urtw(4) unfortunately.
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,
2009/8/11 damien.bergam...@free.fr:
| [...]
| AFAIK, hostap mode is crappy with most drivers, since they doesn't vary
| the sending strength (AKA 'power saving') and the clients expect this.
| [...]
Actually, power saving at the AP has nothing to do with sending strength.
It is about
!)
Are there any plans to add hostap mode to urtw(4) driver ?
May I suggest to delete those lines from the manpage. It misled me.
Regards
Piotr Kapczuk
/wiki/Comparison_of_open_source_wireless_drivers
it simply does not. (sic!)
Are there any plans to add hostap mode to urtw(4) driver ?
Perhaps.
The urtw man page does not currently include those features.
May I suggest to delete those lines from the manpage. It misled me.
Certainly not.
talking about 'man 4
urtw'. How can it be driver independent ?
[...]
Are there any plans to add hostap mode to urtw(4) driver ?
Perhaps.
I guess it means nothing changed in -current. Well, I have to find
some other USB card then. Can you recommend something ?
The urtw man page does not currently
On Tue, Aug 11, 2009 at 05:17:33PM +0200, Piotrek Kapczuk wrote:
Errr ... Maybe I was not specific enough. I'm talking about 'man 4
urtw'. How can it be driver independent ?
'Adapter independent' might be more correct.
I've just checked and I also see in 'urtw(4)' manpage that driver can
| [...]
| AFAIK, hostap mode is crappy with most drivers, since they doesn't vary
| the sending strength (AKA 'power saving') and the clients expect this.
| [...]
Actually, power saving at the AP has nothing to do with sending strength.
It is about buffering frames in the AP for clients that are
On Tue, Aug 11, 2009 at 08:56:58AM -0600, Theo de Raadt wrote:
I was trying to set up access point with Realtek RTL8187 wireless
card on 4.5.
After looking into the manpage I thought it has mediaopt hostap
capability,
The following hostname.if(5) example creates a
I bought a new Wireles USB device, using 5-29-2008 amd64 snapshot
That is an awfully old snapshot. You might want to use something from
this year.
Cheers,
Predrag
P.S. Sorry Sam I couldn't resist:-)
On Mon, Jun 1, 2009 at 2:31 AM, Predrag Punosevac punoseva...@gmail.com wrote:
I bought a new Wireles USB device, using 5-29-2008 amd64 snapshot
That is an awfully old snapshot. You might want to use something from
this year.
Cheers,
Predrag
P.S. Sorry Sam I couldn't resist:-)
Sorry that
misc@,
I bought a new Wireles USB device, using 5-29-2008 amd64 snapshot it will not
attach to urtw.
what are the steps I need to take to add the relevant device ID's to
usbdevs, so that the device will attach?
I know I need to recompile a kernel and I am comfortable with that.
I was able to
17 matches
Mail list logo
