Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@reed.com>
To: Mike O'Dell <mo@ccr.org>,cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 37, Issue 24
Date: Sat, 20 Dec 2014 21:37:41 -0500	[thread overview]
Message-ID: <68a9aec2-9a5e-4cc0-84d1-3fce8ccc0efb@reed.com> (raw)
In-Reply-To: <6764.1419109075@ccr.org>

[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]

Neither 2.4 GHZ nor 5.8 GHz are absorbed more than other bands. That's an old wives tale. The reason for the bands' selection is that they were available at the time. The water absorption peak frequency is 10x higher.

Don't believe what people repeat without checking. The understanding of radio propagation by CS and EE folks is pitiful. Some even seem to think that RF energy travels less far the higher the frequency.

Please don't repeat nonsense.

On Dec 20, 2014, Mike O'Dell <mo@ccr.org> wrote:
>15.9bps/Hz is unlikely to be using simple phase encoding
>
>that sounds more like 64QAM with FEC.
>given the chips available these days for DTV, DBS,
>and even LTE, that kind of processing is available
>off-the-shelf (relatively speaking - compared to
>writing your own DSP code).
>
>keep in mind that the reason the 2.4 and 5.8 ISM bands
>are where they are is specifically because of the ready
>absorption of RF at those frequencies. the propagation
>is *intended* to be problematic. that said, with
>good-enough antennas mounted with sufficient stability
>and sufficient power on the TX end and a good enough
>noise floor on the RX end, one can push a bunch of bits
>pretty far.
>
>Bdale Garbee (of Debian fame) had a 10GHz bent-pipe repeater
>up on the mountain above Colo Spgs for quite some time. X-band
>Gunnplexers were not hard to come by and retune for the
>10GHz ham band. i believe he just FM'ed the Gunnplexer
>with the output of a 10Mbps ethernet chip and ran
>essentially pure Aloha. X-band dishes are relatively
>small and with just a few stations in the area he had fun.
>
>      -mo
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

-- Sent from my Android device with K-@ Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2804 bytes --]

  reply	other threads:[~2014-12-21  2:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1418932802.28010.cerowrt-devel@lists.bufferbloat.net>
2014-12-20 20:57 ` Mike O'Dell
2014-12-21  2:37   ` David P. Reed [this message]
2014-12-21  8:32     ` David Lang
2014-12-21 16:45       ` David P. Reed
2014-12-21 19:20         ` Sebastian Moeller
2014-12-23  2:16           ` dpreed
2014-12-23 16:10             ` dpreed
2014-12-21  8:28   ` David Lang
2014-12-23  4:45 Eric Johansson
2014-12-23 22:15 ` Sebastian Moeller
2014-12-24 22:03   ` Roman Toledo Casabona

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=68a9aec2-9a5e-4cc0-84d1-3fce8ccc0efb@reed.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mo@ccr.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