Arran Cudbard-Bell wrote:
...
> Assertion failed in event.c, line 669

  Hmm... OK.

> Happens after all the home servers have been marked as dead, and you 
> have an incoming request... though could be when it's firing off a ping 
> check event.
> Either way it's repeatable, and *only* happens when all home servers are 
> dead.

  It's a good test case.

> Also little one  with access-reject when home server fails to respond. 
> Not sent through access reject filter, though that's probably because it 
> never passes through post-auth.

  Yes.  It should really run "post-proxy-type = FAIL", or something like
that, followed by the access reject filter.

  Right now, the goal is to add the new features, make them stable, and
then touch it up around the edges.

> and finally, how do you define a binding for the snmp module.... it's 
> on, but I never explicitly bound it to anywhere :|

  snmp.conf

  FreeRADIUS connects to the SNMP daemon, and there's little else to
configure.

> unlike auth/acct that are bound with listen sections. Seems like there 
> may be a need for a small extension to listen sections
> to allow type snmp .

  No.  FreeRADIUS isn't an SNMP server.  It *registers* itself with an
SNMP server, and the SNMP server calls FreeRADIUS whenever something
needs to get done.

  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.html

Reply via email to