* Bastian Bittorf [18.07.2012 17:43]:
> hi devs!
>
> yesterday we had a breaktrough debugging b43 in our hackspace
> maschinenraum/m18[1,2]
> at weimar.freifunk.net[3,4] - since a long time our darling wrt54g suffers
> from a
> hanging wifi and bad performance[5], but the workaround is easy: no
On 08/22/2012 11:19 PM, Larry Finger wrote:
> On 08/22/2012 04:05 PM, Hauke Mehrtens wrote:
>> On 08/22/2012 08:45 PM, Larry Finger wrote:
>>> On 08/22/2012 11:21 AM, Hauke Mehrtens wrote:
On 07/18/2012 01:56 PM, Bastian Bittorf wrote:
> hi devs!
>
> yesterday we had a breaktrough
> How do I monitor this particular channel with an other wifi card to
> get
> most of the packages, with aircrack I am unable to set the
> channel?
the simple approach is installing horst on another router
or your pc. ofcourse you get a full dump with wireshark
sniffing on your monitor-interface.
> Do you have any info whether the failure occurs with the change
> from OFDM to
> CCK, or vice versa? I am wondering if the radio needs a dummy
i cannot answer this question - interesting idea.
i like to test your patch, simply do a dummy tx in both cases.
bye, bastian
On 08/22/2012 08:45 PM, Larry Finger wrote:
> On 08/22/2012 11:21 AM, Hauke Mehrtens wrote:
>> On 07/18/2012 01:56 PM, Bastian Bittorf wrote:
>>> hi devs!
>>>
>>> yesterday we had a breaktrough debugging b43 in our hackspace
>>> maschinenraum/m18[1,2]
>>> at weimar.freifunk.net[3,4] - since a long
On 08/22/2012 07:49 PM, Rafał Miłecki wrote:
> 2012/8/22 Hauke Mehrtens :
>> On 07/18/2012 01:56 PM, Bastian Bittorf wrote:
>>> hi devs!
>>>
>>> yesterday we had a breaktrough debugging b43 in our hackspace
>>> maschinenraum/m18[1,2]
>>> at weimar.freifunk.net[3,4] - since a long time our darling
2012/8/22 Hauke Mehrtens :
> On 07/18/2012 01:56 PM, Bastian Bittorf wrote:
>> hi devs!
>>
>> yesterday we had a breaktrough debugging b43 in our hackspace
>> maschinenraum/m18[1,2]
>> at weimar.freifunk.net[3,4] - since a long time our darling wrt54g suffers
>> from a
>> hanging wifi and bad per
On 07/18/2012 01:56 PM, Bastian Bittorf wrote:
> hi devs!
>
> yesterday we had a breaktrough debugging b43 in our hackspace
> maschinenraum/m18[1,2]
> at weimar.freifunk.net[3,4] - since a long time our darling wrt54g suffers
> from a
> hanging wifi and bad performance[5], but the workaround is
On Thu, Aug 16, 2012 at 4:25 PM, Bastian Bittorf wrote:
> > am on a WRT54GS.
> >
> > I tried:
> > iw dev wlan0 set bitrates legacy-2.4 6 9 12 18 24 36 48 54
>
> are you in adhoc or ap-mode?
>
I am in ap mode.
>
> > Should I be making the equivalent "iw set bitrates" on the client
> > machine a
> am on a WRT54GS.
>
> I tried:
> iw dev wlan0 set bitrates legacy-2.4 6 9 12 18 24 36 48 54
are you in adhoc or ap-mode?
> Should I be making the equivalent "iw set bitrates" on the client
> machine as well (I have a laptop connected to the router)?
yes, ofcourse. otherwise it doesnt make sens
Hi,
I was happy to see this post since I've been wanting to move away from
tbe brcm-2.4 build for quite some time.
Unfortunately I have not been able to fix mine using this method. I
am on a WRT54GS.
I tried:
iw dev wlan0 set bitrates legacy-2.4 6 9 12 18 24 36 48 54
It seems to got a little l
> What chip is in your WRT54G?
We tested both:
4318 (Buffalo HP54G) and
4306 (Linksys WRT54GL)
bye, bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> > 1) why does a band change (can be seen through minstrel) is a
> problem?
>
> Because IIRC b43 doesn't support anything other than 2.4GHz at
> all.
8-) sorry, i used the wrong term "band":
(fast) changing between b and g rates are the problem.
you can easily reproduce, when you force this by:
>>
>> 1) why does a band change (can be seen through minstrel) is a problem?
>
> Because IIRC b43 doesn't support anything other than 2.4GHz at all.
It's not a change between 2.4 and 5 GHz.
Wifi stops working if the bitrate changes between 11b (1, 2, 5.5, 11) and 11g
(6, 9, 12, 18, 24, 36, 48,
hi devs!
yesterday we had a breaktrough debugging b43 in our hackspace
maschinenraum/m18[1,2]
at weimar.freifunk.net[3,4] - since a long time our darling wrt54g suffers from
a
hanging wifi and bad performance[5], but the workaround is easy: now it's up to
you to fix the rootcause.
our testsetup
15 matches
Mail list logo
