Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Harshal Chhaya <harshal@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] 224gBPS LIFI
Date: Tue, 18 Jul 2023 09:48:18 -0500	[thread overview]
Message-ID: <CAJ8GFOgmstEQix_yMci9-RNbw9hvN0q0tm9Uj53G+OqavNfGyA@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-M95e5yCaB_PxQccaHHvDr-P0zYRTLBMDmxrr9e5nbXpQ@mail.gmail.com>

The more things change, the more they remain the same. :)

The original 1997 standard included a physical layer that used light.
It never really took off for various reasons - lower data rate, line
of sight etc.
It's fascinating to see an improved version come back 25 years later :)



On Mon, Jul 17, 2023 at 1:55 PM Aaron Wood via Make-wifi-fast
<make-wifi-fast@lists.bufferbloat.net> wrote:
>
> That’s an interesting possibility for industrial use-cases where wifi has been used to get flexibility in retrofit installations without needing to pull a hunch if new wires, but has been plagued by interference from heavy equipment.  Although you would need to keep the emitters and receivers clean in the dirtier environments.
>
> This could also be interesting for (some) p2p links, at least those where the IR signal won’t be too adversely impacted by atmospheric dust, fog, and precipitation…
>
> Would it have worked at your yurt lab, Dave? Didn’t that have a few p2p links through the grounds to connect places together?
>
> On Fri, Jul 14, 2023 at 4:38 AM Dave Taht via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net> wrote:
>>
>> https://www.tomshardware.com/news/li-fi-standard-released
>>
>> --
>> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
> --
> - Sent from my iPhone.
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast

      reply	other threads:[~2023-07-18 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 11:38 Dave Taht
2023-07-17 18:55 ` Aaron Wood
2023-07-18 14:48   ` Harshal Chhaya [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ8GFOgmstEQix_yMci9-RNbw9hvN0q0tm9Uj53G+OqavNfGyA@mail.gmail.com \
    --to=harshal@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=woody77@gmail.com \
    /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