hello alan, Am Freitag, 8. Juli 2005 22:37 schrieb Alan DeKok:

Gerald Krause <gk@ax.tc> wrote:

...

according to rfc2865 value 5 of attr 6 should be named "Outbound" and not "Outbound-User" (if i have read the rfc well) and that causes all my dial-out's fail after installing v1.0.4 because all users where configured with "Outbound". even though fixing was dead easy - have i misunderstood the rfc?

No. But the names are essentially irrelevant.

yes, i know.

You didn't say what you upgraded from (or if you upgraded), or if you just typed in "outbound" from the RFC's.

we have only cisco NAS's in production and all the examples on cisco.com using "outbound". since using freeradius (from 0.4 or so, livingston/cistron before) i remember that i stumbled on this more then once (after every upgrade?) but asking now the first time about some basics: i know i can easily change all my "outbound" values into "outbound-user" in order to make further upgrades simpler but i wonder if it would make sense to change the default value in the dictionary or include "outbound" in dictionary.cisco (even it looks not cisco specific because the rfc tells the same)? but i'am in doubt because i saw nobody else with this 'problem' (yea, maybe because it is not really one). are they all using "outbound-user" from beginning? do they all edit the dictionary? or nobody runs dial-out? hm, sounds more philosophic ;) ...anyway, that was my impulse to ask. -gerald

Am Samstag, 9. Juli 2005 01:44 schrieb Alan DeKok:

Gerald Krause <gk@ax.tc> wrote:

...

we have only cisco NAS's in production and all the examples on cisco.com using "outbound".

They also give ACS in their examples. Does that mean you use ACS?

do not misunderstood me: i'am not using "outbound" because of faith in cisco. not at all :). i use it because it looks rfc conform - the examples from cisco only second that. it was my fault that i stumbled again over this (because i have done the appropriate dictionary modifications more then once in the past) but this time i asked myself (and afterwards the list) for the rfc-standard...

...

but i'am in doubt because i saw nobody else with this 'problem' (yea, maybe because it is not really one). are they all using "outbound-user" from beginning?

Yes.

...ok. then i'll use it too. -gerald

The names are IRRELEVANT. The dictionaries matter only to the RADIUS server and it's configuration files. I could rename all of the attributes & valuess to random words from the dictionary, and it would make *no* difference to the clients.

To expand on what Alan was saying, for the purpose of the list archive. If you read further into the RFC it talks about how radius attributes are formed. They have 3 fieds, the type, length, and value. The type is one octect, in the case of Service-Type, it would be 6. The length is one octet and indicates the length of the Attribute. Finally, is the value field. In this field we would have what defines the value to be Outbound or Outbound-User. In the RFC, it will tell you that Outbound has a value of 5. If you look at the freeradius dictionary, it shows that Outbound-User is set to 5. If you looked at an actual radius packet with ethereal you would see the value being transferred in the packet is an integer of 5. The dictionary file merely maps that value to a name. This is so you can put something like this in the users file. DEFAULT Service-Type = Outbound-User Think of it like DNS, mapping to a user-friendly name. Otherwise, you'd have to do this. DEFAULT 6 = 5 You could easily change that dictionary file to say whatever you want. Say you changed it from: VALUE Service-Type Outbound-User 5 to: VALUE Service-Type Outbound-Monkey 5 Then in the users file, you could have this rule. DEFAULT Service-Type = Outbound-Monkey That would still make sense to your Cisco gear, because it would come across the line as a Type of 6 and a Value of 5. Hope that is helpful.