Re: Freeradius dies if it cant resolve clients...

J=F3hann B. Gu=F0mundsson wrote:
> I had the unfortunate experience for my radius daemon to die when it =

> couldn't
> resolve one client in clients.conf

Yes. The answer is to not use DNS names for clients. Use IP addresses.

> Is there any particular reason for radius not to spew out error message =

> to the logs and declare the client "dead" or "unresolvable "
> and continue to function or is this just bad programming....

It's intentional. It indicates that your configuration is bad or broken.

The alternative is to start up without the unresolvable client. This
list would then contain complaints from people that "the client is up,
but the server says it's unknown"... when DNS is down.

i.e. you can't please everyone all of the time.

If you don't like the behavior of the software, change it. That's why
you have source. Bad-mouthing the designers of a program because you
don't understand the full implications of a design choice is a less
useful choice than just fixing behavior you don't like.

Alan DeKok.
--
http://deployingradius.com - The web site of the book
http://deployingradius.com/blog/ - The blog
- =

List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.h=
tml