On Saturday 01 December 2012 05:59:22 Eitan Adler wrote:
> On 30 November 2012 20:28, Adrian Chadd wrote:
> > It's not that simple. Speak to bernhard.
>
>
> Davide, You mention some issues and I asked you to follow up to the
> PR. Can you please explain them?
>
> > There are other issues that
On Thursday, February 21, 2013 02:29:20 PM Dominik Wille wrote:
> wlan0: flags=8843 metric 0 mtu 1500
> ether 00:21:5c:02:eb:f7
> inet 192.168.178.76 netmask 0xff00 broadcast 192.168.178.255
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode
The patch effectively reverts a previous change, which was to cap rxmax and
density by what the AP is capable of. I think the better approach would be to
initialize rxmax and density with the VAP capabilities before the condition
and use MIN() in STA mode to limit to AP caps.
--
Bernhard
_
On Friday, February 22, 2013 07:04:39 PM Adrian Chadd wrote:
> Hm, we need to use MIN(rxmax) and MAX(density) regardless, right?
>
> If an AP is transmitting to a STA that has a lower rxmax or higher
> density, it should obey that.
>
> The same rules apply for mesh, ibss, tdma operational modes.
On Friday, February 22, 2013 07:34:30 PM Adrian Chadd wrote:
> Hi,
>
> Why isn't it a per-node thing for the AP case?
>
> Ie, what should the AP do if the ampdu density it supports is 0 but
> the STA AMPDU density on the RX side is 8?
What made you think it isn't? ni_htparams is per-node(ni)?
I
On Friday, February 22, 2013 07:52:47 PM Adrian Chadd wrote:
> Hm, it's possible in my sleep deprived state that I'm on the right but
> wrong track here.
>
> The OP problem is that we're not advertising the right capabilities
> when we associate, right?
Correct.
> Why aren't we just advertising
On Fri, Nov 1, 2013 at 7:40 PM, clutton wrote:
> On Wed, 2013-10-23 at 21:43 -0700, Adrian Chadd wrote:
>> IT's not. It's devd doing something dumb.
>>
>>
>> -a
>>
>>
>> On 23 October 2013 21:30, clutton wrote:
>>
>> > Indeed.
>> >
>> > I have looked at a sys/net80211 and at a sys/dev/ath.
>> > B
On Sat, Nov 2, 2013 at 10:00 AM, clutton wrote:
> On Fri, 2013-11-01 at 23:50 -0700, Adrian Chadd wrote:
>> OK, so where's the other path for invoking wpa_supplicant?
>
> What do you mean?
kldload if_ath if will create ath0 which is a INET interface which
will invoke pccard_ether, which will conf
On Tue, Nov 5, 2013 at 5:54 PM, John Baldwin wrote:
> On Sunday, November 03, 2013 12:56:08 pm Adrian Chadd wrote:
>> On 2 November 2013 12:13, clutton wrote:
>>
>> [snip]
>>
>> > What was happened? netif tries to setup wlan0 (clone, wpa, dhcp, etc),
>> > when wlan0 interface occurs, devd runs an
