From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #6: Tools For Fighting WiFi Inequality
Date: Mon, 05 Jun 2023 01:04:03 -0400 [thread overview]
Message-ID: <83CC67F1-547F-48BA-92AF-302D35CB97E2@stanleylieber.com> (raw)
In-Reply-To: <CAFSF3XO2oVKvLkNPLpPkaJwPQ6s9mp4_E4xQ2WWMDipicwkt3g@mail.gmail.com>
On June 4, 2023 3:32:15 PM EDT, hiro <23hiro@gmail.com> wrote:
>so, like a factor 5.
>2.4ghz wifi is useless for me here even with linux/windows/android. i
>live in a higher density area with too much interference from
>neighbors.
>5ghz stuff otoh has much more regular latencies, i.e. less jitter from
>re-transmissions after collisions. probably mainly bec. the
>attenuation in our brick walls is a lot higher for 5ghz (unlike for
>2.4ghz).
>also, there's less other crap l ike bluetooth on the 5ghz band. 2.4ghz
>is way too overcrowded.
>the big big big downside though is that there aren't many usable bands
>in 5ghz that aren't plagued by DFS procedures, also making all but 4
>channels practically unusable in my area. still, for me, 5ghz still
>helps a lot, just it isn't good enough when you don't have nice brick
>walls (i.e. it's great in old european 100 years old houses. but sucks
>in america).
>
>i have high hopes for wifi6E or wifi7 devices with full 6ghz band
>support. i think once there is a driver and hostapd support for this
>on linux/bsd, it will become very much worth the effort to try and
>support it fully.
>6ghz stuff might finally become universally useful internationally.
>
>On 6/4/23, sl@stanleylieber.com <sl@stanleylieber.com> wrote:
>>> what is the tput result for the "300mbps" bridge?
>>
>> x1 yoga 3rd gen w/ ethernet to wifi bridge:
>>
>> ; cat /n/rachael/usr/bin/* | tput
>> 406.34 KB/s
>> 406.86 KB/s
>> 433.90 KB/s
>> 392.23 KB/s
>> 411.39 KB/s
>> 426.37 KB/s
>> 412.73 KB/s
>> 405.03 KB/s
>> 415.13 KB/s
>> 419.22 KB/s
>> 418.93 KB/s
>> 418.68 KB/s
>> 420.32 KB/s
>> 415.44 KB/s
>> 420.81 KB/s
>> 426.01 KB/s
>> 427.78 KB/s
>> 431.57 KB/s
>> 435.38 KB/s
>> 438.81 KB/s
>> 440.77 KB/s
>> 441.46 KB/s
>> 441.40 KB/s
>> 442.68 KB/s
>> 443.21 KB/s
>> 444.32 KB/s
>> 446.82 KB/s
>> 448.58 KB/s
>> 449.94 KB/s
>> 451.21 KB/s
>> 452.39 KB/s
>> 453.76 KB/s
>> 454.07 KB/s
>>
>> thanks, i've added this to the article.
>>
>> sl
>>
>
i get different kinds of transient problems depending on different combinations of factors, but the disparity between mpcie and m.2 cards is pretty consistent. i don't know if the type of pci connection really matters at all, or if it's just a coincidence that these newer cards suddenly perform so much worse precisely when they switched to m.2.
i haven't researched ethernet to wifi bridges methodically. the iogear thing worked well enough that i didn't continue buying new devices. it seems likely there are more options than just 2.4ghz, but this thing is very small and fairly cheap and actually works for my use case.
yes, wifi sucks, but the same hardware us usable for my tasks on other operating systems, but sucks with 9front. this to me suggests that wifi sucking isn't the whole story.
sl
next prev parent reply other threads:[~2023-06-05 5:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 2:51 sl
2023-06-04 13:39 ` hiro
2023-06-04 16:48 ` sl
2023-06-04 19:32 ` hiro
2023-06-05 5:04 ` Stanley Lieber [this message]
2023-06-05 7:56 ` hiro
2023-07-08 2:38 ` sl
2023-07-22 19:53 ` kemal
2023-07-22 21:30 ` kemal
2023-07-22 21:49 ` kemal
2023-07-22 22:22 ` qwx
2023-07-22 22:57 ` Stanley Lieber
2023-07-23 0:24 ` kemal
2023-07-24 2:35 ` ori
2023-07-24 9:58 ` kemal
2023-07-24 11:55 ` kemal
2023-07-24 12:08 ` Steve simon
2023-07-24 12:40 ` kemal
2023-06-10 12:21 ` mkf9
2023-06-10 23:01 ` sl
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=83CC67F1-547F-48BA-92AF-302D35CB97E2@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).