Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Chris Lawrence <lordsutch@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dnsmasq ipv6 stuff
Date: Tue, 22 Jan 2013 19:14:17 -0500	[thread overview]
Message-ID: <CANJCZGJiCzaB6KDwv1GD+guSkpqy0KrFtUWaAmt56m-LkNyRAg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4rQ5JqW9B+QkCxr98kxAW7g7yTvd-9qFPbRM4iTnt6bQ@mail.gmail.com>

On Tue, Jan 22, 2013 at 6:12 PM, Dave Taht <dave.taht@gmail.com> wrote:
> My own objection to ::1 is that provides both an easy mneumonic for people
> to manage their networks AND an easier vector for attacks from the outside
> world.
>
> J.random.badscript only has to ping ::1 on every subnet in your delegation
> to try and hit all the routers.

True, although I think that's pretty much unavoidable given the design
of ipv6 though (isn't ::1 always the router for the subnet)?  You
could always honeypot or Turing pit the other 2^16-(n) subnets if
you're really paranoid about someone finding your router without a
valid IPv6 address to start guessing with.

The source code also seems to support using
dhcp-range=::,constructor=*,ra-names,ra-stateless (etc.).  I'm not
sure what dropping the "1" does, exactly, not having perfect ipv6-foo
skills yet.


Chris

  reply	other threads:[~2013-01-23  0:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  6:40 Dave Taht
2013-01-22 18:52 ` Chris Lawrence
2013-01-22 22:19   ` Maciej Soltysiak
2013-01-22 23:12   ` Dave Taht
2013-01-23  0:14     ` Chris Lawrence [this message]
2013-01-23  7:24       ` Phil Pennock
2013-01-25 19:21   ` Török Edwin
     [not found] <mailman.5741.1358880757.1742.cerowrt-devel@lists.bufferbloat.net>
2013-01-25  1:47 ` Richard Brown
     [not found] ` <FC4C3393-3EA4-4130-915E-373FAA458A32@intermapper.com>
2013-01-25  1:55   ` Richard Brown
2013-01-30 21:40 Simon Kelley
2013-01-30 23:44 ` Chris Lawrence

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=CANJCZGJiCzaB6KDwv1GD+guSkpqy0KrFtUWaAmt56m-LkNyRAg@mail.gmail.com \
    --to=lordsutch@gmail.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