From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] rpi4 wifi USB dongle
Date: Fri, 23 Apr 2021 09:50:43 -0700 [thread overview]
Message-ID: <52FF8FCFDD0F56AB8692024C94BD53F6@smtp.pobox.com> (raw)
In-Reply-To: <CAFSF3XNPZ3cpdS5DxOox-hs-UcFGYYj9xT6BOhxPrFUA_zRVcg@mail.gmail.com>
Quoth hiro <23hiro@gmail.com>:
> yeah, sadly that doesn't go into depth at all.
>
> proxy arp is not general enough to solve the real problem with wifi
> (e.g. for ipv6 or dhcp).
> the problem with wifi is that it cannot be bridged in the traditional
> (as per ethernet spec) way.
> and we already have mat damon as a solution on 9front. you have quoted
> the summary of the explanation above already, if you check mat damon
> there's more details if you're curious, or you just ask and you'll get
> even more details about this horror.
>
> tap devices are incidental side-effect of how qemu/kvm works on
> unix/linux, has nothing to do with this problem.
Thanks for giving me more details, hiro.
I probably missed the reference where to find mat damon outside of the
silver screen, so took a little digging to find it. In case anyone else
wants to see the code, it's @ /sys/src/9/port/wifi.c:/^dmatproxy .
cpu% lookman 'matt? damon'
cpu% cd /sys/man
cpu% walk -f | xargs grep -i 'matt? damon'
cpu% cd /sys/src
cpu% g 'matt? damon'
cpu% cd /n/extra
cpu% grep 'matt? damon' INDEX
cpu%
I googled and saw @ http://ninetimes.cat-v.org/news/2018/02/02/0/:
wifi: matt damon wifi bridging support
which then led me to look more closely at port/wifi.c .
next prev parent reply other threads:[~2021-04-23 17:01 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
2021-04-23 8:26 ` hiro
2021-04-23 16:50 ` unobe [this message]
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=52FF8FCFDD0F56AB8692024C94BD53F6@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).