Hi All,
I had a quick quesiton regarding the broadcast rates set by Ralink
rt2860 driver. It seems like the broadcast rates are always set to MCS 0.
Suppose i want to increase the broadcast rates to higher MCS's which
function should i be looking into ?
Thanks
ram
__
On 19 February 2013 05:52, Ramanujan Seshadri wrote:
> Hi All,
>I had a quick quesiton regarding the broadcast rates set by Ralink
> rt2860 driver. It seems like the broadcast rates are always set to MCS 0.
> Suppose i want to increase the broadcast rates to higher MCS's which
> function shoul
Here's my current patch. I've tested it lightly in AP mode.
Adrian
20130218-net80211-tx-lock-3.diff
Description: Binary data
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send
Suppose i'm using an adhoc network, then shouldn't i be able to set the
broadcast rates also ?
Ram
On Tue, Feb 19, 2013 at 10:09 AM, Adrian Chadd wrote:
> On 19 February 2013 05:52, Ramanujan Seshadri
> wrote:
> > Hi All,
> >I had a quick quesiton regarding the broadcast rates set by Ralin
On Tue, Feb 19, 2013 at 4:23 PM, Ramanujan Seshadri
wrote:
> Suppose i'm using an adhoc network, then shouldn't i be able to set the
> broadcast rates also ?
ifconfig wlan0 mcastrate XX
you have:
ucastrate
mcastrate
mgmtrate
>
> Ram
>
> On Tue, Feb 19, 2013 at 10:09 AM, Adrian Chadd wrote:
>
>
On Tue, Feb 19, 2013 at 4:10 PM, Adrian Chadd wrote:
> Here's my current patch. I've tested it lightly in AP mode.
Its identical to 20130216-net80211-tx-lock-2.diff?
>
>
>
> Adrian
--
Monthadar Al Jaberi
___
freebsd-wireless@freebsd.org mailing lis
On 19 February 2013 08:32, Adrian Chadd wrote:
> 0x2003 will make things appear. Just do an active scan (ifconfig wlanX
> scan) to ensure something happens.
Hi,
(Cc'ing the list so people can see the progress of debugging this.)
It looks like this happens:
* a channel change occurs;
* beacons
On 19 February 2013 07:50, Monthadar Al Jaberi wrote:
> On Tue, Feb 19, 2013 at 4:10 PM, Adrian Chadd wrote:
>> Here's my current patch. I've tested it lightly in AP mode.
>
> Its identical to 20130216-net80211-tx-lock-2.diff?
>
Good. That means I haven't accidentally changed anything since the
On Tue, Feb 19, 2013 at 5:49 PM, Adrian Chadd wrote:
> On 19 February 2013 07:50, Monthadar Al Jaberi wrote:
>> On Tue, Feb 19, 2013 at 4:10 PM, Adrian Chadd wrote:
>>> Here's my current patch. I've tested it lightly in AP mode.
>>
>> Its identical to 20130216-net80211-tx-lock-2.diff?
>>
>
> Goo
On 19 February 2013 09:44, Monthadar Al Jaberi wrote:
> I have tested between two meshSTAand run iperf UDP until I get close
> to getting lost packets.
>
> Current FreeBSD (r246983): 17 Mbits/
> Current FreeBSD (r246983) + with your patch: 15 Mbit/s
>
> Good news no panic! But looks like a bit sl
On Tue, Feb 19, 2013 at 7:01 PM, Adrian Chadd wrote:
> On 19 February 2013 09:44, Monthadar Al Jaberi wrote:
>
>> I have tested between two meshSTAand run iperf UDP until I get close
>> to getting lost packets.
>>
>> Current FreeBSD (r246983): 17 Mbits/
>> Current FreeBSD (r246983) + with your pa
11 matches
Mail list logo