Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Phil Pennock <cerowrt-devel+phil@spodhuis.org>
To: Chris Lawrence <lordsutch@gmail.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dnsmasq ipv6 stuff
Date: Wed, 23 Jan 2013 02:24:18 -0500	[thread overview]
Message-ID: <20130123072418.GA65889@redoubt.spodhuis.org> (raw)
In-Reply-To: <CANJCZGJiCzaB6KDwv1GD+guSkpqy0KrFtUWaAmt56m-LkNyRAg@mail.gmail.com>

On 2013-01-22 at 19:14 -0500, Chris Lawrence wrote:
> True, although I think that's pretty much unavoidable given the design
> of ipv6 though (isn't ::1 always the router for the subnet)?

No, the router can have any IP within that subnet, but it will also join
various multicast groups.

Link-local multicast is ff02:: and the ::2 address is "all routers", so
given "se00" as a network device name:

 ping6 ff02::2%se00

should elicit a response from every device on the LAN connected to
CeroWRT's first LAN interface, where the device thinks that it's a
router.

Within the multicast assignments (ff0X::) ::1 is all nodes, so

 ping6 ff02::1%se00

gets a response from every machine which has IPv6 configured up,
assuming no packet filters.

This is defined for ff0X for X with 1, 2 and 5 (interface-local (ie,
this machine), link-local and site-local).  Fortunately, IPv6 doesn't
define this for the global scope, ff0e::, otherwise there would be a
teensy amplification factor for a response to a spoofed ICMP source
address sending a ping to ff0e::1.

For CeroWRT and debugging, the other interesting address in ff02:: (so
you need the %device scoping control on the address) is ff02::1:2 for
All_DHCP_Relay_Agents_and_Servers.

-Phil

  reply	other threads:[~2013-01-23  7:24 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
2013-01-23  7:24       ` Phil Pennock [this message]
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=20130123072418.GA65889@redoubt.spodhuis.org \
    --to=cerowrt-devel+phil@spodhuis.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=lordsutch@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