Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Chuck Anderson <cra@WPI.EDU>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] dhcpv4 to slaac naming rfc ready to submit
Date: Mon, 17 Feb 2014 18:01:50 -0500	[thread overview]
Message-ID: <20140217230149.GE27322@angus.ind.WPI.EDU> (raw)
In-Reply-To: <20140217101154.GA1958@ens-lyon.fr>

On Mon, Feb 17, 2014 at 11:11:54AM +0100, Baptiste Jonglez wrote:
> On Sat, Feb 15, 2014 at 10:28:10AM -0500, Chuck Anderson wrote:
> > At best, this is a partial solution.  Using a Modified EUI-64 (RFC4291
> > sec 2.5.1) is not very reliable.  Many systems out there, including
> > Windows and recent Linux distributions, do Privacy Addressing by
> > default, so you will never find their SLAAC address by assuming they
> > constructed their address using EUI-64 based on their Link Layer
> > Address.  Also, they may not respond to ICMPv6 echo requests due to
> > firewall settings.
> 
> Privacy extensions define *additional* addresses, while keeping the SLAAC
> addresses.  RFC4941 does not explicitely state so, but it is hinted at in
> Section 2.4, third paragraph.

Well, whatever Windows 7 does, it doesn't provide *ANY* EUI-64 address
at all, so this won't work with the most popular platform out there.

      reply	other threads:[~2014-02-17 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 21:15 Dave Taht
2014-02-14 21:28 ` Simon Kelley
2014-02-14 23:27 ` Toke Høiland-Jørgensen
2014-02-15 15:28 ` Chuck Anderson
2014-02-17 10:11   ` Baptiste Jonglez
2014-02-17 23:01     ` Chuck Anderson [this message]

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=20140217230149.GE27322@angus.ind.WPI.EDU \
    --to=cra@wpi.edu \
    --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