RFC5607 support on Freeradius

[Frank Wei]

Hi,

Thanks Arran.

We are using freeradius 2.2.5. Does 2.2.5 support RFC5607?

Cheers,

-----Original Message-----
From: freeradius-users-bounces+frank.wei=4rf.com at lists.freeradius.org [mailto:freeradius-users-bounces+frank.wei=4rf.com at lists.freeradius.org] On Behalf Of Arran Cudbard-Bell
Sent: Friday, 17 October 2014 4:47 p.m.
To: FreeRadius users mailing list
Subject: Re: RFC5607 support on Freeradius


On 16 Oct 2014, at 22:28, Frank Wei <Frank.Wei at 4rf.com> wrote:

> RFC5607

# -*- text -*-
# Copyright (C) 2011 The FreeRADIUS Server project and contributors #
#       Attributes and values defined in RFC 5607.
#       http://www.ietf.org/rfc/rfc5607.txt
#
#       $Id: 5ec1ad78888ae44a00f4159743b6cc6fc56fb89a $
#

VALUE   Service-Type                    Framed-Management       18

ATTRIBUTE       Framed-Management                       133     integer

VALUE   Framed-Management               SNMP                    1
VALUE   Framed-Management               Web-Based               2
VALUE   Framed-Management               Netconf                 3
VALUE   Framed-Management               FTP                     4
VALUE   Framed-Management               TFTP                    5
VALUE   Framed-Management               SFTP                    6
VALUE   Framed-Management               RCP                     7
VALUE   Framed-Management               SCP                     8

ATTRIBUTE       Management-Transport-Protection         134     integer

VALUE   Management-Transport-Protection No-Protection           1
VALUE   Management-Transport-Protection Integrity-Protection    2
VALUE   Management-Transport-Protection Integrity-Confidentiality-Protection 3

ATTRIBUTE       Management-Policy-Id                    135     string

ATTRIBUTE       Management-Privilege-Level              136     integer

Arran Cudbard-Bell <a.cudbardb at freeradius.org> FreeRADIUS development team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).