Gary Gatten wrote:
Good point about configuring multiple things at once - but that is a recipe
- right? Several ingredients that make a tasty cake?
Yes. It should be done as a recipe with multiple steps. See
http://deployingradius.com for examples.
I think it would be a pretty common
On 16/05/11 20:26, Alan DeKok wrote:
My $0.02 is that we should use github. They now support git-backed
Wikis, which use markdown. It's close enough, and has a lot of benefits.
I quite like Markdown.
We have some internal introduction to radius and introduction to
FreeRADIUS documents.
Hi John,
Just to chime in, I find all of the comments in radiusd.conf, etc.
distracting overwhelming. I strip out the comments from the files I'm
using - usually to find out how simple the configuration really is.
When I'm missing something, I refer back to the original files look up
the
John,
I believe Alan started a project to try and improve documentation in May last
year. A few documents were converted RST format, but I don't think it was ever
completed.
I'm going to suggest the same thing I did back then. Add RST support to the
Wiki, setup a well defined documentation
On 05/16/2011 02:20 PM, Arran Cudbard-Bell wrote:
John,
I believe Alan started a project to try and improve documentation in
May last year. A few documents were converted RST format, but I don't
think it was ever completed.
I'm going to suggest the same thing I did back then. Add RST support
If I knew more about it I would take my time to write some ... examples, use
cases, case studies, whatever. But, I can barely get by - each time I think I
understand something it turns out I really don't. I don't want to spread bad
info so I say nothing - usually :)
IMHO a good starting
Arran Cudbard-Bell wrote:
I believe Alan started a project to try and improve documentation in May last
year. A few documents were converted RST format, but I don't think it was
ever completed.
I received a number of patches from one person, a few from another one
or two, and nothing else.
John Dennis wrote:
Sounds like a fine plan to me. I do recall the documentation effort from
last year. But the various promises of documentation seem to wither on
the vine, the effort you cite is a perfect example. Maybe Alan's book is
the answer, but that's been promised for a long time too.
Gary Gatten wrote:
I will step up to the plate and offer up a standard format for a Recipe. I
will pick an easy deployment scenario - such as: How do I configure FR to
authenticate VTY access to my Cisco gear using AD on the backend, and users
must be a member of GroupX
That's
John Center wrote:
Just to chime in, I find all of the comments in radiusd.conf, etc.
distracting overwhelming. I strip out the comments from the files I'm
using - usually to find out how simple the configuration really is. When
I'm missing something, I refer back to the original files look
John Dennis wrote:
But all these positive attributes are sometimes negated by the
difficulty of understanding the system. Many justifiably feel
configuring FreeRADIUS is a black art. It's often been pointed out that
config files, doc directory and the wiki contains all you need to know.
There
Good point about configuring multiple things at once - but that is a recipe -
right? Several ingredients that make a tasty cake?
I think it would be a pretty common deployment scenario: lots of people have
Cisco and AD, and want to auth their Cisco admins / VTY access against AD. We
used this
On 05/16/2011 03:41 PM, Alan DeKok wrote:
organization / people / roles:
code: Alan
mgmt: Alan
docs: Alan
web site: Alan
releases: Alan
bug fixes: Alan
Wiki: Peter Nixon
Sense a theme?
I do see a theme but I also see a problem.
John Dennis wrote:
I do see a theme but I also see a problem. FreeRADIUS has gotten big
enough that 1 person, even one as amazing as you are, can't do it all. I
humbly suggest you try to offload some of the work by running this as a
project and having a team.
Sure. Volunteers?
It was
14 matches
Mail list logo
