Not really a bug, but I feel I should report it if someone else run into the
same issue.
On Ubuntu 10.4 (Lucid) when I try to build debs from the 2.1.11 source using
the instructions on the Wiki,
( http://wiki.freeradius.org/Build#Building+Debian+packages
On Mon, Jun 27, 2011 at 12:16 AM, Dirk van der Walt
dirkvanderw...@gmail.com wrote:
Not really a bug, but I feel I should report it if someone else run into the
same issue.
On Ubuntu 10.4 (Lucid) when I try to build debs from the 2.1.11 source using
the instructions on the Wiki,
(
On Thu, Jun 23, 2011 at 12:48 AM, John Dennis jden...@redhat.com wrote:
freeradius-2.1.11 RPM packages for Fedora 14 and Fedora 15 have been pushed
into their respective *testing* repos. It may take a while for them to hit
the mirrors.
To upgrade via yum you will need to enable the testing
Hi,
On Thu, Jun 23, 2011 at 12:48 AM, John Dennis jden...@redhat.com wrote:
freeradius-2.1.11 RPM packages for Fedora 14 and Fedora 15 have been pushed
into their respective *testing* repos. It may take a while for them to hit
the mirrors.
To upgrade via yum you will need to enable the
On 06/23/2011 03:11 AM, Fajar A. Nugraha wrote:
On Thu, Jun 23, 2011 at 12:48 AM, John Dennisjden...@redhat.com wrote:
freeradius-2.1.11 RPM packages for Fedora 14 and Fedora 15 have been pushed
into their respective *testing* repos. It may take a while for them to hit
the mirrors.
To upgrade
John Dennis wrote:
The bootstrap logic has been changed, the comment in eap.conf says:
...
Maybe I'm missing something but it seems pointless to have certificate
validation logic in the bootstrap command if it's only run in debug and
and only if the cert doesn't exist. It also seems to
freeradius-2.1.11 RPM packages for Fedora 14 and Fedora 15 have been
pushed into their respective *testing* repos. It may take a while for
them to hit the mirrors.
To upgrade via yum you will need to enable the testing repo, e.g.
yum --enablerepo=fedora-updates-testing upgrade freeradius
--
Hi,
a similar issue with the config parser here...
The following worked nicely in 2.1.10, but barks with Unexpected text
else (and with the obvious change to elsif, Unexpected text elsif).
if ( %{NAS-Identifier} == ejabberd ) {
update request {
Stefan Winter wrote:
a similar issue with the config parser here...
The following worked nicely in 2.1.10, but barks with Unexpected text
else (and with the obvious change to elsif, Unexpected text elsif).
if ( %{NAS-Identifier} == ejabberd ) {
update request {
man unlang :)
Everything needs to go on its own line:
if (...) {
...
}
elsif (...) {
...
}
Using } elseif won't work. The elsif will *always* be ignored.
Yes... that's always been the syntax, it's a line based parser. All
Hi,
Hi,
a similar issue with the config parser here...
The following worked nicely in 2.1.10, but barks with Unexpected text
else (and with the obvious change to elsif, Unexpected text elsif).
if ( %{NAS-Identifier} == ejabberd ) {
update request {
Hello Alan, all,
thanks for that quick lesson :-) I stand corrected; and with the right
ordering, things are now working as they should.
I did wonder a few times why that attribute RESTENA-Service-Type wasn't
properly populated in some cases :-) But no bad things happened, just
things being
The bootstrap logic has been changed, the comment in eap.conf says:
# This command creates the initial snake oil
# certificates when the server is run as root,
# and via radiusd -X.
#
# As of 2.1.11, it *also* checks the server
# certificate for validity, including expiration.
# This means that
Hi,
It's been a long time since 2.1.10. We're happy to release version
2.1.11, which has many of useful new features, and a number of minor
bugs fixed.
yay! :-) virtual champagne cork released
however, a nice quirky change in config parser means that any unlang
style code with an 'if'
Alan Buxey wrote:
however, a nice quirky change in config parser means that any unlang
style code with an 'if' condition check that end with no space before
curlies eg
Arg. That's annoying. It would have been nice to catch that.
Anyways, the fix is simple.
At least there's a
, 2011 10:00 AM
To: FreeRadius users mailing list
Subject: Re: Version 2.1.11 has been released
Alan Buxey wrote:
however, a nice quirky change in config parser means that any unlang
style code with an 'if' condition check that end with no space before
curlies eg
Arg. That's annoying
Hi,
Arg. That's annoying. It would have been nice to catch that.
it must have gone in pretty late as we didnt have an issue with 2.1.11
GIT release on our test server (which is now running 3.0.0 GIT for some
REAL testing ;-) )
alan
-
List info/subscribe/unsubscribe? See
Hi,
Fix it real quick before many download it, call it 2.1.11.1 - or 2.1.11a :)
if its to be changed then 2.1.12 and at least change the old year in
src/main/version.c
there are other date copyright files - i guess the authors should assert this
but
the main project should cover
18 matches
Mail list logo
