From nobody Fri Jun 14 20:48:18 2024 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W1BFT4bYjz5PV2C for ; Fri, 14 Jun 2024 20:48:29 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W1BFT1gtlz4Wwx; Fri, 14 Jun 2024 20:48:29 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 78D258D4A126; Fri, 14 Jun 2024 20:48:21 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id A43AF2D029D8; Fri, 14 Jun 2024 20:48:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id eHqV0JyapZgH; Fri, 14 Jun 2024 20:48:19 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 996212D029D2; Fri, 14 Jun 2024 20:48:19 +0000 (UTC) Date: Fri, 14 Jun 2024 20:48:18 +0000 (UTC) From: "Bjoern A. Zeeb" To: Shawn Webb cc: freebsd-wireless@freebsd.org, obiwac@freebsd.org Subject: Re: Suggestions for a wireless chipset for 802.11s and/or hostap mode In-Reply-To: Message-ID: <5noq724s-nqn5-rr29-943o-n0s2o7693q5p@yvfgf.mnoonqbm.arg> References: <72o5o66r-8n82-8318-5rp7-8q7n9r6nnn3o@yvfgf.mnoonqbm.arg> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE] X-Rspamd-Queue-Id: 4W1BFT1gtlz4Wwx On Fri, 14 Jun 2024, Shawn Webb wrote: > Hey Bjoern, > > Thank you for taking the time to respond! > > On Fri, Jun 14, 2024 at 08:31:10PM +0000, Bjoern A. Zeeb wrote: >> On Thu, 13 Jun 2024, Shawn Webb wrote: >> >>> On Thu, Jun 13, 2024 at 11:21:22PM +0000, Shawn Webb wrote: >>>> Hey all, >>>> >>>> Given either an m.2 or mPCIe interface, what would be my best option >>>> for a wireless network adapter that, at a minimum, supports hostap >>>> mode? Hoping for 802.11n or 802.11ac for hostap mode. >> >> 11n the options are documented for the drivers and nothing has changed >> in years. Theres a few options to pick from if you want hostap. >> Most of that hardware is a decade old. >> >> 11ac nothing there yet. >> >>>> I know mesh networking isn't supported (yet) on FreeBSD. I'm hoping >> >> Sorry, but mesh is in FreeBSD (or at least a state of it) and has been >> for ages. People used to use it on research in the past. >> I believe it is even compiled in by default these days: >> >> % grep -r MESH sys/*/conf/* >> sys/amd64/conf/GENERIC:options IEEE80211_SUPPORT_MESH # enable 802.11s draft support >> sys/i386/conf/GENERIC:options IEEE80211_SUPPORT_MESH # enable 802.11s draft support >> sys/powerpc/conf/GENERIC:options IEEE80211_SUPPORT_MESH >> sys/powerpc/conf/GENERIC64:options IEEE80211_SUPPORT_MESH # enable 802.11s draft support >> sys/powerpc/conf/GENERIC64LE:options IEEE80211_SUPPORT_MESH # enable 802.11s draft support > > Back in 2018, 802.11s support wasn't functionally complete. No bit of our wireless implementation is or ever will be. > I had > tried to set up a mesh network with multiple PC-Engines devices, each > using an ath(4) card. What you do not mention, did it work or did you not manage to get anything working? > Consulting the resident wifi guru back then, > Adrian Chadd, I learned that the wireless mesh implementation still > had a long ways to go before it could be used in production. > > Has something changed since then? What he said then. No. > I have a couple PC-Engines devices with ath(4) cards gathering dust. > Perhaps I'll try a test deployment of 802.11s and report back. > > Thanks, > > -- Bjoern A. Zeeb r15:7