12 Jun
2015
12 Jun
'15
10:12 a.m.
Hello, I am using version freeradius-server-3.0.8, it's only from version 3.x that that the rfc6929 is supported. Kind regards, Katrien. -----Original Message----- From: Freeradius-Users [mailto:freeradius-users-bounces+katrien.vereecke=alcatel-lucent.com@lists.freeradius.org] On Behalf Of Jorge Pereira Sent: Friday, June 12, 2015 16:10 To: FreeRadius users mailing list Subject: Re: how do I define in my dictionary the vendor of format Extended-Vendor-Specific-1 What the version of your Radius? -- Jorge Pereira On Fri, Jun 12, 2015 at 10:57 AM, Vereecke, Katrien (Katrien) < katrien.vereecke@alcatel-lucent.com> wrote: > Hello, > > What you explain is for a normal format vendorID, the problem is that > I want my vendor ID according to the rfc6929, in dotted format : 241.26.6527 > VENDOR Alcatel-IPD-Ext-1 241.26.6527 (=> 241.26 is as > defined in dictionary.rfc6929 and 6527 is my vendorID.) > BEGIN-VENDOR Alcatel-IPD-Ext-1 > ATTRIBUTE Alc-Ext-TestAttr-1 1 integer > END-VENDOR Alcatel-IPD-Ext-1 > > This is not working, if I specify it like this, my radius packet are > not in the correct format according rfc6929, it's still the old way of > VSA's like RFC 2865. > How do I indicate in my dictionary that the vendor must be in the > format Extended-Vendor-Specific-1? > > Kind regards, > Katrien. > -----Original Message----- > From: Freeradius-Users > [mailto:freeradius-users-bounces+katrien.vereecke= > alcatel-lucent.com@lists.freeradius.org] On Behalf Of Jorge Pereira > Sent: Friday, June 12, 2015 15:43 > To: FreeRadius users mailing list > Subject: Re: how do I define in my dictionary the vendor of format > Extended-Vendor-Specific-1 > > Hi, > > trust me, is more easy that you can imagine... my sugestion is: > > # cd /etc/freeradius > > the below dictionary.. is a smal/simple example to be based. > > # cp /usr/share/dictionary.zyxel dictionary.blable > > Open the file dictionary.blable and change the number of VENDOR for > your preference. and change/add/remove the attributes that you need.... save. > > # echo '$INCLUDE dictionary.blable' >> dictionary > > done... now you can use your custom dictionary... remember that you > need to have the same dicionary in the other side that will > send/receive the requests. > > -- > Jorge Pereira > > On Fri, Jun 12, 2015 at 7:24 AM, Vereecke, Katrien (Katrien) < > katrien.vereecke@alcatel-lucent.com> wrote: > > > Hello, > > > > I am using freeradius-server-3.0.8. > > > > I am trying to use the extended-vendor-sepcific-1 attribute as > > specified in RC6929. > > > > How can I indicate in my dictionary that the vendor must be > > according to the extended-vendor-specific format? > > > > I added the following in a new dictionary file: > > VENDOR Alcatel-IPD-Ext-1 241.26.6527 > > > > BEGIN-VENDOR Alcatel-IPD-Ext-1 > > ATTRIBUTE Alc-Ext-TestAttr-1 1 integer > > END-VENDOR Alcatel-IPD-Ext-1 > > > > This gives no problems when starting the radius server, but the > > attribute is not sent in the extended-vendor-specific format but > > still in the old way VSA. > > > > I found in the http://freeradius.org/radiusd/man/dictionary.txt that : > > > > "You can also use "format=Extended-Vendor-Specific-1", through > > "format=Extended-Vendor-Specific-6". These define VSAs in the > > "extended vendor-specific" space" > > > > but this gives errors : > > Errors reading dictionary: dict_init: > > /usr/local/share/freeradius/dictionary.alcatel.sr.ext[15]: Invalid > > format for VENDOR. Expected text like "1,1", got > "Extended-Vendor-Specific-1" > > > > Could you please help in how this should be done? > > > > Thanks. > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html