Cannot initialize Compex WLE600VX for 802.11ac?

[Tom Marble]

Michal Kazior <michal.kazior at tieto.com> writes:
> On 24 June 2016 at 05:27, Tom Marble <tmarble at info9.net> wrote:
>> The solution here was just removing avahi-daemon (and mDNS services).
>>
>> Then the interface wasn't happy about IPv6
>>   IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not read
>
> This is normal. Try down/up your ethernet interface and you'll see the
> same thing.

Ok.

>> Even with setting (in /etc/hostapd/wlan0.conf ) this problem still occurred.
>>   ipaddr_type_availability=32
>>
>> The solution was disabling IPv6 (at least for now.. I do want IPv6
>> eventually), in /etc/sysctl.conf
>> # NO IPV6                                                                        net.ipv6.conf.all.disable_ipv6 = 1
>> net.ipv6.conf.default.disable_ipv6 = 1
>> net.ipv6.conf.lo.disable_ipv6 = 1
>> net.ipv6.conf.eth0.disable_ipv6 = 1
>> net.ipv6.conf.wan0.disable_ipv6 = 1
>
> Do you really need to disable ipv6?

No.. I *want* IPv6! I'm going to try adding it back in now
to see if I can get it to work.

>> Certain clients seemed to get "kicked off" the network which has
>> been mitigated by setting:
>>   ap_max_inactivity=600
>>   disassoc_low_ack=0
>
> Try using disassoc_low_ack=1 which enables station inactivity
> detection up to firmware/driver (there are some bugs with sending
> nullfunc frames depending on fw/hw/driver combo).

I'll try that!

>> One strange thing I've noticed is that if I configure the wlan0 (5 GHz)
>> channel=52 on boot up it doesn't work... However if I have once
>> done channel=0 then on subsequent bounces of the interface I can have
>> it come up on a specific channel.
>
> (haven't followed the entire thread, so sorry if I re-iterate something).
>
> Channel availability can get messy and quirky (unless that has changed
> in recent kernels?) with multiple wireless cards on the same system.
> So there's that.

I realize this can be tricky. My current thought is to bring
up wlan0 (5 GHz) first and then bring up wlan1 (2.4 GHz).

I'll report my findings after my next round of tests.

Thanks!

--Tom