Hi Kevin and thanks for your time,
- "In your snmpd.conf file, do you have a line that looks like the following?
smuxpeer .1.3.6.1.4.1.3317.1.3.1 public "
+ No i hadn't in my snmpd.conf a line like the follwing : smuxpeer .1.3.6.1.4.1.3317.1.3.1 public
However when i add the line in my snmpd.conf at a random place in the file i got the same output. Do i have to write it in a specific place in the snmpd.conf ?
- "Are there any errors in your log files that might indicate a problem with your snmpd config? "
+ I checked the radiusd.log but nothing useful.
- "Does freeradius exit without error or do you press Ctrl-C to kill it? "
+ No my freeradius exits without error and i don't press Ctrl-C to kill
it.
Adreas Polyxronopoulos----- Original Message ----
From: Kevin Bonner <keb@pa.net>
To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
Sent: Friday, 12 January, 2007 6:43:04 PM
Subject: Re: freeradius-1.1.3 + snmp...
On Friday 12 January 2007 11:13, adreas Polyxronopoulos wrote:
> I have configured the radiusd.conf to support snmp
> and in snmp.conf i have set the community string to public as it is in
> snmpd.conf.
In your snmpd.conf file, do you have a line that looks like the
following?
smuxpeer .1.3.6.1.4.1.3317.1.3.1 public
Are there any errors in your log files that might indicate a problem with your
snmpd config?
> However when i am running freeradius in debugging mode :
> radiusd -X , i get the following output and the freeradius does not start.
> Why is that happening ? When i configured the radiusd.conf without snmp
> everything works perfect.
Does freeradius exit without error or do you press Ctrl-C to kill it?
Kevin Bonner