Dictionary files for HP Procurve switch?
Can anyone point me to dictionary file for an HP ProCurve 2650 switch? I've got basic authentication functioning but I don't have the information I need to get the privilege level working. Thanks, Mark
Hi, I am using HP ProCurve 2626 ( smaller version of 2650 ) and I haven't seen any dictionary files nor need for a dictionary file. MAC-Based auth is working fine with freeradius and I suppose EAP would works fine as well. Regards, Edvin Seferovic -----Original Message----- From: freeradius-users-bounces@lists.freeradius.org [mailto:freeradius-users-bounces@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Dienstag, 13. Dezember 2005 23:30 To: FreeRadius users mailing list Subject: Re: Dictionary files for HP Procurve switch? Mark Tunnell <mtunnell@livebridge.com> wrote:
Can anyone point me to dictionary file for an HP ProCurve 2650 switch?
Ask HP. I've never used one of those switches, or seen an HP dictionary. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Seferovic Edvin wrote:
Hi,
I am using HP ProCurve 2626 ( smaller version of 2650 ) and I haven't seen any dictionary files nor need for a dictionary file. MAC-Based auth is working fine with freeradius and I suppose EAP would works fine as well.
Get them from HP then post them with a bug report as a file and maybe they'll get in the next release. -- Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 Off. 325-691-1301 Cell 325-439-0533 fax 325-695-6841
Is it possible to configure freeradius to send its log files to a remote syslog server? The only reference I've found at all to syslog in the documentation is the deprecated radiusd switch -l, and that was for a local syslog process. Thanks, Mark
Mark Tunnell <mtunnell@livebridge.com> wrote:
Is it possible to configure freeradius to send its log files to a remote syslog server? The only reference I've found at all to syslog in the documentation is the deprecated radiusd switch -l, and that was for a local syslog process.
You should configure your local syslog server to send the logs to a remote syslog server. See "man syslog.conf" Alan DeKok.
How do I send radius logs to the local syslog server? The man page says the -l radiusd switch is deprecated and that you should see the log_dir configuration item in the radiusd.conf file. There is no 'log_dir' configuration item in the radiusd.conf file. There is a 'logdir' and a 'log_file'. I've tried setting those = to 'syslog' with no luck. I've tried adding a log_dir to radiusd.conf but that didn't work either. Thanks, Mark Alan DeKok wrote:
You should configure your local syslog server to send the logs to a remote syslog server.
See "man syslog.conf"
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Mark Tunnell <mtunnell@livebridge.com> writes:
How do I send radius logs to the local syslog server? The man page says the -l radiusd switch is deprecated and that you should see the log_dir configuration item in the radiusd.conf file. There is no 'log_dir' configuration item in the radiusd.conf file. There is a 'logdir' and a 'log_file'. I've tried setting those = to 'syslog' with no luck. I've tried adding a log_dir to radiusd.conf but that didn't work either.
A little grepping shows that you are right. The "-l" switch is AFAICT the only supported way to configure logging to syslog in FR 1.x, despite the comment in the man page. I guess this is something that snuck in from CVS HEAD (2.x to-be) where you can do log_destination = null | files | syslog | stdout | stderr in radiusd.conf Bjørn
Mark Tunnell:
How do I send radius logs to the local syslog server? The man page says the -l radiusd switch is deprecated and that you should see the log_dir configuration item in the radiusd.conf file. There is no 'log_dir' configuration item in the radiusd.conf file. There is a 'logdir' and a 'log_file'. I've tried setting those = to 'syslog' with no luck. I've tried adding a log_dir to radiusd.conf but that didn't work either.
I think that it somewhat depends on what you expect your logs to contain. If you set """ logdir = syslog log_file = /var/log/radius/radius.log log_auth = yes """ you get succeeded/failed auth-attempts into syslog, but some entries into radius.log: Mon Jan 16 10:42:19 2006 : Info: rlm_passwd: nfields: 3 keyfield 0(User-Name) listable: no If I remember it correctly, the docs were a bit unclear on the matter. Spent some hours getting it to work. I may not have spent too much time on it, but I don't think I ever got accounting logs into syslog to work. This is on freeradius 1.0.1, and without any commandline arguments. -- Lasse Karstensen
Hmmm... When I do that it takes syslog as a directory and complains it can't write to it. Wed Jan 25 12:17:22 2006 : Info: Starting - reading configuration files ... radiusd: Couldn't open syslog/radius.log for logging: Not a directory Mark Lasse Karstensen wrote:
I think that it somewhat depends on what you expect your logs to contain.
If you set """ logdir = syslog log_file = /var/log/radius/radius.log log_auth = yes """
participants (6)
-
Alan DeKok -
Bjørn Mork -
Lasse Karstensen -
Lewis Bergman -
Mark Tunnell -
Seferovic Edvin