ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Marble <tmarble@info9.net>
To: Tomasz Skapski <tomasz.skapski@tieto.com>
Cc: Tom Marble <tmarble@info9.net>,
	"Valo, Kalle" <kvalo@qca.qualcomm.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Cannot initialize Compex WLE600VX for 802.11ac?
Date: Thu, 23 Jun 2016 22:27:20 -0500	[thread overview]
Message-ID: <57dfus3l10n.fsf@cerise.info9.net> (raw)
In-Reply-To: <CABkMH_rZNhxHtfaD3pz0ymSjvEKGxDycjDcwxKBZFKj8j2P_Jg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3138 bytes --]

Tomasz Skapski <tomasz.skapski@tieto.com> writes:
> In your config file set 'fragm_threshold=-1', or comment it.

Indeed this was the last critical configuration change...
Now I'm able to bring up the interface!

Then I was getting errors when 'ifup'-ing the interface
  RTNETLINK answers: File exists
which were resolved by ensuring that
1. The interface was flushed prior to being up'ed
   ip addr flush dev wlan0
2. The interface was *not* configured to add an (additional) gateway

Following this the interface would not stay up due to avahi-daemon
decideding it didn't like something and removing the address
  avahi-daemon[2925]: Withdrawing address record for 10.6.8.1 on wlan0.

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

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

I also rebuilt hostapd because it seems to have a version locked
dependency of libssl (for some reason?).

With the addition of dnsmasq (for DHCP and DNS proxying) and
simple nftables rules for nat/masquerade I now have a functioning AP!

Certain clients seemed to get "kicked off" the network which has
been mitigated by setting:
  ap_max_inactivity=600
  disassoc_low_ack=0

One problem that results in clients getting removed from the AP is:
Jun 23 19:07:28 six kernel: [  995.006727] wlan0: dropped frame to 00:01:02:03:37:15 (unauthorized port)

... and I'm not sure what's causing that?

Amusingly certain Android clients seem to constantly "fishing" to find
active networks (these messages occur every 15 seconds):
Jun 23 21:26:23 six kernel: [ 9330.082522] wlan1: STA 00:01:02:03:37:15 aid 1 enters power save mode
Jun 23 21:26:38 six kernel: [ 9345.059365] wlan1: STA 00:01:02:03:37:15 aid 1 exits power save mode
Jun 23 21:26:38 six kernel: [ 9345.059408] wlan1: STA 00:01:02:03:37:15 aid 1 sending 0 filtered/0 PS frames since STA \
not sleeping anymore
Jun 23 21:26:39 six kernel: [ 9345.364866] wlan1: STA 00:01:02:03:37:15 aid 1 enters power save mode

In other good news I added a second nic (wlan1) to handle 2.4 GHz
traffic in the form of a TP-LINK TL-WN722N which is supported by
the driver ath9k_htc. Using a separate instance of hostapd for wlan1
I now have a dual mode access point!

I found I had to move the TL-WN722N antenna as far away as possible
to minimize interference with the 5 GHz signal.

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.

Thanks Tomasz and Kalle for your help!!!

--Tom



[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2016-06-24  3:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 14:42 Cannot initialize Compex WLE600VX for 802.11ac? Tom Marble
2016-06-22  6:47 ` Valo, Kalle
2016-06-22 13:10   ` Tom Marble
2016-06-22 14:08     ` Valo, Kalle
2016-06-23 13:00       ` Tom Marble
2016-06-23 13:27         ` Tomasz Skapski
2016-06-24  3:27           ` Tom Marble [this message]
2016-06-27 11:52             ` Michal Kazior
2016-06-27 12:42               ` Tom Marble

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57dfus3l10n.fsf@cerise.info9.net \
    --to=tmarble@info9.net \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=tomasz.skapski@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox