<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Radius on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/radius/</link>
        <description>Recent content in Radius on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 27 Jun 2016 11:51:44 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/radius/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Ubuntu] Radsecproy for secure Radius over WAN</title>
            <link>https://www.nico-maas.de/posts/2016-06-27-ubuntu-radsecproy-for-secure-radius-over-wan/</link>
            <pubDate>Mon, 27 Jun 2016 11:51:44 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-06-27-ubuntu-radsecproy-for-secure-radius-over-wan/</guid>
            <description>&lt;p&gt;Chances are you going to need an radius Auth over WAN - because your Radius and Identity Mngmnt is hosted in the security of the local datacenter of your corp&amp;hellip; but the client (i.e. an network switch) is somewhere over the &lt;del&gt;rainbow&lt;/del&gt; WAN. You &lt;em&gt;could&lt;/em&gt; just pipe the radius traffic over the internet - but there be dragons: radius communication is unencrypted. So&amp;hellip; just no.&lt;/p&gt;&#xA;&lt;p&gt;Enter radsecproxy: Radsecproxy is - as the name implies, an radius proxy - which needs to be installed on both servers (the local one in your company, now called SERVER, and the remote one with the switch attached, now called CLIENT) - and does encrypt the communication between both server parts (over WAN i.e.) via TLS.&lt;/p&gt;</description>
        </item><item>
            <title>[Ubuntu] Freeradius: Improve Uptime</title>
            <link>https://www.nico-maas.de/posts/2016-05-20-ubuntu-freeradius-improve-uptime/</link>
            <pubDate>Fri, 20 May 2016 08:00:43 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-05-20-ubuntu-freeradius-improve-uptime/</guid>
            <description>&lt;p&gt;As a network admin, you&amp;rsquo;re going to have at least one Freeradius running, mostly for 802.1x authentication. At my place the problem arised, that the service was down too often - for different reasons.&lt;/p&gt;&#xA;&lt;p&gt;1.) Logrotate&lt;br&gt;&#xA;If you&amp;rsquo;re using logrotate, you should check out /etc/logrotate.d/freeradius:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;/var/log/freeradius/*.log {&#xD;&#xA;weekly&#xD;&#xA;rotate 52&#xD;&#xA;compress&#xD;&#xA;delaycompress&#xD;&#xA;notifempty&#xD;&#xA;missingok&#xD;&#xA;postrotate&#xD;&#xA;invoke-rc.d freeradius reload &amp;amp;gt;/dev/null 2&amp;amp;gt;&amp;amp;1 || true&#xD;&#xA;endscript&#xD;&#xA;}&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Logrotate does restart freeradius after it swapped the logs with reload, which often results in a crash or race condition (freeradius does not shutdown fast enough, and the restarting process thinks it already got one running process - and both terminate). So to change that, you should stop the process, wait, and start again.&lt;/p&gt;</description>
        </item></channel>
</rss>
