Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1314588ybt; Thu, 25 Jun 2020 03:08:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz1yUkmwecKNC5qiYrCaVev6456BYRpYJUXBtxd5i40uISqFtCtmPpkYiZRCHntlpUYfkIE X-Received: by 2002:a17:907:20d1:: with SMTP id qq17mr23476082ejb.214.1593079680625; Thu, 25 Jun 2020 03:08:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593079680; cv=none; d=google.com; s=arc-20160816; b=IiF7jkNTjiO+v2Osz5mrG3iOSY+6/jPSIOi7AHZiKygjlNB+mqK5y0VWphc1nSK/yf THvmYVNPZ2jf+xCI2aRNlJ8dr+w52yVxafCKx+SGre9ssKDCx2Q6SNLD3jXjJM++F2KJ NVZHxU4uQt1TQjJWs7l/7Qb/0CYE2p1wb0TopBZfB7Hev1jF7C2FH3NcgiY4zR+KmOPt Zt/MB9SVzdPd3sqJHckvdXsILDy7YW/Nr8oH0VFCYU0ijUYEgMBnCxSBchXCXQulkhQc z4W9lbiC0WDm9TiOvMUSnLemdD+gAbs1bYjBKboxdY3N9/I/xWcwi7/6Jv5IExrf60q5 aVTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=Yx1P/s2z0fobYGswcLQdQXEGGnA5NOC+VLvlioJl5O8=; b=HEXMjcaZJEE7J1iVSeCm+xG6wZno3SglNhJnKn2Q/2BPsOx/kBDFGKn69hdd6cOYQ7 Cx4CxVFEB0dcKY7RicOxbs8N3mQI4Bh1CkxpFwrTyZSjopRxBlN3NDyKrjlEs0YVm2xG T0/1xXkxSFl1uI88e5loABDOkWsthya68WJquv/cRmlDcgKZfHsYxKZNOj165IcurjKL if9+ana+fInOh2YqDKVkJnmNag9S2qpaULyDEPI++S3JozyCERSHWrSPgt5wFVcNxD/b rItGXb+g9CwYYCg9htYYv3irXJwJ7n5O02GSOn4UkA6TV4XDCEij+odeEbWEu0YvWGn5 e3eA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w13si9113630eju.736.2020.06.25.03.07.28; Thu, 25 Jun 2020 03:08:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390262AbgFYJvy (ORCPT + 99 others); Thu, 25 Jun 2020 05:51:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60366 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389744AbgFYJvx (ORCPT ); Thu, 25 Jun 2020 05:51:53 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 77AECC061573 for ; Thu, 25 Jun 2020 02:51:53 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1joOXr-00BnlL-VR; Thu, 25 Jun 2020 11:51:48 +0200 Message-ID: <2a607392179a76f0f6fc3cef2e6e141f25dc0254.camel@sipsolutions.net> Subject: Re: [PATCH] mac80211: Send deauth to STA's upon AP stop From: Johannes Berg To: Shay Bar , Ben Greear Cc: "linux-wireless@vger.kernel.org" Date: Thu, 25 Jun 2020 11:51:47 +0200 In-Reply-To: References: <20200618093609.16514-1-shay.bar@celeno.com> <2a7b33ace030fdeda96e60b2abd6c70a11f426e0.camel@sipsolutions.net> <54236bdd708c53ec2f2a776bb3badcd77c7fecc6.camel@sipsolutions.net> <6da8757ac90a4d34ed1bdc7c84b40aac06c01af9.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.3 (3.36.3-1.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Sun, 2020-06-21 at 10:12 +0000, Shay Bar wrote: > Hi Johannes and Ben, > > To conclude this thread, hostapd doesn’t send any deauth/disassoc > upon AP stop (when hostapd is killed _or_ when "ifconfig down" the > AP interface). Right. I'm sort of suggesting you just shouldn't be doing this, and it doesn't seem like most people actually do, otherwise we'd have seen this issue before? > This is causing a situation where stations keep sending unicast frames > to a down AP interface as it doesn’t know it's gone down. > I tried your suggestion and sent 1 deauth/disassoc as broadcast > (instead of unicast to each STA), but some stations (e.g. Samsung S8) > Ignore this broadcast (while it will not ignore unicast deauth/disassoc). > Although not indicated in the standard, I think it's better to let STA > Know AP gone down by sending this unicast deauth to each STA > (as this patch does). I'm not really sure. That's a _lot_ of frames and potentially quite a long time. In the patch, as written, I'm not even convinced you can be sure that they will all make it out to the air? johannes