Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] making cerowrt chattier
Date: Tue, 12 Jun 2012 09:10:40 -0400	[thread overview]
Message-ID: <CAA93jw4j+Agsz5hjEpYkTezW1opbVgsMdrdNry2iEypS1J9h+A@mail.gmail.com> (raw)

I am fiddling with ideas towards making the router chattier.

One reason is that some countries, and locations (hotspots) tend to
require that a person agree to the terms of service before using the
service. I happen to dislike intensely how this is usually implemented
(requiring a signin via web browser and having something like a
chilispot intercept DNS and all access) - I'd prefer some automated
system and to allow
basic services (like telephone, etc), automagically just work, and
only intercept browser access if required.

The second reason is that periodically a router needs an update, for
example to address a CVE. I note that versions of cerowrt prior to
3.3.8-1 have a version of bind in them that had a CVE issued against
it that needs to be addressed.

A third reason would be to enable various sorts of other messages to
make it to the user faster/more often.

Now, I've implemented a tiny jabber server in my current builds and am
looking into javascript based chat servers that I could incorporate
into the introductory web page, which could be used for notices of
this sort, and jabber users could also merely subscribe to notices
from the router so that they get chat notices when something is going
wrong - "upgrade needed", "we are under a syn attack", "Earthquake",
"out of memory", etc.  I haven't found a lightweight version of
sendxmpp yet, and have never been fond of centralized chat services in
the first place (the venerable "talk" protocol has no ipv6
implementation, I note) , so perhaps there's a better standard or
system I can use that is more aggressively p2p/distributed? I have
seen chat demonstrated over ccnx, but don't know anything
about the implementation.

ejabberd is NOT lightweight but supports muc and other services.

There is also the possibility of a lightweight email tool or the
winpopup utility for samba.

-- 
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/

             reply	other threads:[~2012-06-12 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 13:10 Dave Taht [this message]
2012-06-12 13:22 ` Mark Constable
2012-06-13  0:52 ` Robert Bradley
2012-06-13  1:41   ` Jim Gettys
2012-06-13  2:22     ` dpreed
2012-06-13  2:28       ` Jim Gettys
2012-06-13  3:09         ` Dave Taht
2012-06-13 19:49           ` dpreed
2012-06-13 19:57             ` Dave Taht

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=CAA93jw4j+Agsz5hjEpYkTezW1opbVgsMdrdNry2iEypS1J9h+A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.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