| 325 |
richard |
1 |
<html>
|
|
|
2 |
<head>
|
|
|
3 |
<title>Service-Type Help Page</title>
|
|
|
4 |
<link rel="stylesheet" href="../style.css">
|
|
|
5 |
</head>
|
|
|
6 |
<body bgcolor="#80a040" background="../images/greenlines1.gif" link="black" alink="black">
|
|
|
7 |
<center>
|
|
|
8 |
<table border=0 width=540 cellpadding=1 cellspacing=1>
|
|
|
9 |
<tr valign=top>
|
|
|
10 |
<td width=340></td>
|
|
|
11 |
<td bgcolor="black" width=400>
|
|
|
12 |
<table border=0 width=100% cellpadding=2 cellspacing=0>
|
|
|
13 |
<tr bgcolor="#907030" align=right valign=top><th><font color="white">Service-Type Help Page</font> </th></tr>
|
|
|
14 |
</table>
|
|
|
15 |
</td></tr>
|
|
|
16 |
<tr bgcolor="black" valign=top><td colspan=2>
|
|
|
17 |
<table border=0 width=100% cellpadding=12 cellspacing=0 bgcolor="#ffffd0" valign=top>
|
|
|
18 |
<tr><td>
|
|
|
19 |
<br>
|
|
|
20 |
<center>
|
|
|
21 |
<pre>
|
|
|
22 |
This Attribute indicates the type of service the user has
|
|
|
23 |
requested, or the type of service to be provided. It MAY be used
|
|
|
24 |
in both Access-Request and Access-Accept packets. A NAS is not
|
|
|
25 |
required to implement all of these service types, and MUST treat
|
|
|
26 |
unknown or unsupported Service-Types as though an Access-Reject
|
|
|
27 |
had been received instead.
|
|
|
28 |
|
|
|
29 |
Possible values are.
|
|
|
30 |
</pre>
|
|
|
31 |
<i>1 Login</i><br>
|
|
|
32 |
<i>2 Framed</i><br>
|
|
|
33 |
<i>3 Callback Login</i><br>
|
|
|
34 |
<i>4 Callback Framed</i><br>
|
|
|
35 |
<i>5 Outbound</i><br>
|
|
|
36 |
<i>6 Administrative</i><br>
|
|
|
37 |
<i>7 NAS Prompt</i><br>
|
|
|
38 |
<i>8 Authenticate Only</i><br>
|
|
|
39 |
<i>9 Callback NAS Prompt</i><br>
|
|
|
40 |
<pre>
|
|
|
41 |
The service types are defined as follows when used in an Access-
|
|
|
42 |
Accept. When used in an Access-Request, they should be considered
|
|
|
43 |
to be a hint to the RADIUS server that the NAS has reason to
|
|
|
44 |
believe the user would prefer the kind of service indicated, but
|
|
|
45 |
the server is not required to honor the hint.
|
|
|
46 |
|
|
|
47 |
Login The user should be connected to a host.
|
|
|
48 |
Framed A Framed Protocol should be started for the
|
|
|
49 |
User, such as PPP or SLIP.
|
|
|
50 |
Callback Login The user should be disconnected and called
|
|
|
51 |
back, then connected to a host.
|
|
|
52 |
Callback Framed The user should be disconnected and called
|
|
|
53 |
back, then a Framed Protocol should be started
|
|
|
54 |
for the User, such as PPP or SLIP.
|
|
|
55 |
Outbound The user should be granted access to outgoing
|
|
|
56 |
devices.
|
|
|
57 |
Administrative The user should be granted access to the
|
|
|
58 |
administrative interface to the NAS from which
|
|
|
59 |
privileged commands can be executed.
|
|
|
60 |
NAS Prompt The user should be provided a command prompt
|
|
|
61 |
on the NAS from which non-privileged commands
|
|
|
62 |
can be executed.
|
|
|
63 |
Authenticate Only Only Authentication is requested, and no
|
|
|
64 |
authorization information needs to be returned
|
|
|
65 |
in the Access-Accept (typically used by proxy
|
|
|
66 |
servers rather than the NAS itself).
|
|
|
67 |
Callback NAS Prompt The user should be disconnected and called
|
|
|
68 |
back, then provided a command prompt on the
|
|
|
69 |
NAS from which non-privileged commands can be
|
|
|
70 |
executed.
|
|
|
71 |
</pre>
|
|
|
72 |
</td></tr>
|
|
|
73 |
<tr><td align=center>
|
|
|
74 |
<a href="javascript:window.close();"><b>Close Window</b></a>
|
|
|
75 |
</td></tr>
|
|
|
76 |
</center>
|
|
|
77 |
</table>
|
|
|
78 |
</tr>
|
|
|
79 |
</table>
|
|
|
80 |
</body>
|
|
|
81 |
</html>
|