Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-12 released
Date: Sat, 22 Mar 2014 19:18:05 +0100	[thread overview]
Message-ID: <87a9cit7vm.fsf@alrua-x1.karlstad.toke.dk> (raw)
In-Reply-To: <CAA93jw74YS+3KXqFTYJcH3Qq5H_Kz0RE=_N2cNb1expLB-ZdLQ@mail.gmail.com> (Dave Taht's message of "Sat, 22 Mar 2014 17:09:38 +0000")

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

Dave Taht <dave.taht@gmail.com> writes:

> Perhaps this is a new logo idea for cero: A giant clue-bat.

That'd be cool. I've always wondered what a clue-bat would actually look
like... :)

> Well, a brute force way would be to insert all these addresses with
> say a one hour timeout to expire on a cold boot.

Yeah, but then you'd have to handle collisions with subnets configured
on the internal interface and all sorts of weird edge cases, I'm sure...

Perhaps some sort of feasibility study on the arping approach could be
conducted? Someone with a cable modem who can check if `arping <addr>`
with its configuration address returns anything when no corresponding
address is configured on the router? Or am I completely off base in
thinking that would work?

> In terms of featureitus it might be nice to have a comment field shown
> in the gui and in the config file.

Right, well if you don't mind restructuring the config file completely
in a non-backwards-compatible way, it would be pretty easy to give it a
section for each subnet, with an associated comment / name field,
and use the same widget as the hostname setup. Would make the config
file significantly more verbose, though, and also harder to read IMO...

-Toke

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

  reply	other threads:[~2014-03-22 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 17:47 Dave Taht
2014-03-21 18:51 ` Toke Høiland-Jørgensen
2014-03-21 22:00 ` Sebastian Moeller
2014-03-21 22:53   ` Toke Høiland-Jørgensen
2014-03-21 23:04     ` Sebastian Moeller
2014-03-21 23:26       ` Toke Høiland-Jørgensen
     [not found]         ` <608F3E46-3D81-48A3-B60C-E90661DD3AB2@gmx.de>
2014-03-22 11:08           ` Toke Høiland-Jørgensen
2014-03-22 17:09             ` Dave Taht
2014-03-22 18:18               ` Toke Høiland-Jørgensen [this message]
2014-03-22 20:20               ` Sebastian Moeller
2014-03-22 19:23             ` Sebastian Moeller
2014-03-22 19:36               ` Toke Høiland-Jørgensen
2014-03-22 20:24                 ` Sebastian Moeller
2014-03-24  0:56 ` Valdis.Kletnieks
2014-03-24 14:35   ` Jim Reisert AD1C
2014-03-26  4:37     ` Kai Yang
2014-03-24 16:32 ` [Cerowrt-devel] upnp oddness (was " Valdis.Kletnieks

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=87a9cit7vm.fsf@alrua-x1.karlstad.toke.dk \
    --to=toke@toke.dk \
    --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