From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] rpi4 wifi USB dongle
Date: Thu, 22 Apr 2021 23:38:14 -0700 [thread overview]
Message-ID: <048BB57D207AA5342CD1569D2C8F4F79@smtp.pobox.com> (raw)
In-Reply-To: <7AD97663-4C69-49C0-9515-FC1DFB4567E7@me.com>
Quoth Daniel Morandini <danielmorandini@me.com>:
> > 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.
next prev parent reply other threads:[~2021-04-23 6:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 11:10 Daniel Morandini
2021-03-03 11:42 ` kemal
2021-03-03 12:17 ` hiro
2021-03-03 14:07 ` Daniel Morandini
2021-03-03 14:43 ` Stanley Lieber
2021-03-03 14:55 ` hiro
2021-03-03 16:56 ` Julien Blanchard
2021-03-03 17:19 ` hiro
2021-03-04 8:57 ` Daniel Morandini
2021-03-04 10:09 ` hiro
2021-03-04 10:14 ` hiro
2021-03-04 10:40 ` Daniel Morandini
2021-03-04 11:04 ` hiro
2021-03-04 11:21 ` Daniel Morandini
2021-04-23 6:38 ` unobe [this message]
2021-04-23 8:26 ` hiro
2021-04-23 16:50 ` unobe
2021-03-04 12:22 ` Noam Preil
2021-03-04 13:18 ` hiro
2021-03-04 13:43 ` Noam Preil
2021-03-03 17:21 ` Kurt H Maier
2021-03-05 18:25 ` tony
2021-03-03 16:05 ` fulton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=048BB57D207AA5342CD1569D2C8F4F79@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).