From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 366573CB36 for ; Mon, 30 Sep 2019 11:32:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1569857528; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VMF0N59fnI1J/QvSy2BMq44lceym5lYIGRA1qHQjDH0=; b=SlxMGuHbU1Kjf4N13dH7O2d50hr9UiFGWdDdcn+69xWejDgaAUgUD+eLHBJpaDOtXINVQ8 kCIuv5EAKmORPhD7DMj6aJo0PcOEgokoayJ8sFGB2O2gOrdyDvvoYQP7hHufUSRX98VEbU mOuozp+YWTlWoa9Gv8FKgiR3Nb3xqz0= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-296-NOu-8P4hPNy74Fir_OmUyw-1; Mon, 30 Sep 2019 11:32:03 -0400 Received: by mail-ed1-f71.google.com with SMTP id h12so6555359eda.19 for ; Mon, 30 Sep 2019 08:32:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=VMF0N59fnI1J/QvSy2BMq44lceym5lYIGRA1qHQjDH0=; b=n2daOXS9hAelxHSY3Z+XwQrMQsKTkfkh41XT0ArxmHtOjSPfsVBcMa5gcTqUbI+2+X U7FpPnByr6sP3pECzOHlfj+gUaIjKUdwJaap0p1APObacb7QjbPRgUTDBAbXKohtCxok ZodalOtzExFlb4DPSYfgaDHmXfATtfED9kA/EUGsyR+LeH+Q4fOu22UvSAc4t6LvxMZU P6Y3Koj0hBgRHCzt70msrKnxfavq+oH2hMZjT0HIzkQSVMi9RBuY5S6M6xD06+6RsLZp Nde42DeqFNk1EheMChpzMeRq7BNlESN30XCmBt1k6IE5U7SJdr/zuZt8b5/Ra3vgpn1Z 1gNQ== X-Gm-Message-State: APjAAAXZL0Pb+LfySoP9Xcn8/xgXn6FKMzheOYpQsY7iejp7rOMZaRFL +3VDE9g98WrH6a1HmwUCn8v+k3p0QVoOsPZt+DZ0D8bVtKPFPhx6/Yaen4aWryF76Xr+T0N2CcF NszAaZgworRFhyOn9RQcnhOYe4Wsi6GBnXr0= X-Received: by 2002:a50:935d:: with SMTP id n29mr20368812eda.294.1569857521670; Mon, 30 Sep 2019 08:32:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqwNKNFnN5xyo9L0ffLj8SG0M1P1byiAO02sVjJsVHj/SL3iv5e/xJNOMDK4IzJJDH73ZZpVjA== X-Received: by 2002:a50:935d:: with SMTP id n29mr20368793eda.294.1569857521478; Mon, 30 Sep 2019 08:32:01 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk (borgediget.toke.dk. [85.204.121.218]) by smtp.gmail.com with ESMTPSA id z39sm2507224edd.46.2019.09.30.08.32.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Sep 2019 08:32:00 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 22FF718063D; Mon, 30 Sep 2019 17:32:00 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Rich Brown , make-wifi-fast@lists.bufferbloat.net In-Reply-To: <1C8CA44A-31E8-4EF0-B685-5534CF2F64BE@gmail.com> References: <1C8CA44A-31E8-4EF0-B685-5534CF2F64BE@gmail.com> X-Clacks-Overhead: GNU Terry Pratchett Date: Mon, 30 Sep 2019 17:32:00 +0200 Message-ID: <87wodpx0jz.fsf@toke.dk> MIME-Version: 1.0 X-MC-Unique: NOu-8P4hPNy74Fir_OmUyw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] Best practice: multiple SSIDs on a radio...? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2019 15:32:09 -0000 Rich Brown writes: > Sorry for this somewhat OT question, but I know that I'm tapping into > a mother lode of Wi-Fi knowledge... > > A local coffee shop wants a guest and a private network, supported by > separate SSIDs. Is there a benefit (or would it be bad) to put the > public network on one channel and the other network/SSID on another > channel? You generally can't, at least not in the same band. You could put one on 2.4GHz and the other on 5GHz, but to run multiple SSIDs on the same radio, they generally need to be on the same channel (you can see this by the way the openwrt config splits things into 'phy' and 'device' config sections). -Toke