Re : example dictionary entries wanted for 6929 - for new Extended Type 241.XX and Long ExtendedType 246.XX
I am new to Radius and trying to implement the extensions to RFC2865 specified in RFC6929. Are there any example dictionary entries showing how the new extensions are coded ? I am referring to, 1. Extended Type (e.g 241) 2. Long Extended Type (e.g. 245) 3. TLV 4. EVS For example, for 1. should the entry in our vendor dictionary be like, a) "ATTRIBUTE XY-NEW-EXTENDED Extended-Vendor-Specific-1.1 STRING" or b) "ATTRIBUTE XY-NEW-EXTENDED 241.1 STRING" examples for the other would be helpful as well as any references to examples / docs etc. thank you.
On Sep 27, 2019, at 12:08 PM, robert.stannard@bt.com wrote:
I am new to Radius and trying to implement the extensions to RFC2865 specified in RFC6929.
Sounds like fun. Why implement something else tho, when you can just use FreeRADIUS? :)
Are there any example dictionary entries showing how the new extensions are coded ? I am referring to, 1. Extended Type (e.g 241) 2. Long Extended Type (e.g. 245) 3. TLV 4. EVS
For example, for 1. should the entry in our vendor dictionary be like, a) "ATTRIBUTE XY-NEW-EXTENDED Extended-Vendor-Specific-1.1 STRING" or b) "ATTRIBUTE XY-NEW-EXTENDED 241.1 STRING"
examples for the other would be helpful as well as any references to examples / docs etc.
See dictionary.rfc6929 and the other dictionaries with higher RFC numbers. Alan DeKok.
Thank you Alan, I've had a look and find only one dictionary file with a few lines of examples. <<---------------------------------------- # -*- text -*- # Copyright (C) 2013 The FreeRADIUS Server project and contributors # # Attributes and values defined in RFC 6930 # http://www.ietf.org/rfc/rfc6930.txt # ATTRIBUTE IPv6-6rd-Configuration 173 tlv ATTRIBUTE IPv6-6rd-IPv4MaskLen 173.1 integer ATTRIBUTE IPv6-6rd-Prefix 173.2 ipv6prefix ATTRIBUTE IPv6-6rd-BR-IPv4-Address 173.3 ipaddr ---------------------------------------->> Would you have any other sources that I can look for for more comprehensive samples/examples and documentation ? I am interested in TLVs, evs, the extended-long-type etc... Kind Regards, Robert. P.S wasn't sure how to reply to your previous email - when I hit the reply button on my email it bounced back - so am sending this email to the general list hoping that the mail-daemon will forward it to the correct "started" thread using the header text. From: Alan DeKok-2 [via FreeRADIUS] <ml+s1045715n5755915h87@n5.nabble.com> Sent: 27 September 2019 17:44 To: Stannard,R,Robert,TLV3 C Subject: Re: example dictionary entries wanted for 6929 - for new Extended Type 241.XX and Long ExtendedType 246.XX On Sep 27, 2019, at 12:08 PM, [hidden email] wrote:
I am new to Radius and trying to implement the extensions to RFC2865 specified in RFC6929.
Sounds like fun. Why implement something else tho, when you can just use FreeRADIUS? :)
Are there any example dictionary entries showing how the new extensions are coded ? I am referring to, 1. Extended Type (e.g 241) 2. Long Extended Type (e.g. 245) 3. TLV 4. EVS
For example, for 1. should the entry in our vendor dictionary be like, a) "ATTRIBUTE XY-NEW-EXTENDED Extended-Vendor-Specific-1.1 STRING" or b) "ATTRIBUTE XY-NEW-EXTENDED 241.1 STRING"
examples for the other would be helpful as well as any references to examples / docs etc. See dictionary.rfc6929
and the other dictionaries with higher RFC numbers. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html If you reply to this email, your message will be added to the discussion below: http://freeradius.1045715.n5.nabble.com/Re-example-dictionary-entries-wanted... To unsubscribe from FreeRADIUS, click here. NAML
Robert, Just fetch the source code and use the command “grep” to list all *tlvs*. $ git clone git@github.com:FreeRADIUS/freeradius-server.git $ cd freeradius-server $ git checkout v3.0.x $ grep -i "tlv$" -r share/ --- Jorge Pereira jpereira@networkradius.com
On 30 Sep 2019, at 13:39, robert.stannard@bt.com wrote:
Thank you Alan,
I've had a look and find only one dictionary file with a few lines of examples.
<<---------------------------------------- # -*- text -*- # Copyright (C) 2013 The FreeRADIUS Server project and contributors # # Attributes and values defined in RFC 6930 # http://www.ietf.org/rfc/rfc6930.txt <http://www.ietf.org/rfc/rfc6930.txt> #
ATTRIBUTE IPv6-6rd-Configuration 173 tlv ATTRIBUTE IPv6-6rd-IPv4MaskLen 173.1 integer ATTRIBUTE IPv6-6rd-Prefix 173.2 ipv6prefix ATTRIBUTE IPv6-6rd-BR-IPv4-Address 173.3 ipaddr ---------------------------------------->>
Would you have any other sources that I can look for for more comprehensive samples/examples and documentation ? I am interested in TLVs, evs, the extended-long-type etc...
Kind Regards, Robert.
P.S wasn't sure how to reply to your previous email - when I hit the reply button on my email it bounced back - so am sending this email to the general list hoping that the mail-daemon will forward it to the correct "started" thread using the header text.
From: Alan DeKok-2 [via FreeRADIUS] <ml+s1045715n5755915h87@n5.nabble.com <mailto:ml+s1045715n5755915h87@n5.nabble.com>> Sent: 27 September 2019 17:44 To: Stannard,R,Robert,TLV3 C Subject: Re: example dictionary entries wanted for 6929 - for new Extended Type 241.XX and Long ExtendedType 246.XX
On Sep 27, 2019, at 12:08 PM, [hidden email] wrote:
I am new to Radius and trying to implement the extensions to RFC2865 specified in RFC6929.
Sounds like fun. Why implement something else tho, when you can just use FreeRADIUS? :)
Are there any example dictionary entries showing how the new extensions are coded ? I am referring to, 1. Extended Type (e.g 241) 2. Long Extended Type (e.g. 245) 3. TLV 4. EVS
For example, for 1. should the entry in our vendor dictionary be like, a) "ATTRIBUTE XY-NEW-EXTENDED Extended-Vendor-Specific-1.1 STRING" or b) "ATTRIBUTE XY-NEW-EXTENDED 241.1 STRING"
examples for the other would be helpful as well as any references to examples / docs etc. See dictionary.rfc6929
and the other dictionaries with higher RFC numbers.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
If you reply to this email, your message will be added to the discussion below: http://freeradius.1045715.n5.nabble.com/Re-example-dictionary-entries-wanted... <http://freeradius.1045715.n5.nabble.com/Re-example-dictionary-entries-wanted-for-6929-for-new-Extended-Type-241-XX-and-Long-ExtendedType-246X-tp5755914p5755915.html> To unsubscribe from FreeRADIUS, click here. NAML
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
Thank you Jorge, I have the source already available locally so used your grep command to do the search and did find many tlv examples. So thank you for that. Can you please tell me then, how to distinguish between tlv and extended-type since both can be represented in dot notation i.e. xxx.1, xxx.2 Also I doing a search using the grep command I couldn't find any examples of any of the other new data-types documented as part of the radius extensions RFC6929. ________________________________________ From: Freeradius-Users <freeradius-users-bounces+robert.stannard=bt.com@lists.freeradius.org> on behalf of Jorge Pereira <jpereira@freeradius.org> Sent: 30 September 2019 17:55 To: FreeRadius users mailing list Subject: Re: example dictionary entries wanted for 6929 - for new Extended Type 241.XX and Long ExtendedType 246.XX Robert, Just fetch the source code and use the command “grep” to list all *tlvs*. $ git clone git@github.com:FreeRADIUS/freeradius-server.git $ cd freeradius-server $ git checkout v3.0.x $ grep -i "tlv$" -r share/ --- Jorge Pereira jpereira@networkradius.com
On Sep 30, 2019, at 1:04 PM, <robert.stannard@bt.com> <robert.stannard@bt.com> wrote:
I have the source already available locally so used your grep command to do the search and did find many tlv examples. So thank you for that.
Is it really that amazing to use "grep?" Honestly, that's a bit surprising.
Can you please tell me then, how to distinguish between tlv and extended-type since both can be represented in dot notation i.e. xxx.1, xxx.2
Also I doing a search using the grep command I couldn't find any examples of any of the other new data-types documented as part of the radius extensions RFC6929.
It's simple: a) you are creating a FreeRADIUS dictionary. If so, just create the dictionary. It's not difficult. There are examples and documentation. If you have specific questions about it, ask. We can help. b) you are trying to understand RADIUS in general, *outside* of FreeRADIUS. In which case we can't help you. You should do what we did: learn. This list is for FreeRADIUS. Not for general RADIUS Q&A. Alan DeKok.
On Sep 30, 2019, at 12:39 PM, robert.stannard@bt.com wrote:
I've had a look and find only one dictionary file with a few lines of examples.
Then you're looking at an old version of the server.
<<---------------------------------------- # -*- text -*- # Copyright (C) 2013 The FreeRADIUS Server project and contributors
There have been many new dictionaries since then: $ ls share/dictionary.rfc7* share/dictionary.rfc7055 share/dictionary.rfc7268 share/dictionary.rfc7930 share/dictionary.rfc7155 share/dictionary.rfc7499
Would you have any other sources that I can look for for more comprehensive samples/examples and documentation ? I am interested in TLVs, evs, the extended-long-type etc...
I've never understood this question. You're really asking if we have super-secret examples that we *don't* ship with the server? Examples that we give out only if people ask "pretty please" for them? Everything we have is shipped with the server. It's that simple. If you're looking for something specific, ask. Or read the code. But this isn't difficult. The dictionaries in v3 are in the share/dictionarr.rfc* files. There's no magic. Alan DeKok.
participants (3)
-
Alan DeKok -
Jorge Pereira -
robert.stannard＠bt.com