Re: Operator-Name not being logged

Stefan Winter wrote: > That means pretty much every new RADIUS attribute will be hampered in > FreeRADIUS by their hijacking of more than half of the IETF's space! Yes. > I > noticed that in other conflicting cases, the corresponding attributes > were put into a different .conflict dictionary f

Re: Operator-Name not being logged

Hi, hm, yes... in disctionary.ascend, there's the group of X-Ascend-* attributes which aren't vendor-specifics. They clog up the *IETF* range of attributes 119-255, and X-Ascend-Temporary-Rtes occupies 126. That means pretty much every new RADIUS attribute will be hampered in FreeRADIUS by thei

[no subject]

http://penepymibasok.moy.su _ Got a phone? Get Hotmail & Messenger for mobile! http://go.microsoft.com/?linkid=9724464- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/user

User enabled for one only NAS

Hi, I've enabled on users file something like that: guest Cleartext-Password := "guest" How can I limit that user to one only NAS IP Address? Thanks in advance! -- -- Open Kairos http://www.sergiobelkin.com Watch More TV http://sebelk.blogspot.com Sergio Belkin - - List info/subscribe/unsub

"Exiting normally" on FreeBSD -- Synopsis?

All: Did anyone ever track this down? I'm assuming the consensus is that the kernel is SIGTERM'ing the process when it exceeds login_class(3) restrictions in login.conf(5) Obviously, other reports have eliminated the usual sources of signals as a cause. As for the root cause, are

Re: I have a question about freeradius-client-1.1.6.

Bryant wrote:1.6/src/radexample.c or run radlogin. > #login:test > #passoword:test > This don't authorize successfully. > When I see the server's display ,I find the password is encryped. > What should I do? Read the debug output of the server. It is TELLING YOU what the problem is, and HOW TO