From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy?
Date: Sat, 28 Dec 2013 00:56:58 +0100 [thread overview]
Message-ID: <CAMZR1YBFa+RMpztDtDDo1fbgoDKH0grxnr8NyHJZ4CmxYKHSvw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7wRuadsrU0MXJt5FspyYTV1ZPuOv=7DMojTWssXG_Sog@mail.gmail.com>
I'm not too keen on the -legacy thing, because it's not language agnostic.
However it seems to be a trend. At 30c3 they do exactly that:
https://twitter.com/arambartholl/statuses/416612652539191296/photo/1/large
Best regards,
Maciej
On Mon, Dec 16, 2013 at 8:46 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I have long used "5" as an indicator that the 5ghz channel was better.
> This goes back to a long thread on nanog, like 4? 5? years ago, where
> the hope was to train users that "5" was better.
>
> Well, it's turned out that 5 is frequently better, but not always, AND
> that clients tend to go for the shortest of the SSIDs available. So a
> thought would be to create another ad-hoc standard for deprecating 2.4
> ghz, and have the shorter SSID be the 5ghz one.
>
> Ideas for the 2ghz channel:
>
> CEROwrt-legacy
> CEROwrt2
>
> I'm not huge on "legacy" because it's rather long but am stuck for
> standards, I'd like a default 2.4 ghz SSID that clearly indicates the
> real use to which 2.4ghz is suitable, like:
> CEROwrt-GET-OFF-MY-BABY-MONITOR-YOU-FREAK
>
> ideas for another ssid naming standard slightly longer than a single
> digit that would make sense to mom?
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
prev parent reply other threads:[~2013-12-27 23:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 19:46 Dave Taht
2013-12-16 20:19 ` Sebastian Moeller
2013-12-16 20:25 ` Toke Høiland-Jørgensen
2013-12-16 20:48 ` Kelvin Edmison
2013-12-16 21:28 ` David Lang
2013-12-16 22:06 ` Fred Stratton
2013-12-17 17:54 ` Michael Richardson
2013-12-17 18:51 ` Jim Gettys
2013-12-17 22:25 ` dpreed
2013-12-17 22:32 ` Jim Gettys
2013-12-17 23:43 ` Stephen Hemminger
2013-12-18 1:33 ` Theodore Ts'o
2013-12-18 3:04 ` David Lang
2013-12-18 5:05 ` Theodore Ts'o
2013-12-18 5:49 ` David Lang
2013-12-18 14:17 ` Chuck Anderson
2013-12-18 15:19 ` dpreed
2013-12-18 16:54 ` Michael Richardson
2013-12-18 18:18 ` Toke Høiland-Jørgensen
2013-12-18 19:24 ` David Lang
2013-12-18 20:07 ` Michael Richardson
2013-12-18 20:14 ` David Lang
2013-12-19 9:31 ` Toke Høiland-Jørgensen
2013-12-19 14:32 ` Michael Richardson
2013-12-19 20:05 ` David Lang
2013-12-19 21:01 ` Chuck Anderson
2013-12-20 0:50 ` Theodore Ts'o
2013-12-20 5:18 ` dpreed
2013-12-18 14:06 ` Michael Richardson
2013-12-27 23:56 ` Maciej Soltysiak [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/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=CAMZR1YBFa+RMpztDtDDo1fbgoDKH0grxnr8NyHJZ4CmxYKHSvw@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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