From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6975 invoked from network); 23 Apr 2021 06:46:27 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 23 Apr 2021 06:46:27 -0000 Received: from pb-smtp20.pobox.com ([173.228.157.52]) by 1ess; Fri Apr 23 02:38:26 -0400 2021 Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 4B37413FE47 for <9front@9front.org>; Fri, 23 Apr 2021 02:38:19 -0400 (EDT) (envelope-from unobe@cpan.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id :to:subject:date:from:in-reply-to:mime-version:content-type :content-transfer-encoding; s=sasl; bh=R3NzYUt8HF28jD4GLbfzyq6Vg 3PB6GYkboDIdYc/ThA=; b=nkBrE+0ifW/rA5y88WQT/3TrALM2ZqBJvFyVzofVg /27sztWXbBREfnUwb9CU9r6VNoIb/byIv0KKbq1EYjsIMWHAcW39ox41+JFdgYxA Yu7wS5AXYXCnpCoO+RFwePwSjSvBQ9w0UUJpGk/ZWPAMcsdxH3L1fJcYXiSgnjp/ h4= Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 458CE13FE46 for <9front@9front.org>; Fri, 23 Apr 2021 02:38:19 -0400 (EDT) (envelope-from unobe@cpan.org) Received: from peregrin (unknown [47.34.135.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id 7D62E13FE45 for <9front@9front.org>; Fri, 23 Apr 2021 02:38:16 -0400 (EDT) (envelope-from unobe@cpan.org) Message-ID: <048BB57D207AA5342CD1569D2C8F4F79@smtp.pobox.com> To: 9front@9front.org Date: Thu, 22 Apr 2021 23:38:14 -0700 From: unobe@cpan.org In-Reply-To: <7AD97663-4C69-49C0-9515-FC1DFB4567E7@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 7C33521E-A3FE-11EB-9B53-E43E2BB96649-09620299!pb-smtp20.pobox.com List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: converged overflow-preventing WEB2.0 hosting blockchain CSS-scale controller Subject: Re: [9front] rpi4 wifi USB dongle Reply-To: 9front@9front.org Precedence: bulk Quoth Daniel Morandini : > > yeah you got it right. > > > > it's hard to find good terminology that still makes sense in all this. > > > > on ethernet all nodes are the same, addressed by MAC addresses. on > > wifi a station can only use one mac address, so bridges never work on > > wifi stations but only on ap side, of which there can only be one. > Now I see. Thank you very, very much. My reply is dated, but maybe it'll be useful for someone. On June 4 of last year, I had this in my 9front setup notes: """ Over the last couple of days I've been working to get bilbo transitioned from a qemu instance on a macbook pro to a qemu instance running on a kvm-capable computer. I finally got it, but most of the time was spent figuring out how to do bridging on a wireless card. That was non-trivial. The qemu documentation was like a scatterplot and gave little insight into how to do it, and the resources it directed one to were quite dated or didn't work for non-Linux guests. Finally, I struck gold with this comment: https://unix.stackexchange.com/questions/159191/setup-kvm-on-a-wireless-interface-on-a-laptop-machine That worked flawlessly. I also was able to update the kernel from running 9pc to 9pc64. Additionally, the kvm enabling is *well* worth the time I spent working on networking and made me appreciate the simplicity of plan9 even more. """ The idea described at stackexchange is to use a TAP device. My situation was using qemu, so not a native install, but thought I'd mention how it worked if anyone was running a virtualized qemu on an rpi4 (which is terribly slow--I've done it, but go with what you got!). In the setup described above, I just created a small wrapper that did the required bits before starting qemu and after stopping it.