Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Michael Richardson <mcr@sandelman.ca>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy?
Date: Wed, 18 Dec 2013 18:18:59 +0000	[thread overview]
Message-ID: <874n66yqcs.fsf@toke.dk> (raw)
In-Reply-To: <18235.1387385681@sandelman.ca> (Michael Richardson's message of "Wed, 18 Dec 2013 11:54:41 -0500")

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

Michael Richardson <mcr@sandelman.ca> writes:

> As for having identical ESSID on the same layer-2... I think that
> perhaps cerowrt/openwrt/homenet should consider a wireless AP
> discovery attribute in the routing protocol, and given that, run GRE
> over IPv6 ULA between APs.

I was thinking something like that would be neat. I seem to recall that
the homenet effort at IETF is in the process of specifying standard(s)
for how multiple routes that get plugged into each other in random
fashions should auto-configure themselves. In the meantime, perhaps a
poor-mans version could be to have cero check, when the wan interface
comes up, whether the upstream router is also running cero, and if so
setup the appropriate GRE tunnels and, basically, turn off all other
functionality.

Some sort of negotiation would be needed, but a lua script running in
the (upstream) web configuration (or even an inetd-powered pipe to a
shell script) could work I guess. This could be authenticated by a
shared secret (which the cero firmware would ship with), to prevent the
most obvious abuse.

Any reason why the above wouldn't work?

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-12-18 18:18 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 [this message]
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

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=874n66yqcs.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    /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