Tomasz Skapski <[email protected]> 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
signature.asc
Description: PGP signature
_______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
