Hi,
one of the main issues is using a distro version of the code.
what they do to the files provided in the TARBALL is up to them.
i would advise doing something like
locate scripts | grep -i radius
...they might have been dumped into somewhere like /usr/share/doc/radiusd
or somesuch.
you can
hi,
Charles, this is an unpaid community support list. you are coming
across as a very angry person with no regard that the people
on this list arent paid to give you informaation which is probably
essential for you to actually do your work, get paid etc.
if you'd actually like any help/advice
On Mon, 15 Jun 2009, a.l.m.bu...@lboro.ac.uk wrote:
one of the main issues is using a distro version of the code.
(nod) Once John mentioned a folder I just didn't have, the light came on
(so to speak) :)
...they might have been dumped into somewhere like /usr/share/doc/radiusd
or
On Mon, 15 Jun 2009, a.l.m.bu...@lboro.ac.uk wrote:
Charles, this is an unpaid community support list. you are coming
across as a very angry person with no regard that the people
on this list arent paid to give you informaation which is probably
essential for you to actually do your work, get
On 15/6/09 16:37, Charles Gregory wrote:
On Mon, 15 Jun 2009, a.l.m.bu...@lboro.ac.uk wrote:
one of the main issues is using a distro version of the code.
(nod) Once John mentioned a folder I just didn't have, the light came on
(so to speak) :)
...they might have been dumped into
On Mon, 15 Jun 2009, Arran Cudbard-Bell wrote:
See the thing is a lot of the documentation pitfalls aren't there in 2.*, a
lot of the inconsistencys aren't there in 2.*. I know, because I regularly
play the dumb user and pester Alan about niggly bits of syntax and
documentation.
I try to be
Enough already :-) Take it off list please.
--
John Dennis jden...@redhat.com
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
hi,
H. My first gut reaction is that I don't know enough, but before
I dismiss this idea, I have to ask what you have in mind.
I think the initial idea would be to document what/how you've used
exec module to define an attribute - rlm_exec is quite bare on the wiki ;-)
alan
-
List
Charles Gregory wrote:
No, I'm offended that you can say things like you have NO IDEA when
clearly anyone who read my first post would know what I was asking.
Yes, but you were given 5-6 options for solving the problem. Instead,
you did something that was not documented as working, and which
Charles Gregory wrote:
Five or six huh? Quote them. Paraphrase them. And don't just lamely say
check the archives because I did that when I double-checked that you
'had no idea'. I've been up and down this thread a few times now. And
there is NO posting with clear code like the one I posted in
On Sun, 14 Jun 2009, Alan DeKok wrote:
Charles Gregory wrote:
Five or six huh? Quote them.
1) Read my messages.
That's rich coming from you.
The text you *deleted* pointed you to documentation for the
users file, and the SQL module.
Speaking of 'not reading' didn't you catch my
Charles Gregory wrote:
Well, keeping in mind that this is now a philosphical discussion...
And it's mostly wasted. The time spent arguing over the documentation
would have been better spent installing 2.x, which has much better
documentation.
Notice the complete lack of instruction as to
On Fri, 12 Jun 2009, Ivan Kalik wrote:
Nothing to give. You already have it in scripts/exec-program-wait.
I do not have a directory named 'scripts'. And the only reference to
'exec-program-wait' is in the comments of 'experimental.conf' as something
that a 'perl' rlm can 'replace'. I'm
On Sat, 13 Jun 2009, Alan DeKok wrote:
No... I had NO IDEA what you were trying to do.
I had gotten the impression that you don't read posts thoroughly,
and this only reinforces that perception. My very first post said:
I've been cruising the archives and pages and don't quite see
what
On Sat, 13 Jun 2009, Ivan Kalik wrote:
. I'm really thinking that CentOS screwed up some documentation
Could be. They might have packaged server core without examples. ..
If you want you can download and unpack your version tarball from the
freeradius site
Just because I am
Charles Gregory wrote:
It clearly conveys my intention and my first attempt at code.
Yes... and it clearly conveys that you hadn't read the documentation
that came with the version you had.
So with (dwindling) respect, if you can't get the IDEA from that
then you really are a serious waste
On Sat, 13 Jun 2009, Alan DeKok wrote:
and yet you're frustrated that I'm explaining the *reasons* behind my
opinions.
No, I'm offended that you can say things like you have NO IDEA when
clearly anyone who read my first post would know what I was asking.
It's one step short of outright
On Fri, 12 Jun 2009, Alan DeKok wrote:
Charles Gregory wrote:
But CentOS is supposedly still a 'supported' OS, so I think it's fair
to ask simple 'how to' questions for that environment.
Centos supports their OS. This list answers questions about FreeRADIUS.
Quite right. CentOS supports
Charles Gregory wrote:
Why do you LET RedHat use the old version if it is so unsupported?
There appears to be a fundamental misconception in that sentence:
We don't control RedHat.
So... RedHat does whatever the heck makes them happy. And it makes
them happy to keep their
On 06/12/2009 01:23 AM, Alan DeKok wrote:
Charles Gregory wrote:
But CentOS is
supposedly still a 'supported' OS, so I think it's fair to ask simple
'how to' questions for that environment.
Centos supports their OS. This list answers questions about FreeRADIUS.
Let's clarify something,
John Dennis wrote:
Let's clarify something, calling CentOS a supported OS is a little
misleading.
The CentOS people answer questions about CentOS on the CentOS mailing
list. That is the limit of their support.
Similarly, the FreeRADIUS people answer questions about FreeRADIUS on
the
On Fri, 12 Jun 2009, John Dennis wrote:
BTW, the philosophy of RHEL (why it's older), the philosophy of Fedora (why
it's bleeding edge) and CentOS is explained on the FreeRadius FAQ under Red
Hat (http://wiki.freeradius.org/Red_Hat_FAQ). It's incumbent upon you when
selecting an OS to install
So if I have any legitimate complaint against the FreeRADIUS team it is
only that with versions so 'close together' in time, there really should
either be a repository of documents applying to 1.x
Documentation is included with the server. Read comments in configuration
files you are
On Fri, 12 Jun 2009, Alan DeKok wrote:
The CentOS people answer questions about CentOS on the CentOS mailing
list. That is the limit of their support.
Similarly, the FreeRADIUS people answer questions about FreeRADIUS on
the freeradius-users list.
What do you mean by people? What *I* mean
Charles Gregory wrote:
On Fri, 12 Jun 2009, Alan DeKok wrote:
The CentOS people answer questions about CentOS on the CentOS mailing
list. That is the limit of their support.
Similarly, the FreeRADIUS people answer questions about FreeRADIUS on
the freeradius-users list.
What do you mean
Charles Gregory wrote:
...there really
should either be a repository of documents applying to 1.x (similar to
how Apache mainatains its separate document trees for 1.x and 2x),
Sure. Apache has 1000 times as many installations as FreeRADIUS, and
probably 1000 times as much funding, and
You better believe that if I 'work
it out for myself' I will be coming back to this list with a howto and
examples for any other 1.x user who runs into the same situation that I
have.
Work what out?
Your problem has nothing to do with freeradius vesrion. exec module hasn't
changed in years.
On Fri, 12 Jun 2009, Ivan Kalik wrote:
Work what out?
Finally got my 1.x Session-Time script working (as an exec module). The
really strange thing is that it is working *exactly* as I first thought
I should be doing it!!! (see below) I can only guess that somewhere along
the way I had a
Sure. We'll wait.
Alan DeKok.
(smile)
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Charles Gregory wrote:
I did try to follow the oft-quoted (almost shoved down my throat)
example, right from the comments within the config file
postauth {
Session-Timeout := `%{exec:/usr/local/etc/timecalc %{User-Name}}`
}
No... that won't work. The examples given to you weren't
Well, keeping in mind that this is now a philosphical discussion...
On Fri, 12 Jun 2009, Alan DeKok wrote:
Charles Gregory wrote:
I did try to follow the oft-quoted (almost shoved down my throat)
example, right from the comments within the config file
postauth {
Session-Timeout :=
Well, firstly, no one *gave* me 'examples',
Nothing to give. You already have it in scripts/exec-program-wait. It's
included in the distribution. Should be in same place in your version too.
they said just to look in my
radiusd.conf, and secondly, yes, it's exactly 'like that':
#
On Fri, 12 Jun 2009, Ivan Kalik wrote:
Nothing to give. You already have it in scripts/exec-program-wait.
I do not have a directory named 'scripts'. And the only reference to
'exec-program-wait' is in the comments of 'experimental.conf' as something
that a 'perl' rlm can 'replace'. I'm really
Okay, I'm banging my head up against the expected proverbial wall.
Please remember I'm stuck with old 1.x version. on Centos
I'm trying to get a script to execute and set the 'Session-Timeout'
value. I've defined the script thusly:
exec timecalc {
wait = yes
Okay, I'm banging my head up against the expected proverbial wall.
Please remember I'm stuck with old 1.x version. on Centos
Which is not supported.
I'm trying to get a script to execute and set the 'Session-Timeout'
value. I've defined the script thusly:
exec timecalc {
On 06/11/2009 04:42 PM, Charles Gregory wrote:
Okay, I'm banging my head up against the expected proverbial wall.
Please remember I'm stuck with old 1.x version. on Centos
No you're not stuck with an old 1.x.
See: http://wiki.freeradius.org/Red_Hat_FAQ
--
John Dennis jden...@redhat.com
On Thu, 11 Jun 2009, John Dennis wrote:
No you're not stuck with an old 1.x.
See: http://wiki.freeradius.org/Red_Hat_FAQ
Go read the thread Version... Version..
I posted that thread partly in anticipation that when I started to ask
for help with my 'standard' CentOS FreeRadius, people
Charles Gregory wrote:
But CentOS is
supposedly still a 'supported' OS, so I think it's fair to ask simple
'how to' questions for that environment.
Centos supports their OS. This list answers questions about FreeRADIUS.
And the 1.x versions are *not* supported by us. When people ask
Hello again!
Sorry, maybe I should take 'pseudo' out of the subject line...
Firstly, MY BAD. I forgot to post that I'm on CentOS 4, and therefore
limited to whatever syntax applies to freeradius-1.0.1-3.RHEL4.5
Hopefully what I want to do is so 'basic' it doesn't change :)
Secondly, anyone
Charles Gregory wrote:
Sorry, maybe I should take 'pseudo' out of the subject line...
Firstly, MY BAD. I forgot to post that I'm on CentOS 4, and therefore
limited to whatever syntax applies to freeradius-1.0.1-3.RHEL4.5
Upgrade. There should be RPMs available for that. See
Greetings!
I've been cruising the archives and pages and don't quite see
what I am looking for. I am hoping someone can point me to a nice
simple HOWTO or MAN page for specifying an 'exec' script
in radiusd.conf that will set the Session-Timeout and return
it to the NAS.
I'm thinking:
Hi,
I'm thinking:
Session-Timeout := %{exec:timecalc}
pretty much, you need to set this via the update reply style as
recently posted several times this past month to the list
Or something like that. Also, where exactly should this go in the
'authorize' section? I'm presuming at the
42 matches
Mail list logo
