From: Rosen Penev <rosenp@gmail.com>
To: davecb@spamcop.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Another comment re FTC and weather radar from /.
Date: Thu, 08 Oct 2015 21:36:29 +0000 [thread overview]
Message-ID: <CAKxU2N_tqXHvk+DE+mZvKV6MHnH=Rk_mOnVRz-JJt4KfqQcKMA@mail.gmail.com> (raw)
In-Reply-To: <5616D005.9080404@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 4280 bytes --]
How does a router that transmits at milliwatts interfere with airport
equipment? This seems like such an isolated case. At the very least would
it not require the routers to be relatively close?
On Thu, Oct 8, 2015, 13:20 David Collier-Brown <davec-b@rogers.com> wrote:
> Anyone who's an American citizen want to write a short to-the-point
> response suggesting that this was vendor error, caused by not using the
> database that linux uses for wi-fi cards?
>
> I want them to have a public "out" from the current scheme of telling the
> vendors to protect their code.
>
> I prefer to give the FCC the option of telling the vendors to stop messing
> up their code, like a regulatory agency would like to be seen doing (;-))
>
> About one page!
>
> --dave
>
>
>
> On 08/10/15 04:11 PM, David Collier-Brown wrote:
>
> From tlkingan at
> http://tech.slashdot.org/comments.pl?sid=8141531&cid=50686561
>
>
> And that's what the FCC really wants The problem the FCC is seeing right
> now is the modified firmware allows access to frequencies that aren't
> allowed to be used for WiFI in the US. This is more than just channels 12
> and 13 on 2.4GHz, but also on the complex 5GHz band.
>
> The FCC has many complaints already from airports and other entities whose
> radar is being interfered with by 5GHz WiFi (the band plan is complex
> enough that channels are "locked out" because they're used by higher
> priority services like radar).
>
> And you really can't blame the open firmware guys either - mostly because
> they don't know any better and they only build one binary that works for
> all devices worldwide. (the available channels on 5GHz vary per country -
> depending on the radar in use).
>
> All the FCC really wants (and they've clarified it in the Notice of
> Proposed Rulemaking) is the steps wifi manufacturers are taking to prevent
> people from loading on firmware that does not comply with FCC regulations -
> i.e., allows transmissions on frequencies they are not allowed to transmit
> on.
>
> It can either take place as hardware (filters blocking out the
> frequencies), or software that cannot be modified by the open firmware
> (e.g., firmware on wifi chip reads a EEPROM or something and locks out
> those frequencies).
>
> The thing it cannot be is rely on "goodwill" or firmware that respects the
> band plan - i.e., you cannot rely on "blessed" open firmware that only uses
> the right frequencies (because anyone can modify it to interfere).
>
> The FCC has all the powers to enforce compliance right now - users of open
> firmware who are caught creating interference with higher priority services
> can already be fined, equipment seized and all that stuff (and that would
> not include just the WiFi router - any WiFi device like PCs can be seized
> if they attach to that network). That's the heavy handed legal approach
> they have. However, they don't want to do that, because most users probably
> don't realize the problem, and the FCC really doesn't want to destroy all
> that stuff. So instead, the FCC is working with manufacturers to fix the
> issue at the source.
>
> The problem lies in the fact that most manufacturers are cheap and will
> not spend a penny more, so instead of locking out the radio from
> interfering, they'll lock out the entire firmware.
>
> The FCC mentions DD-WRT and all that by name because their investigations
> revealed that when they investigate interference, the offending routers run
> that firmware (and which doesn't lock out frequencies that they aren't
> supposed to transmit on).
>
>
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the restdavecb@spamcop.net | -- Mark Twain
>
>
>
> _______________________________________________
> Bloat mailing listBloat@lists.bufferbloat.nethttps://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the restdavecb@spamcop.net | -- Mark Twain
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 6195 bytes --]
next prev parent reply other threads:[~2015-10-08 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 20:11 David Collier-Brown
2015-10-08 20:20 ` David Collier-Brown
2015-10-08 21:36 ` Rosen Penev [this message]
2015-10-08 22:18 ` David Collier-Brown
2015-10-08 22:26 ` David Collier-Brown
2015-10-13 16:09 ` Simon Barber
2015-10-13 17:29 ` Matt Mathis
2015-10-13 18:18 ` Jonathan Morton
2015-10-13 18:19 ` Sebastian Moeller
2015-10-15 19:21 ` [Bloat] The press release is working David Collier-Brown
2015-10-15 19:44 ` Dave Taht
2015-10-18 23:13 ` [Bloat] Another comment re FTC and weather radar from / Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKxU2N_tqXHvk+DE+mZvKV6MHnH=Rk_mOnVRz-JJt4KfqQcKMA@mail.gmail.com' \
--to=rosenp@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.net \
/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