Commit df5bfc6a authored by Francis Dupont's avatar Francis Dupont

[75-radius-documentation-needs-an-update] Resolved merge conflict

parents b52fedcf 75627fcd
......@@ -93,7 +93,7 @@ $ sudo yum install gcc-g++ openssl-devel log4cplus-devel wget git
reported to FreeRadius client project. Acceptance of those
changes is outside of ISC responsibilities. Until those
are processed, it is strongly recommended to use FreeRadius
client with ISC patches. To and compile this version, please use
client with ISC patches. To download and compile this version, please use
the following steps:
<screen>
$ git clone https://github.com/fxdupont/freeradius-client.git
......@@ -137,8 +137,7 @@ $ sudo ./b2 install
</screen>
Note that b2 script may optionally take extra parameters. One
of them specify the destination path where the sources are to
be compiled. Boost is different compared to other software in
the sense that there is no explicit make install step.
be compiled.
</para>
<para>
......@@ -154,7 +153,7 @@ $ sudo ./b2 install
$ git clone https://github.com/isc-projects/kea
# Get a tarball and extract it
$ tar zxvf kea-1.4.0-beta.tar.gz
$ tar zxvf kea-1.4.0.tar.gz
</screen>
The next step is to extract premium Kea package that contains Radius repository
......@@ -163,7 +162,7 @@ a premium/ subdirectory.
<screen>
$ cd kea
$ tar zxvf ../kea-premium-radius-1.4.0-beta.tar.gz
$ tar zxvf ../kea-premium-radius-1.4.0.tar.gz
</screen>
Once this is done, make sure the kea sources look similar to this:
......@@ -188,15 +187,14 @@ drwxr-xr-x 10 thomson staff 340 Apr 26 19:04 src
drwxr-xr-x 14 thomson staff 476 Apr 26 19:04 tools
</screen>
The next step is to configure Kea. There are several essential steps necessary here.
The makefiles have to be regenerated using autoreconf.</para>
<para>The next step is to configure Kea. There are several essential steps necessary here.
Running autoreconf -if is necessary to compile premium package that contains
RADIUS. Also, --with-freeradius option is necessary to tell Kea where the FreeRADIUS
client sources can be found. Also, since the non-standard boost is used, the path
to it has to be specified.</para>
<para>If the sources are not from a tarball release, makefiles have to be regenerated
using autoreconf.</para>
<screen>
$ autoreconf -i
$ ./configure --with-freeradius=/path/to/freeradius --with-boost-include=/path/to/boost --with-boost-lib-dir=/path/to/boost/state/lib
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment