From owner-freebsd-net@freebsd.org Sat Jun 20 10:06:47 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0D9C434CCF2 for ; Sat, 20 Jun 2020 10:06:47 +0000 (UTC) (envelope-from darcy@druid.net) Received: from mail.vex.net (mail.vex.net [IPv6:2605:2600:1001::44]) by mx1.freebsd.org (Postfix) with ESMTP id 49prtZ0Sn1z3VRk for ; Sat, 20 Jun 2020 10:06:45 +0000 (UTC) (envelope-from darcy@druid.net) Received: from dilbert.druid.net (unknown [216.105.80.22]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: darcy) by mail.vex.net (Postfix) with ESMTPSA id 6AE447D732; Sat, 20 Jun 2020 06:06:39 -0400 (EDT) Subject: Re: WiFi hotspot keeps dropping To: Adrian Chadd Cc: FreeBSD Net References: <07f4e7f5-095e-e89e-2c55-d283ca62149c@druid.net> From: D'Arcy Cain Autocrypt: addr=darcy@druid.net; prefer-encrypt=mutual; keydata= mDMEXno+ARYJKwYBBAHaRw8BAQdAR2o17zm/M442SONWLjdQ/8Jpro8TbnUm/m1r4MHhygS0 HUQnQXJjeSBDYWluIDxkYXJjeUBkcnVpZC5uZXQ+iJYEExYIAD4WIQQZ0YBgv7psnnP4U/Hh AAd6d7lwwgUCXno+AQIbAwUJCWYBgAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRDhAAd6 d7lwwvvTAQCfxQvyB5M06arZ2cL4LDj0wVxG9ay0PTR+qrQQ9DhevAD+I7W9XlbX6qL3gfDe A0wmuPKWrdSRWEcagXI1sGSC3Ay4OAReej4BEgorBgEEAZdVAQUBAQdAbPzu0iryH2ph9hjN L+Cu1Wo85QbDLV174RHCnjmD5WMDAQgHiH4EGBYIACYWIQQZ0YBgv7psnnP4U/HhAAd6d7lw wgUCXno+AQIbDAUJCWYBgAAKCRDhAAd6d7lwwhb/AQD/8Vd7zTK1s3g4bFCApa3W4zSqUa3/ 9trMr0wfaEOngAEA8iWgHnExoVEdLo9542+dJ8K0L7ntWdfIZLgCXK/2OQ8= Message-ID: <742710a7-7af0-6edb-d594-55d04f357bfc@druid.net> Date: Sat, 20 Jun 2020 06:06:38 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GsjfEOYsWMVpGJng7KaKBuTMUZGr0SLtL" X-Rspamd-Queue-Id: 49prtZ0Sn1z3VRk X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of darcy@druid.net has no SPF policy when checking 2605:2600:1001::44) smtp.mailfrom=darcy@druid.net X-Spamd-Result: default: False [-0.56 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_NA(0.00)[no SPF record]; NEURAL_SPAM_SHORT(0.24)[0.243]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[druid.net]; HAS_ATTACHMENT(0.00)[]; NEURAL_SPAM_MEDIUM(0.24)[0.238]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.06)[0.058]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; ASN(0.00)[asn:19842, ipnet:2605:2600::/32, country:CA]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jun 2020 10:06:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GsjfEOYsWMVpGJng7KaKBuTMUZGr0SLtL Content-Type: multipart/mixed; boundary="AsO5oMFulJynnjUuEuqVWw4KJudCIIBau" --AsO5oMFulJynnjUuEuqVWw4KJudCIIBau Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2020-06-19 12:13, Adrian Chadd wrote: > If I can't keep it running can someone suggest a system test I can = do to > decide that hostapd needs to be restarted? >=20 > So, you shouldn't need to restart hostapd after a stuck beacon. It > should recover. That was my understanding. > One thing I found was lots of log entries like this: >=20 > ath0: stuck beacon; resetting (bmiss count 4) >=20 > So there's plenty of reasons for a stuck beacon. I've mostly fixed the > programming problems and now it's typically really busy air.=C2=A0 > > From reading up on that it seems that it is just a cosmetic warning= =2E > Could this be an indication of something that is killing the hotspo= t? > > It's possible but it shouldn't be killing the interface. >=20 > What you could try is forcing a full reset every time the NIC needs to > reset. >=20 > sysctl dev.ath.0.hal.force_full_reset=3D1 I have done this. It still happened. Note that hostapd is still running when I restart it. > What I suggest you do is recompile your kernel/modules with the > following options: >=20 > IEEE80211_DEBUG > ATH_DEBUG > AH_DEBUG > ATH_DIAGAPI >=20 > Then you'll get access to a lot more debugging tools (ie, the stuff in > tools/tools/ath/) which we can use to diagnose what's going on. I like to run a generic kernel and use loadable modules so I don't compile my own kernel yet. I will try that if I can't fix it any other w= ay. --=20 D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@VybeNetworks.com, VoIP: sip:darcy@druid.net --AsO5oMFulJynnjUuEuqVWw4KJudCIIBau-- --GsjfEOYsWMVpGJng7KaKBuTMUZGr0SLtL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQZ0YBgv7psnnP4U/HhAAd6d7lwwgUCXu3frgAKCRDhAAd6d7lw wpoxAP9+x5waDJScmCdQB6JRBL3ya4Dgv2Xq8s+KR0lfC/kgfAEA1Y5lcwg5Xnqo XEhbYrm4zvUz4xXZZbHtaf1LEsAxbQg= =00XV -----END PGP SIGNATURE----- --GsjfEOYsWMVpGJng7KaKBuTMUZGr0SLtL--