⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2866.txt

📁 gnu 的radius服务器很好用的
💻 TXT
📖 第 1 页 / 共 4 页
字号:
RFC 2866                   RADIUS Accounting                   June 20005.4.  Acct-Output-Octets   Description      This attribute indicates how many octets have been sent to the      port in the course of delivering this service, and can only be      present in Accounting-Request records where the Acct-Status-Type      is set to Stop.   A summary of the Acct-Output-Octets attribute format is shown below.   The fields are transmitted from left to right.    0                   1                   2                   3    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |             Value   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              Value (cont)         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   Type      43 for Acct-Output-Octets.   Length      6   Value      The Value field is four octets.5.5.  Acct-Session-Id   Description      This attribute is a unique Accounting ID to make it easy to match      start and stop records in a log file.  The start and stop records      for a given session MUST have the same Acct-Session-Id.  An      Accounting-Request packet MUST have an Acct-Session-Id.  An      Access-Request packet MAY have an Acct-Session-Id; if it does,      then the NAS MUST use the same Acct-Session-Id in the Accounting-      Request packets for that session.      The Acct-Session-Id SHOULD contain UTF-8 encoded 10646 [7]      characters.Rigney                       Informational                     [Page 15]RFC 2866                   RADIUS Accounting                   June 2000      For example, one implementation uses a string with an 8-digit      upper case hexadecimal number, the first two digits increment on      each reboot (wrapping every 256 reboots) and the next 6 digits      counting from 0 for the first person logging in after a reboot up      to 2^24-1, about 16 million.  Other encodings are possible.   A summary of the Acct-Session-Id attribute format is shown below.   The fields are transmitted from left to right.    0                   1                   2    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |  Text ...   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   Type      44 for Acct-Session-Id.   Length      >= 3   String      The String field SHOULD be a string of UTF-8 encoded 10646 [7]      characters.5.6.  Acct-Authentic   Description      This attribute MAY be included in an Accounting-Request to      indicate how the user was authenticated, whether by RADIUS, the      NAS itself, or another remote authentication protocol.  Users who      are delivered service without being authenticated SHOULD NOT      generate Accounting records.   A summary of the Acct-Authentic attribute format is shown below.  The   fields are transmitted from left to right.    0                   1                   2                   3    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |             Value   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              Value (cont)         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Rigney                       Informational                     [Page 16]RFC 2866                   RADIUS Accounting                   June 2000   Type      45 for Acct-Authentic.   Length      6   Value      The Value field is four octets.      1      RADIUS      2      Local      3      Remote5.7.  Acct-Session-Time   Description      This attribute indicates how many seconds the user has received      service for, and can only be present in Accounting-Request records      where the Acct-Status-Type is set to Stop.   A summary of the Acct-Session-Time attribute format is shown below.   The fields are transmitted from left to right.    0                   1                   2                   3    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |             Value   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              Value (cont)         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   Type      46 for Acct-Session-Time.   Length      6   Value      The Value field is four octets.Rigney                       Informational                     [Page 17]RFC 2866                   RADIUS Accounting                   June 20005.8.  Acct-Input-Packets   Description      This attribute indicates how many packets have been received from      the port over the course of this service being provided to a      Framed User, and can only be present in Accounting-Request records      where the Acct-Status-Type is set to Stop.   A summary of the Acct-Input-packets attribute format is shown below.   The fields are transmitted from left to right.    0                   1                   2                   3    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |             Value   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              Value (cont)         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   Type      47 for Acct-Input-Packets.   Length      6   Value      The Value field is four octets.5.9.  Acct-Output-Packets   Description      This attribute indicates how many packets have been sent to the      port in the course of delivering this service to a Framed User,      and can only be present in Accounting-Request records where the      Acct-Status-Type is set to Stop.   A summary of the Acct-Output-Packets attribute format is shown below.   The fields are transmitted from left to right.Rigney                       Informational                     [Page 18]RFC 2866                   RADIUS Accounting                   June 2000    0                   1                   2                   3    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |             Value   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              Value (cont)         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   Type      48 for Acct-Output-Packets.   Length      6   Value      The Value field is four octets.5.10.  Acct-Terminate-Cause   Description      This attribute indicates how the session was terminated, and can      only be present in Accounting-Request records where the Acct-      Status-Type is set to Stop.   A summary of the Acct-Terminate-Cause attribute format is shown   below.  The fields are transmitted from left to right.    0                   1                   2                   3    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |     Type      |    Length     |             Value   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              Value (cont)         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Rigney                       Informational                     [Page 19]RFC 2866                   RADIUS Accounting                   June 2000   Type      49 for Acct-Terminate-Cause   Length      6   Value      The Value field is four octets, containing an integer specifying      the cause of session termination, as follows:      1       User Request      2       Lost Carrier      3       Lost Service      4       Idle Timeout      5       Session Timeout      6       Admin Reset      7       Admin Reboot      8       Port Error      9       NAS Error      10      NAS Request      11      NAS Reboot      12      Port Unneeded      13      Port Preempted      14      Port Suspended      15      Service Unavailable      16      Callback      17      User Error      18      Host Request      The termination causes are as follows:      User Request         User requested termination of service, for                           example with LCP Terminate or by logging out.      Lost Carrier         DCD was dropped on the port.      Lost Service         Service can no longer be provided; for                           example, user's connection to a host was                           interrupted.      Idle Timeout         Idle timer expired.      Session Timeout      Maximum session length timer expired.      Admin Reset          Administrator reset the port or session.Rigney                       Informational                     [Page 20]RFC 2866                   RADIUS Accounting                   June 2000      Admin Reboot         Administrator is ending service on the NAS,                           for example prior to rebooting the NAS.      Port Error           NAS detected an error on the port which                           required ending the session.      NAS Error            NAS detected some error (other than on the                           port) which required ending the session.      NAS Request          NAS ended session for a non-error reason not                           otherwise listed here.      NAS Reboot           The NAS ended the session in order to reboot                           non-administratively ("crash").      Port Unneeded        NAS ended session because resource usage fell                           below low-water mark (for example, if a                           bandwidth-on-demand algorithm decided that                           the port was no longer needed).      Port Preempted       NAS ended session in order to allocate the                           port to a higher priority use.      Port Suspended       NAS ended session to suspend a virtual                           session.      Service Unavailable  NAS was unable to provide requested service.      Callback             NAS is terminating current session in order                           to perform callback for a new session.      User Error           Input from user is in error, causing                           termination of session.      Host Request         Login Host terminated session normally.5.11.  Acct-Multi-Session-Id   Description      This attribute is a unique Accounting ID to make it easy to link      together multiple related sessions in a log file.  Each session      linked together would have a unique Acct-Session-Id but the same      Acct-Multi-Session-Id.  It is strongly recommended that the Acct-      Multi-Session-Id contain UTF-8 encoded 10646 [7] characters.   A summary of the Acct-Session-Id attribute format is shown below.   The fields are transmitted from left to right.Rigney                       Informational                     [Page 21]

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -