The following reply was made to PR kern/149643; it has been noted by GNATS.
From: Adrian Chadd
To: Steven Chamberlain
Cc: freebsd-net@freebsd.org, bug-follo...@freebsd.org
Subject: Re: kern/149643: [rum] device not sending proper beacon frames in ap
mode
Date: Tue, 18 Oct 2011 11:44:59 +0800
On 18 October 2011 11:36, Steven Chamberlain wrote:
> Hi Adrian,
>
> I see that revision 226467 by bz already fixed the compiler warnings.
> I've now built and tested this on freebsd-8 amd64.
Sweet. I'll just assume at this point that it'll work on FreeBSD-9 and
aim to get it into the tree in the
The following reply was made to PR kern/149643; it has been noted by GNATS.
From: Steven Chamberlain
To: Adrian Chadd
Cc: freebsd-net@freebsd.org, bug-follo...@freebsd.org
Subject: Re: kern/149643: [rum] device not sending proper beacon frames in
ap mode
Date: Tue, 18 Oct 2011 04:36:33 +0100
Hi Adrian,
I see that revision 226467 by bz already fixed the compiler warnings.
I've now built and tested this on freebsd-8 amd64.
The same bugfix has been working throughout the day on a couple of
openbsd i386 boxes with rum hardware too.
I guess the PR number you asked me for yesterday is jus
On 17/10/11 14:13, Adrian Chadd wrote:
> I've committed this to -HEAD in r226465.
> I'll MFC this to -9 and -8 in the next 3 or so days, re@ approval pending.
Argh... there were a couple of issues someone pointed out to me off-list
that you may not have seen:
On 17/10/11 01:16, Gang 'Henry' Hu wr
Hi,
I've committed this to -HEAD in r226465.
I'll MFC this to -9 and -8 in the next 3 or so days, re@ approval pending.
Thanks,
adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send
Hi!
Thanks very much for this. I'll make sure it gets into -HEAD.
If someone can test out a patch on -9, I'll submit it as a candidate to re@.
Would you please create a PR and tell me what the PR number is? I'll
then make sure it gets committed.
Thanks again!
adrian
___
Hi,
I'm attaching patches for the rum device driver in freebsd and openbsd
latest CVS.
Firstly I am testing this on a couple of openbsd i386 boxes which should
see some heavy usage tomorrow, but so far it has fixed host AP beacons
during my testing here. This has also helped some devices to conn
On 16/10/11 17:46, Adrian Chadd wrote:
> I don't think it's the mbuf. It looks like the mbuf allocation is fine.
> The linux code in compat-wireless...
Hi Adrian!
Thanks for your suggestions. Happily I've got it working, and it wasn't
nearly that complicated. I'm only using i386 architecture.
I don't think it's the mbuf. It looks like the mbuf allocation is fine.
The linux code in compat-wireless:
* seems to handle endian-ness a bit better;
* does a bunch of different stuff - look at
drivers/net/wireless/rt2x00/rt2500usb.c:
static void rt2500usb_write_beacon(struct queue_entry *entry
Is this plugged into an i386/amd64, or something that isn't little endian?
I just wonder about the endian-ness of that tx/rx descriptor struct..
Adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To uns
Hello again,
I've made another observation regarding this bug. It is possible to
also trigger it in 11b mode if the ESSID is large enough -- up to 11
chars is okay:
> # ifconfig rum0 media DS1 mode 11b mediaopt hostap nwid
> 0xcc
> 15:51:43.053446 00:19:5b:d3:00:56 > ff:ff:
Hi Adrian,
On 16/10/11 02:15, Adrian Chadd wrote:
> Just look at what the mgmtrate is set to? It should be set to 1mbit
> for both 11b and 11g.
I've just managed to test this, but it seems everything was as it should
be. An mgmtrate of 2 is chosen (1Mbit), and I've checked from another
device th
Hi!
Thanks for your diagnosis. I don't have any rum hardware at the moment
(and no time to go diving through the code) but that's an excellent
set of debugging/diagnosis results you have there.
Just look at what the mgmtrate is set to? It should be set to 1mbit
for both 11b and 11g. It shouldn't
The following reply was made to PR kern/149643; it has been noted by GNATS.
From: Steven Chamberlain
To: bug-follo...@freebsd.org, n...@jelal.kn-bremen.de
Cc: henry.hu...@gmail.com
Subject: Re: kern/149643: [rum] device not sending proper beacon frames in
ap mode
Date: Sat, 15 Oct 2011 22:56:55
The following reply was made to PR kern/149643; it has been noted by GNATS.
From: Henry Hu
To: bug-follo...@freebsd.org, n...@jelal.kn-bremen.de
Cc:
Subject: Re: kern/149643: [rum] device not sending proper beacon frames in ap
mode
Date: Sat, 19 Mar 2011 18:17:24 +0800
I have similar issue
Synopsis: [rum] device not sending proper beacon frames in ap mode
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sat Aug 14 13:31:54 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi
17 matches
Mail list logo
