From: Michael Richardson <mcr@sandelman.ca>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] RE : Save WiFi from the FCC - DEADLINE is in 3 days *September* 8
Date: Tue, 08 Sep 2015 10:45:06 -0400 [thread overview]
Message-ID: <26692.1441723506@sandelman.ca> (raw)
In-Reply-To: <alpine.DEB.2.02.1509081045590.8750@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> So I think a constructive approach would be to try to say how the FCC
> concern can be solved or at least mitigated in a FOSS world. Do we have
> any ideas?
The FCC needs to think bigger: restricting who can make/design/update
(fundamentally: 'own') wifi devices leads to millions of compromised devices
attacking the Internet.
If you think of the wifi spectrum as a small component of a bigger "Internet"
spectrum, and that FCC really cares about all of it, then it makes no sense
to manage each part in isolation.
Or to put it differently: if company X's locked down wifi device is attacking
the Internet, then maybe their wifi license should be revoked.
> Because I can understand that regulators whose job it is to make sure
> devices follow the rules have a problem with FOSS code that lets people
> do whatever they want.
Manufacturer devices that have security holes in them let black hats do
whatever they want with the device.
> Do we really want for regulators to bring back the vans who might roll
> around and impose a fine because you were running OpenWRT and happened
> to set the output power too high for whatever local regulation was in
> place?
Yes, actually, I do.
I'm starting to be convinced that the Bell FIBE "wireless TV" eats more than
it's fair share of wifi. I have no way to prove it without that Van.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2015-09-08 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 10:42 [Cerowrt-devel] cerowrt.org vs make-wifi-fast Dave Taht
2015-09-05 14:04 ` [Cerowrt-devel] cerowrt.org vs make-wifi-fast/Network Solutions price is high Rich Brown
2015-09-05 14:12 ` [Cerowrt-devel] Save WiFi from the FCC - DEADLINE is in 3 days *September* 8 Rich Brown
2015-09-05 22:05 ` Dave Taht
2015-09-06 9:02 ` [Cerowrt-devel] RE : [Bloat] " luca.muscariello
2015-09-08 7:55 ` Dave Taht
2015-09-08 8:22 ` [Cerowrt-devel] [Bloat] RE : " Mikael Abrahamsson
2015-09-08 8:36 ` Dave Taht
2015-09-08 8:55 ` Mikael Abrahamsson
2015-09-08 9:21 ` Dave Taht
2015-09-08 9:55 ` Mikael Abrahamsson
2015-09-08 14:45 ` Michael Richardson [this message]
2015-09-08 12:13 ` [Cerowrt-devel] RE : [Bloat] " MUSCARIELLO Luca IMT/OLN
2015-09-06 9:57 ` [Cerowrt-devel] " Fred Stratton
2015-09-07 23:12 ` Jonathan Morton
2015-09-08 6:12 ` Rich Brown
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26692.1441723506@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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