Hi, thanks for answering. The main functionality I need is RadSec I'm not very shure on which version it is practical to use. The other things I'll get to work I think. Maybe you can get me a hint which version, or which not, to use? Thank you much! Am Montag, 19. September 2016, 19:19:52 CEST schrieb freeradius-users- request@lists.freeradius.org:
Message: 1 Date: Mon, 19 Sep 2016 12:51:15 +0000 From: Alan Buxey <A.L.M.Buxey@lboro.ac.uk> To: "freeradius-users@lists.freeradius.org" <freeradius-users@lists.freeradius.org> Subject: Re: 4.0.x Release Date Message-ID:
<DB5PR04MB111196F42778A4E93A555AD1A7F40@DB5PR04MB1111.eurprd04.prod.outlo ok
.com>
Content-Type: text/plain; charset="iso-8859-1"
hi,
More precice I'm standing before the questions to wait for the next release while using 3.0.x or 4.0.x. It will be no complex infrastructure, just LDAP, PEAP w. MS-CHAPv2 and unsing the proxy.
a common question. if you want latest features, then 3.1.x will do the MSCHAPv2 stuff for you much better with winbind native and the LDAP stuff is much better too.
*currently* there is little difference with 3.1.x and 4.0.x config BUT that is set to change massively. (I'd prefer the big changes just go to 4.1.x and 4.0.x becomes what it is now.....)
(so whilst docs may say one thing, it may be best to wait for main developers to have a clear answer!)
alan
------------------------------
Message: 2 Date: Mon, 19 Sep 2016 08:59:24 -0400 From: Alan DeKok <aland@deployingradius.com> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: 4.0.x Release Date Message-ID: <CBE58A41-403B-46AE-8E14-4C87C7C8C561@deployingradius.com> Content-Type: text/plain; charset=us-ascii
On Sep 19, 2016, at 8:51 AM, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
*currently* there is little difference with 3.1.x and 4.0.x config BUT that is set to change massively. (I'd prefer the big changes just go to 4.1.x and 4.0.x becomes what it is now.....) Major releases are for changes which break configurations. We don't do that in a minor release.
We can't release version 3.2. OS vendors refuse to upgrade for years, and we just don't have enough people to to support 4-5 "stable" releases
(so whilst docs may say one thing, it may be best to wait for main developers to have a clear answer!)
Use 3.0.
If you know what you're doing, and you *need* the functionality in 3.1, then use 3.1.
Otherwise, wait for 4.0.
Alan DeKok.
------------------------------
Message: 3 Date: Mon, 19 Sep 2016 13:02:49 +0000 From: Alan Buxey <A.L.M.Buxey@lboro.ac.uk> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: 4.0.x Release Date Message-ID:
<DB5PR04MB1111641E8D515F21292200D6A7F40@DB5PR04MB1111.eurprd04.prod.outlo ok
.com>
Content-Type: text/plain; charset="iso-8859-1"
hi,
so the key message is
"Use 3.0, unless you know what you're doing, and you *need* the functionality in 3.1, then use 3.1. Otherwise, wait for 4.0"
- so if people are aware of 3.1.x extra functionality, thats okay - but what about bugs/issues found in 3.1.x ?
alan
------------------------------
Message: 4 Date: Mon, 19 Sep 2016 09:20:59 -0400 From: Alan DeKok <aland@deployingradius.com> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: 4.0.x Release Date Message-ID: <CC6CEE2D-FE14-4769-BF8A-8F8818B5E856@deployingradius.com> Content-Type: text/plain; charset=us-ascii
On Sep 19, 2016, at 9:02 AM, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
so the key message is
"Use 3.0, unless you know what you're doing, and you *need* the functionality in 3.1, then use 3.1. Otherwise, wait for 4.0"
Yes.
- so if people are aware of 3.1.x extra functionality, thats okay - but what about bugs/issues found in 3.1.x ? Submit a patch.
We can commit to maintaining 3.0, and doing development on 4.0. Adding another release is just too much.
So... anyone needing a fix in 3.1 should submit a fix. :(
Alan DeKok. --
