Commit f66a5ee5 authored by Wlodzimierz Wencel's avatar Wlodzimierz Wencel

[master] all links kea.isc.org were temporary changed to oldkea.isc.org for upcoming release

parent 1a871b14
......@@ -35,8 +35,8 @@ OSes require boost-system library), log4cplus and one crypto library (either
OpenSSL or Botan) for compilation. Optional backends (MySQL, PostgreSQL and
Cassandra) have additional dependencies. For detailed installation directions,
see the guide at doc/guide/kea-guide.txt or doc/guide/kea-guide.html or on
the Kea wiki: http://kea.isc.org/docs/kea-guide.html#installation
the Kea wiki: http://oldkea.isc.org/docs/kea-guide.html#installation
You can find user-contributed OS-specific build/installation
instructions on the Kea wiki: http://kea.isc.org/wiki/Install
instructions on the Kea wiki: http://oldkea.isc.org/wiki/Install
......@@ -10,7 +10,7 @@ Limitations, known issues and feature requests can be found
at https://gitlab.isc.org/isc-projects/kea/wikis/known-issues-list
If you are thinking about contributing a patch, please read this first:
http://kea.isc.org/wiki/ContributorsGuide
http://oldkea.isc.org/wiki/ContributorsGuide
The Kea mailing lists are available via
https://lists.isc.org/
// Copyright (C) 2017 Internet Systems Consortium, Inc. ("ISC")
// Copyright (C) 2017-2018 Internet Systems Consortium, Inc. ("ISC")
//
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
......@@ -41,7 +41,7 @@ this step is called phase 2.
Other issues with the old parsers are discussed here: @ref dhcpv6ConfigParserBison (this section is
focused on DHCPv6, but the same issues affected DHCPv4 and D2) and here:
http://kea.isc.org/wiki/SimpleParser.
http://oldkea.isc.org/wiki/SimpleParser.
@section parserBisonIntro Flex/Bison Based Parser
......
......@@ -27,7 +27,7 @@ to kea-users.
The first step in writing the patch or new feature should be to get
the source code from our Git repository. The procedure is very easy and
is explained here: http://kea.isc.org/wiki/GitGuidelines. While it is
is explained here: http://oldkea.isc.org/wiki/GitGuidelines. While it is
possible to provide a patch against the latest stable release, it makes
the review process much easier if it is for latest code from the Git \c
master branch.
......@@ -40,12 +40,12 @@ relatively uncommon systems like OpenBSD. Will your code
compile and work there? What about endianness? It is likely that you used
a regular x86 architecture machine to write your patch, but the software
is expected to run on many other architectures. You may take a look at
system specific build notes (http://kea.isc.org/wiki/Install).
system specific build notes (http://oldkea.isc.org/wiki/Install).
For a complete list of systems we build on, you may take a look at the
following build farm report: https://jenkins.isc.org/view/Kea_BuildFarm/ .
Does your patch conform to Kea coding guidelines
(http://kea.isc.org/wiki/CodingGuidelines)? You can submit a
(http://oldkea.isc.org/wiki/CodingGuidelines)? You can submit a
patch that does not adhere to them, but that will reduce its chances of
being accepted. If the deviations are minor, one of the Kea engineers who
does the review will likely fix the issues. However, if there are lots
......
......@@ -22,14 +22,14 @@
*
* If you are a user or system administrator, rather than software engineer,
* you should read the
* <a href="http://kea.isc.org/docs/kea-guide.html">Kea
* <a href="http://oldkea.isc.org/docs/kea-guide.html">Kea
* Administrator Reference Manual</a> instead. If you are using a beta or
* development version of Kea, the
* <a href="http://git.kea.isc.org/~tester/kea/guide/kea-guide.html">
* development version of the manual</a> is recommended.
*
* Regardless of your field of expertise, you are encouraged to visit the
* <a href="http://kea.isc.org/">Kea webpage (http://kea.isc.org)</a>
* <a href="http://oldkea.isc.org/">Kea webpage (http://oldkea.isc.org)</a>
*
* @section contrib Contributor's Guide
* - @subpage contributorGuide - This page describes the process of sending
......
......@@ -15,7 +15,7 @@ base for our C++ unit-tests. See https://github.com/google/googletest for
details. We used to have Python unit-tests inherited from BIND10
days but have been removed, so please do not write any new Kea unit
tests in Python. If you want to write DHCP tests in Python, we encourage you to
take a look at ISC Forge: http://kea.isc.org/wiki/IscForge .
take a look at ISC Forge: http://oldkea.isc.org/wiki/IscForge .
You must have \c gtest installed or at least extracted in a directory
before compiling Kea unit-tests. To enable unit-tests in Kea, use:
......@@ -131,7 +131,7 @@ The following environment variable can affect the unit tests:
The unit tests are run automatically when "make check" is executed (providing
that Kea has been build with the \c --with-mysql switch (see the installation
section in the <a href="http://kea.isc.org/docs/kea-guide.html">Kea Administrator
section in the <a href="http://oldkea.isc.org/docs/kea-guide.html">Kea Administrator
Reference Manual</a>).
@subsection pgsqlUnitTestsPrerequisites PostgreSQL Database
......@@ -257,7 +257,7 @@ local all postgres trust
The unit tests are run automatically when "make check" is executed (providing
that Kea has been build with the \c --with-pgsql switch (see the installation
section in the <a href="http://kea.isc.org/docs/kea-guide.html">Kea Administrator
section in the <a href="http://oldkea.isc.org/docs/kea-guide.html">Kea Administrator
Reference Manual</a>).
......
......@@ -1123,7 +1123,7 @@ concatenation of the strings</entry></row>
<para>
In order to understand the logging statements one must understand a
bit about how expressions are evaluated, for a more complete description
refer to the design document at <uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/KeaDesigns">http://kea.isc.org/wiki/KeaDesigns</uri>.
refer to the design document at <uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/KeaDesigns">http://oldkea.isc.org/wiki/KeaDesigns</uri>.
In brief there are two structures used during the evaluation of an expression:
a list of tokens which represent the expressions and a value stack which
represents the values being manipulated.
......
......@@ -95,7 +95,7 @@
<ulink url="http://tools.ietf.org/html/rfc4361">RFC 4703</ulink>.
In this way, DNS upates for both IPv4 and IPv6 can be managed under
the same DHCID RR. Support for this does not yet exist in Kea but is
called for in the ticket, http://kea.isc.org/ticket/4519, which we
called for in the ticket, http://oldkea.isc.org/ticket/4519, which we
hope to include in a future release.
</para>
</section>
......
......@@ -425,7 +425,7 @@ be followed by a comma and another object definition.</para>
file used by the server to record lease updates. There are also other files
being created as a side effect of the lease file cleanup. The detailed
description of the LFC is located on the Kea wiki:
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/LFCDesign">http://kea.isc.org/wiki/LFCDesign</uri>.
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/LFCDesign">http://oldkea.isc.org/wiki/LFCDesign</uri>.
</para>
</section>
......@@ -3909,7 +3909,7 @@ It is merely echoed by the server
managing reservations in a database, section <xref linkend="host-cmds" /> provide
detailed information. <uri
xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:href="http://kea.isc.org/wiki/HostReservationsHowTo">http://kea.isc.org/wiki/HostReservationsHowTo</uri>
xlink:href="http://oldkea.isc.org/wiki/HostReservationsHowTo">http://oldkea.isc.org/wiki/HostReservationsHowTo</uri>
provides some examples how to conduct common host reservation operations.
</para>
......
......@@ -416,7 +416,7 @@ be followed by a comma and another object definition.</para>
file used by the server to record lease updates. There are also other files
being created as a side effect of the lease file cleanup. The detailed
description of the LFC is located on the Kea wiki:
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/LFCDesign">http://kea.isc.org/wiki/LFCDesign</uri>.
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/LFCDesign">http://oldkea.isc.org/wiki/LFCDesign</uri>.
</para>
</section>
......@@ -3536,7 +3536,7 @@ should include options from the isc option space:
managing reservations in a database, section <xref linkend="host-cmds" /> provide
detailed information. The Kea wiki <uri
xmlns:xlink="http://www.w3.org/1999/xlink"
xlink:href="http://kea.isc.org/wiki/HostReservationsHowTo">http://kea.isc.org/wiki/HostReservationsHowTo</uri>
xlink:href="http://oldkea.isc.org/wiki/HostReservationsHowTo">http://oldkea.isc.org/wiki/HostReservationsHowTo</uri>
provides some examples how to conduct some common operations
on host reservations.
</para>
......
......@@ -574,7 +574,7 @@ $ <userinput>ls -l /usr/local/lib/hooks/*.so</userinput>
ISC hopes to see more hooks libraries become available as time
progresses, both developed internally and externally. Since
this list may evolve dynamically, we decided to keep it on a
wiki page, available at this link: <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/Hooks">http://kea.isc.org/wiki/Hooks</link>.
wiki page, available at this link: <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/Hooks">http://oldkea.isc.org/wiki/Hooks</link>.
If you are a developer or are aware of any hooks libraries not
listed there, please send a note to the kea-users or kea-dev
mailing lists and someone will update it.
......@@ -1405,7 +1405,7 @@ $
<para>
Additional host reservation commands are planned in the future. For
a description of envisaged commands, see
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/ControlAPIRequirements">Control API
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/ControlAPIRequirements">Control API
Requirements </link> document.</para>
<para>
......
......@@ -212,7 +212,7 @@ Debian and Ubuntu:
<para>
Visit the user-contributed wiki at
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/Install">http://kea.isc.org/wiki/Install</uri>
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/Install">http://oldkea.isc.org/wiki/Install</uri>
for system-specific installation tips.
</para>
</section>
......@@ -286,7 +286,7 @@ Debian and Ubuntu:
your code. Please consult
<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://help.github.com/articles/fork-a-repo/">https://help.github.com/articles/fork-a-repo/</uri> for help on
how to fork a Github repository.
The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/docs/devel/">Kea
The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/docs/devel/">Kea
Developer's Guide</link> contains more information about the process, as
well as describing the requirements for contributed code to be accepted by ISC.
</para>
......
......@@ -180,6 +180,14 @@
</simpara>
</listitem>
<listitem>
<simpara>
<command>kea-netconf</command> ?~@~T
Kea netconf is an agent that provides a YANG/NETCONF interface
for the Kea environment.
</simpara>
</listitem>
<listitem>
<simpara>
<command>kea-shell</command>
......
......@@ -47,7 +47,7 @@
This is the reference guide for Kea version &keaversion;.
The most up-to-date version of this document (in PDF, HTML,
and plain text formats), along with other documents for
Kea, can be found at <uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/docs">http://kea.isc.org/docs</uri>.
Kea, can be found at <uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/docs">http://oldkea.isc.org/docs</uri>.
</para> </abstract>
</info>
......
......@@ -520,7 +520,7 @@
identification, which can be used as an index into the
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="kea-messages.html"><citetitle>Kea Messages
Manual</citetitle></link>
(<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/docs/kea-messages.html">http://kea.isc.org/docs/kea-messages.html</uri>)
(<uri xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/docs/kea-messages.html">http://oldkea.isc.org/docs/kea-messages.html</uri>)
from which more information can be obtained.
</para>
</listitem>
......
......@@ -122,8 +122,8 @@ $ <userinput>./configure [your extra parameters]</userinput></screen>
</orderedlist>
<para>
For instructions specific to your system, please read the
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/wiki/SystemSpecificNotes">system specific notes</link>,
available on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://kea.isc.org/">Kea web site</link>.
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/wiki/SystemSpecificNotes">system specific notes</link>,
available on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://oldkea.isc.org/">Kea web site</link>.
</para>
<para>The details of <command>keactrl</command> script usage can be found
......
......@@ -135,14 +135,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -16,7 +16,7 @@ carrying out DDNS conversations with the appropriate DNS servers such that they
update the DNS data.
The design documentation for D2 can be found here:
<a href="http://kea.isc.org/wiki/DhcpDdnsDesign">D2 Design</a>.
<a href="http://oldkea.isc.org/wiki/DhcpDdnsDesign">D2 Design</a>.
This document contains several UML diagrams, and a few conventions used within
these diagrams are worth noting:
......
......@@ -131,14 +131,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -311,7 +311,7 @@ public:
/// instantly. However, it may lead to situations that the message sent
/// in one test will not be dropped by the kernel by the time, the next
/// test starts. This will lead to intermittent unit test errors as
/// described in the ticket http://kea.isc.org/ticket/3265.
/// described in the ticket http://oldkea.isc.org/ticket/3265.
/// Increasing the timeout to a non-zero value mitigates this problem.
/// The proper way to solve this problem is to receive the packet
/// on our own and drop it. Such a fix will need to be applied not only
......
// Copyright (C) 2012-2015,2017 Internet Systems Consortium, Inc. ("ISC")
// Copyright (C) 2012-2018 Internet Systems Consortium, Inc. ("ISC")
//
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
......
......@@ -136,14 +136,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -62,7 +62,7 @@ src/bin/dhcp6/json_config_parser.cc.
During 1.2 milestone it has been decided to significantly refactor the
parsers as their old implementation became unsustainable. For the brief overview
of the problems, see ticket 5014 (http://kea.isc.org/ticket/5014). In
of the problems, see ticket 5014 (http://oldkea.isc.org/ticket/5014). In
general, the following issues of the existing code were noted:
-# parsers are overwhelmingly complex. Even though each parser is relatively
......@@ -343,7 +343,7 @@ mode). Finally, the syntactic context allows the error message to be more
descriptive if the input string does not parse properly.
Details of the refactor of the classes derived from DhcpConfigParser are
documented in http://kea.isc.org/wiki/SimpleParser.
documented in http://oldkea.isc.org/wiki/SimpleParser.
For a generic description of the conflict avoidance, see @ref parserFlex.
......
......@@ -136,14 +136,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -6,8 +6,8 @@
// do. Comments in this configuration file sometimes refer to sections for more
// details. These are section numbers in Kea User's Guide. The version matching
// your software should come with your Kea package, but it is also available
// on Kea web page (http://kea.isc.org, click User's Guide, direct link for
// stable version is http://kea.isc.org/docs/kea-guide.html).
// on Kea web page (http://oldkea.isc.org, click User's Guide, direct link for
// stable version is http://oldkea.isc.org/docs/kea-guide.html).
//
// This configuration file contains only Control Agent's configuration.
// If configurations for other Kea services are also included in this file they
......
......@@ -6,8 +6,8 @@
// do. Comments in this configuration file sometimes refer to sections for more
// details. These are section numbers in Kea User's Guide. The version matching
// your software should come with your Kea package, but it is also available
// on Kea web page (http://kea.isc.org, click User's Guide, direct link for
// stable version is http://kea.isc.org/docs/kea-guide.html).
// on Kea web page (http://oldkea.isc.org, click User's Guide, direct link for
// stable version is http://oldkea.isc.org/docs/kea-guide.html).
//
// This configuration file contains only DHCP DDNS daemon's configuration.
// If configurations for other Kea services are also included in this file they
......
......@@ -15,8 +15,8 @@
// do. Comments in this configuration file sometimes refer to sections for more
// details. These are section numbers in Kea User's Guide. The version matching
// your software should come with your Kea package, but it is also available
// on Kea web page (http://kea.isc.org, click User's Guide, direct link for
// stable version is http://kea.isc.org/docs/kea-guide.html).
// on Kea web page (http://oldkea.isc.org, click User's Guide, direct link for
// stable version is http://oldkea.isc.org/docs/kea-guide.html).
//
// This configuration file contains only DHCPv4 server's configuration.
// If configurations for other Kea services are also included in this file they
......@@ -245,7 +245,7 @@
// even influence how the server processes packets. Those libraries include
// additional forensic logging capabilities, ability to reserve hosts in
// more flexible ways, and even add extra commands. For a list of available
// hook libraries, see http://kea.isc.org/wiki/Hooks.
// hook libraries, see http://oldkea.isc.org/wiki/Hooks.
//"hooks-libraries": [
// {
// // Forensic Logging library generates forensic type of audit trail
......
......@@ -15,8 +15,8 @@
// do. Comments in this configuration file sometimes refer to sections for more
// details. These are section numbers in Kea User's Guide. The version matching
// your software should come with your Kea package, but it is also available
// on Kea web page (http://kea.isc.org, click User's Guide, direct link for
// stable version is http://kea.isc.org/docs/kea-guide.html).
// on Kea web page (http://oldkea.isc.org, click User's Guide, direct link for
// stable version is http://oldkea.isc.org/docs/kea-guide.html).
//
// This configuration file contains only DHCPv6 server's configuration.
// If configurations for other Kea services are also included in this file they
......
......@@ -203,14 +203,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -200,14 +200,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -21,7 +21,7 @@ the lease files and keep only the most recent instance of each lease. When it f
reading the leases it will write the unique leases to the output file.
The design documentation for kea-lfc can be found here:
<a href="http://kea.isc.org/wiki/LFCDesign"> LFC Design</a>
<a href="http://oldkea.isc.org/wiki/LFCDesign"> LFC Design</a>
While kea-lfc can be started externally, there is usually no need to do this as the
Kea servers will run it on a periodic basis.
......@@ -59,7 +59,7 @@ the extra files then exits.
This section is intended to provide a brief overview of how kea-lfc uses its
files. For a more in depth discussion of the design see
<a href="http://kea.isc.org/wiki/LFCDesign"> LFC Design</a>
<a href="http://oldkea.isc.org/wiki/LFCDesign"> LFC Design</a>
There are four files used during the kea-lfc process: previous, input, output
and finish. They are used to both hold the leases and to indicate to the Kea
......
......@@ -55,7 +55,7 @@ public:
///
/// Provides the control logic to combine two lease files and
/// weed out duplicate and expired leases. A description of
/// the design can be found at http://kea.isc.org/wiki/LFCDesign
/// the design can be found at http://oldkea.isc.org/wiki/LFCDesign
///
/// -# parse command line arguments
/// -# verify that it is the only instance
......
......@@ -10,8 +10,8 @@
<info>
<productname>ISC Kea</productname>
<date>Oct. 14, 2018</date>
<edition>1.5.0</edition>
<date>Nov. 9, 2018</date>
<edition>1.5.0-beta</edition>
<author>
<contrib>The Kea software has been written by a number of
engineers working for ISC: Tomek Mrugalski, Stephen Morris, Marcin
......@@ -126,14 +126,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -152,14 +152,14 @@
description for each of them. Both documents are typically
available in various formats (txt, html, pdf) with your Kea
distribution. The on-line version is available at
http://kea.isc.org/docs/.</para>
http://oldkea.isc.org/docs/.</para>
<para>
Kea source code is documented in the Kea Developer's Guide. It's
on-line version is available at http://kea.isc.org. Please
on-line version is available at http://oldkea.isc.org. Please
follow Developer's Guide link.
</para>
<para>
Kea project website is available at: http://kea.isc.org.
Kea project website is available at: http://oldkea.isc.org.
</para>
</refsect1>
......
......@@ -16,7 +16,7 @@ library. This file provides information needed to understand and perhaps extend
this library.
This documentation is stand-alone: you should have read and understood <a
href="http://kea.isc.org/docs/devel/">Kea Developer's Guide</a> and in
href="http://oldkea.isc.org/docs/devel/">Kea Developer's Guide</a> and in
particular its section about hooks.
@section lease_cmds Lease Commands Overview
......
......@@ -16,7 +16,7 @@ library. This file provides information needed to understand and perhaps extend
this library.
This documentation is stand-alone: you should have read and understood <a
href="http://kea.isc.org/docs/devel/">Kea Developer's Guide</a> and in
href="http://oldkea.isc.org/docs/devel/">Kea Developer's Guide</a> and in
particular its section about hooks.
@section stat_cmds Stat Commands Overview
......@@ -49,7 +49,7 @@ As with other hooks, this one keeps its code in a separate namespace which
corresponds to the file name of the library: isc::stat_cmds.
For background on the design and design choices please refer to: <a
href="http://kea.isc.org/wiki/SharedLeaseStorageStats">Shared Lease Stats Design</a>
href="http://oldkea.isc.org/wiki/SharedLeaseStorageStats">Shared Lease Stats Design</a>
@section stat_cmdsCode Stat Commands Code Overview
......
......@@ -16,7 +16,7 @@ over time (DHCP configuration is significantly more complex than DNS, with
more interdependent values) and as of Kea 1.1 release it became very difficult
to manage. The decision has been made to significantly refactor or even
partially rewrite the parser code. The design for this effort is documented
here: http://kea.isc.org/wiki/SimpleParser It discusses the original issues
here: http://oldkea.isc.org/wiki/SimpleParser It discusses the original issues
and the proposed architecture.
There are several aspects of this new approach. The base class for all
......
......@@ -14,7 +14,7 @@
///
/// This file contains several functions and constants that are used for
/// handling commands and responses sent over control channel. The design
/// is described here: http://kea.isc.org/wiki/StatsDesign, but also
/// is described here: http://oldkea.isc.org/wiki/StatsDesign, but also
/// in @ref ctrlSocket section in the Developer's Guide.
namespace isc {
......
......@@ -41,7 +41,7 @@ public:
/// uses the command as an input and invokes appropriate handlers.
///
/// The commands and responses are formatted using JSON.
/// See http://kea.isc.org/wiki/StatsDesign for details.
/// See http://oldkea.isc.org/wiki/StatsDesign for details.
///
/// Below is an example of the command using JSON format:
/// @code
......
......@@ -24,7 +24,7 @@ namespace dhcp {
///
/// This is an implementation of the DHCPv4-query/response DHCPv6 messages
/// defined in RFC 7341 (http://ietf.org/rfc/rfc7341.txt).
/// See also http://kea.isc.org/wiki/Dhcp4o6Design for design discussions.
/// See also http://oldkea.isc.org/wiki/Dhcp4o6Design for design discussions.
class Pkt4o6 : public Pkt4 {
public:
......
......@@ -486,7 +486,7 @@ const OptionDefParams OPTION_DEF_PARAMS_S46_PORTPARAMS = { "s46-portparams",
/// @brief Definitions of vendor-specific DHCPv6 options, defined by ISC.
/// 4o6-* options are used for inter-process communication. For details, see
/// http://kea.isc.org/wiki/Dhcp4o6Design
/// http://oldkea.isc.org/wiki/Dhcp4o6Design
///
/// @todo: As those options are defined by ISC, they do not belong in std_option_defs.h.
/// We need to move them to a separate file, e.g. isc_option_defs.h
......
......@@ -642,7 +642,7 @@ public:
/// @brief Reclaims expired IPv6 leases.
///
/// This method retrieves a collection of expired leases and reclaims them.
/// See http://kea.isc.org/wiki/LeaseExpirationDesign#LeasesReclamationRoutine
/// See http://oldkea.isc.org/wiki/LeaseExpirationDesign#LeasesReclamationRoutine
/// for the details.
///
/// This method is executed periodically to act upon expired leases. This
......@@ -700,7 +700,7 @@ public:
/// @brief Reclaims expired IPv4 leases.
///
/// This method retrieves a collection of expired leases and reclaims them.
/// See http://kea.isc.org/wiki/LeaseExpirationDesign#LeasesReclamationRoutine
/// See http://oldkea.isc.org/wiki/LeaseExpirationDesign#LeasesReclamationRoutine
/// for the details.
///
/// This method is executed periodically to act upon expired leases. This
......
......@@ -226,7 +226,7 @@ public:
/// received over.
///
/// @todo: Add additional selection criteria. See
/// http://kea.isc.org/wiki/ISC-DHCP4o6-Design for details.
/// http://oldkea.isc.org/wiki/ISC-DHCP4o6-Design for details.
///
/// @param selector Const reference to the selector structure which holds
/// various information extracted from the client's packet which are used
......
......@@ -28,7 +28,7 @@ namespace dhcp {
///
/// @todo This class doesn't validate the lease values read from the file.
/// The @c Lease4 is a structure that should be itself responsible for this
/// validation (see http://kea.isc.org/ticket/2405). However, when #2405
/// validation (see http://oldkea.isc.org/ticket/2405). However, when #2405
/// is implemented, the @c next function may need to be updated to use the
/// validation capablity of @c Lease4.
class CSVLeaseFile4 : public isc::util::VersionedCSVFile, public LeaseFileStats {
......@@ -77,7 +77,7 @@ public:
///
/// @todo Make sure that the values read from the file are correct.
/// The appropriate @c Lease4 validation mechanism should be used once
/// ticket http://kea.isc.org/ticket/2405 is implemented.
/// ticket http://oldkea.isc.org/ticket/2405 is implemented.
bool next(Lease4Ptr& lease);
private:
......
......@@ -27,7 +27,7 @@ namespace dhcp {
///
/// @todo This class doesn't validate the lease values read from the file.
/// The @c Lease6 is a structure that should be itself responsible for this
/// validation (see http://kea.isc.org/ticket/2405). However, when #2405
/// validation (see http://oldkea.isc.org/ticket/2405). However, when #2405
/// is implemented, the @c next function may need to be updated to use the
/// validation capablity of @c Lease6.
class CSVLeaseFile6 : public isc::util::VersionedCSVFile, public LeaseFileStats {
......@@ -76,7 +76,7 @@ public:
///
/// @todo Make sure that the values read from the file are correct.
/// The appropriate @c Lease6 validation mechanism should be used once
/// ticket http://kea.isc.org/ticket/2405 is implemented.
/// ticket http://oldkea.isc.org/ticket/2405 is implemented.
bool next(Lease6Ptr& lease);
private:
......
......@@ -37,7 +37,7 @@ class LFCSetup;
/// in a significant growth of the lease file size over time, because the lease
/// file will contain many entries for each lease. In order to mitigate this
/// problem, the backend implements the Lease File Cleanup mechanism which is
/// described on the Kea wiki: http://kea.isc.org/wiki/LFCDesign.
/// described on the Kea wiki: http://oldkea.isc.org/wiki/LFCDesign.
///
/// The backend installs an @c asiolink::IntervalTimer to periodically execute
/// the @c Memfile_LeaseMgr::lfcCallback. This callback function controls
......@@ -548,7 +548,7 @@ public:
/// - LFC Finish File: ".completed"
/// - LFC PID File: ".pid"
///
/// See http://kea.isc.org/wiki/LFCDesign for details.
/// See http://oldkea.isc.org/wiki/LFCDesign for details.
///
/// @param file_name A base file name to which suffix is appended.
/// @param file_type An LFC file type.
......@@ -634,7 +634,7 @@ private:
///
/// The <filename>.2, <filename>.1 and <filename>.completed are the
/// products of the lease file cleanups (LFC).
/// See: http://kea.isc.org/wiki/LFCDesign for details.
/// See: http://oldkea.isc.org/wiki/LFCDesign for details.
///
/// @note: When the server starts up or is reconfigured it will try to