Netdev List
 help / color / mirror / Atom feed
From: Pekka Savola <pekkas@netcore.fi>
To: netdev@vger.kernel.org, radvd-announce-l@litech.org
Cc: radvd-devel-l@litech.org
Subject: radvd 1.1 released
Date: Mon, 4 Feb 2008 08:55:12 +0200 (EET)	[thread overview]
Message-ID: <alpine.LRH.1.00.0802040849370.19987@netcore.fi> (raw)

Hi,

A new version of radvd has been released.  There have been a couple of 
new features.

Interfaces must now be RUNNING, not just UP, to be considered by 
default radvd configuration.  This is because nowadays kernels no 
longer generate v6 link-local addresses if the interface is just UP, 
in contrast to e.g., what earlier kernels did.

I'd like issue special thanks to Jim Paris for all the patches he has 
sent :-).

Get it at: http://www.litech.org/radvd/

Changes since 1.0:
     *  Implement privilege separation on Linux: a master root process 
(which is able to reconfigure interfaces) and the main process. There 
is '-s' toggle to keep old behaviour.
     * Fix Linux retrans_timer on old kernels (newer ones have 
retrans_timer_ms)
     * Fix stderr+syslog (default) logging on non-i386 platforms.
     * Require that interface must be RUNNING instead of just UP. Note: 
this could break deployments with very old kernels.
     * Implement automatic interface address advertising with special 
prefix ::/64.
     * Relax interface naming (e.g. with VLANs) requirements.
     * Fix ordering of route, prefix and RDNSS options (only matters 
with RDNSS)

--
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

                 reply	other threads:[~2008-02-04  7:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.1.00.0802040849370.19987@netcore.fi \
    --to=pekkas@netcore.fi \
    --cc=netdev@vger.kernel.org \
    --cc=radvd-announce-l@litech.org \
    --cc=radvd-devel-l@litech.org \
    /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