Chapter 15: Customizing the public access interface194
DRAFT
Source code for the internal pages
This section presents commented source code for the default internal pages.
Important: Do not create your own pages by saving a page from within your web
browser. The server side code is removed when you do this and the resulting
pages will not work. Use the examples in this section or those on the CD in
\HTML\Colubris\Internal as the basis for your pages.
// Define the size of your remote window in pixels with "width" and "height."
remote =
window.open("","sessionwin","width=240,height=400,toolbar=0,location=0,directories=0,status=0,me
nubar=0,scrollbars=1,resizable=1");
if (remote.blur) remote.focus();
// Put the full url of your remote document where you see "URL".
remote.location.href = "<%GetSessionUrl();%>";
Chapter 15: Customizing the public access interface197
<font face="verdana, arial, helvetica" size="2">
<h4>This should take 1 second...</h4>
If you are not redirected within a few seconds, please <a href="<%GetWelcomeUrl();%>">click here</
a>.
If you have JavaScript disabled and the session page doesn't appear, please <a
href="<%GetSessionUrl();%>">click here</a>.
Chapter 15: Customizing the public access interface200
DRAFT
Source code for the external pages
Sample external pages are provided on the CD in the folder
\HTML\Colubris\External. Three versions are included for each page: HTML,
ASP, and PHP.
Welcome page
HTML
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling welcome-url is:
welcome-url=https://207.35.116.198:8888/colubris-php/
welcome.php?site=%s&user=%u&wantedurl=%o
-->
<html>
<head>
<title>Welcome</title>
</head>
<body>
Welcome
</body>
</html>
ASP
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling welcome-url is:
welcome-url=https://207.35.116.198:8888/colubris-php/
welcome.php?site=%s&user=%u&wantedurl=%o
-->
<%@ Language=VBScript %>
<%
site = Request("site")
user = Request("user")
wantedurl = Request("wantedurl")
%>
<html>
<head>
<title>Welcome</title>
</head>
<body>
Welcome <%=user%>, to <%=site%>
<br>
The URL you were trying to access was <a href="<%=wantedurl%>"><%=wantedurl%></a>.
</body>
</html>
Chapter 15: Customizing the public access interface201
DRAFT
PHP
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling welcome-url is:
welcome-url=https://207.35.116.198:8888/colubris-php/
welcome.php?site=%s&user=%u&wantedurl=%o
-->
<? /*
PHP makes QUERY STRING variables immediatly available to any
PHP scripts you embed in your file.
*/ ?>
<html>
<head>
<title>Welcome</title>
</head>
<body>
Welcome <? echo $user; ?>, to <? echo $site; ?>
<br>
The URL you were trying to access was <a href="<? echo $wantedurl; ?>"><? echo $wantedurl; ?></
a>.
Goodbye page
</body>
</html>
HTML
<!-This file remains on your webserver and is fully customisable by you.
For example, in this file the calling goodbye-url is:
goodbye-url=https://207.35.116.198:8888/colubris-php/goodbye.php?site=%s&user=%u
-->
<html>
<head>
<title>Logout</title>
</head>
<body>
Thank you.
</body>
</html>
ASP
<!-This file remains on your webserver and is fully customisable by you.
For example, in this file the calling goodbye-url is:
goodbye-url=https://207.35.116.198:8888/colubris-php/goodbye.php?site=%s&user=%u
-->
<%@ Language=VBScript %>
<%
site = Request("site")
user = Request("user")
Chapter 15: Customizing the public access interface202
wantedURL = Request("wantedURL")
%>
<html>
<head>
<title>Logout</title>
</head>
<body>
Thank you <%=user%>
</body>
</html>
DRAFT
PHP
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling goodbye-url is:
goodbye-url=https://207.35.116.198:8888/colubris-php/goodbye.php?site=%s&user=%u
-->
Login Error page
<? /*
PHP makes QUERY STRING variables immediatly available to any
PHP scripts you embed in your file.
*/ ?>
<html>
<head>
<title>Logout</title>
</head>
<body>
Thank you <? echo $user; ?>.
</body>
</html>
HTML
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling login-err-url is:
login-err-url=https://207.35.116.198:8888/colubris-php/login-error.php?site=%s&user=%u
-->
<html>
<head>
<title>Login Error</title>
</head>
<body>
There has been a login error.
Chapter 15: Customizing the public access interface203
</body>
</html>
DRAFT
ASP
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling login-err-rl is:
login-err-url=https://207.35.116.198:8888/colubris-php/login-error.php?site=%s&user=%u
-->
<%@ Language=VBScript %>
<%
site = Request("site")
user = Request("user")
wantedurl = Request("wantedurl")
%>
<html>
<head>
<title>Login Error</title>
</head>
<body>
Sorry <%=user%><br>
There has been a login error.
</body>
</html>
PHP
<!-This file remains on your webserver and is fully customisable by you.
You also have access to the CGI variables which are defined in the URL
that calls this page.
For example, in this file the calling login-err-url is:
login-err-url=https://207.35.116.198:8888/colubris-php/login-error.php?site=%s&user=%u
-->
<? /*
PHP makes QUERY STRING variables immediately available to any
PHP scripts you embed in your file.
*/ ?>
<html>
<head>
<title>Login Error</title>
</head>
<body>
Sorry <? echo $user; ?>.<br>
There has been a login error.
</body>
</html>
Chapter 15: Customizing the public access interface204
DRAFT
Remote login page
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<meta http-equiv="Expires" CONTENT="0">
<meta http-equiv="Cache-Control" CONTENT="no-cache">
<meta http-equiv="Pragma" CONTENT="no-cache">
<title>Login</title>
Chapter 15: Customizing the public access interface206
DRAFT
Chapter 16: Customizing CN3200 and customer settings207
Chapter 16: Customizing CN3200 and customer settings
DRAFT
Chapter 16
Customizing CN3200 and customer settings
This chapter presents a summary of the configuration settings you can
define to customize the operation of your public access network and
customer accounts.
Chapter 16: Customizing CN3200 and customer settings208
DRAFT
Overview
The CN3200 uses a third-party RADIUS server to store configuration settings for
customer accounts, accounting data, as well as certain operating settings for the
public access network. The configuration settings are stored in profiles, which
you must create before the public access interface can be used.
The minimum setup you must define is as follows:
• Define RADIUS client settings for the CN3200
Any device that uses the authentication services of a RADIUS server is called
a RADIUS client. Therefore, each CN3200 is considered to be a RADIUS client
and you must define client settings for each one that you intend to install.
See page 213 for details.
• Create a RADIUS profile for the CN3200
Before it can activate the public access interface, the CN3200 must log into a
RADIUS server and retrieve certain operating settings which you must define.
Therefore, you must create at least one RADIUS profile for use by the CN3200.
If you have multiple CN3200s, they can all be associated with a single RADIUS
profile.
See page 214 for details.
• Create a RADIUS profile for one or more customers
The customer profile is used to authenticate customers when they login. It
contains settings that define the characteristics of their account.
Chapter 16: Customizing CN3200 and customer settings209
DRAFT
RADIUS attributes
Attributes are configuration parameters that you can attach to a RADIUS profile.
The CN3200 supports standard RADIUS attributes and a Colubris Networks
vendor-specific attribute.
Standard RADIUS
attributes
The CN3200 supports the following RADIUS attributes. (Attributes starting with
MS are Microsoft and are not standard.)
Access Request
• Acct-Session-Id
• NAS-Port
• NAS-Port-Type
• User-Name
• Calling-Station-Id
• Called-Station-Id
• User-Password
• CHAP-Password
• CHAP-Challenge
• MSCHAP-Challenge
• MSCHAP-Response
• MSCHAPv2-Response
• EAP-Message
• State
• NAS-Identifier
• NAS-Ip-Address
• Framed-MTU
• Connect-Info
• Service-Type
• Message-Authenticator
Access Accept
• MS-MPPE-Recv-Key
• MS-MPPE-Send-Key
• Service-Type
• EAP-Message
• Class
• Idle-Timeout
• Session-Timeout
• Acct-Interim-Interval
• Tunnel-type
• Tunnel-meduim-type
• Tunnel-private-group
Access Reject
• MSCHAP-Error
• Reply-Message
• EAP-Message
Access Challenge
• EAP-Message
• State
Accounting Request
•User-Name
• NAS-Port
• NAS-Port-Type
• NAS-Identifier
• NAS-Ip-Address
• Acct-Status-Type
• Calling-Station-Id
• Called-Station-Id
• Acct-Event-Timestamp
• Acct-Delay-Time
• Acct-Session-Id
• Acct-Authentic
• Acct-Session-Time
• Acct-Input-Octets
• Acct-Input-Gigawords
• Acct-Input-Packets
• Acct-Output-Octets
• Acct-Output-Gigawords
• Acct-Output-Packets
• Acct-Terminate-Cause
• Class
• Framed-Ip-Address
Accounting Response
• No attribute
Interim accounting updates
To enable interim accounting updates for each customer you must define a value
for the RADIUS attribute Acct-Interim-Interval. This sets the frequency with which
the CN3200 will send accounting information to the RADIUS server.
Chapter 16: Customizing CN3200 and customer settings210
DRAFT
Colubris Networks
vendor-specific
attributes
In certain cases, the set of standard RADIUS attributes needs to be extended to
specify custom settings for specific types of equipment. These are called vendorspecific attributes. Colubris Networks has defined two vendor-specific attributes
to support special features on the CN3200, such as the customization of the web
interface and the security certificate. This attribute are:
• Colubris-AVPair
• Colubris-Intercept
These attributes conform to RADIUS RFC 2865.
You may need to define these attributes on your RADIUS server if they are not
already present. In this case, you need to specify the following:
The following values are permitted for the Colubris-AVPair attribute. These
values are described in greater detail later in this chapter and in Chapter 15.
Important: It is important to specify the attribute values exactly as shown below.
Adding extra spaces between options will result in errors.
Chapter 16: Customizing CN3200 and customer settings211
DRAFT
RADIUS limitations
The maximum number of attributes the CN3200 can receive in one request is
limited by the maximum packet size of the UDP protocol which is 64K. Some
networks may drop fragmented UDP packets which may leave you with less than
the maximum size.
Chapter 16: Customizing CN3200 and customer settings212
DRAFT
Terminate-AcctCause values
Terminate Acct Cause values are supported as follows:
IDCauseNotes
1User RequestSupported. Indicates that the customer logged
out.
2Lost Carrier Supported. Indicates that the client station is no
longer alive.
4Idle TimeoutSupported. Customer exceeded the idle timeout
value defind for the session.
5Session TimeoutSupported. Customer exceeded maximum time
defined for the session.
6Admin ResetSupported. Customer session was terminated by
the CN3200 administrator via SNMP or the
management tool.
7Admin RebootNot Supported. (not applicable)
8Port ErrorSupported. If two customers are detected using
the same IP address, both are logged out with
this error. Another cause is if an error is
encountered in an access list definition. For
example, an invalid host was specified.
9NAS ErrorNot Supported. (not applicable)
10NAS RequestNot Supported. (not applicable)
11NAS RebootSupported. Customer was logged out because
the CN3200 was restarted.
12Port UnneededNot Supported. (not applicable)
13Port PreemptedNot Supported. (not applicable)
14Port SuspendedNot Supported. (not applicable)
15Service
Unavailable
16CallbackNot Supported. (not applicable)
17User ErrorSupported. An 801.1x client initiated a second
18Host RequestNot Supported. (not applicable)
0x8744
(34628
decimal)
TerminationColubris-specific termination cause. See page
Not Supported. (not applicable)
authentication request for a customer, and this
request was refused.
229 for details.
Chapter 16: Customizing CN3200 and customer settings213
DRAFT
Creating a RADIUS client entry for the CN3200
Any device that uses the authentication services of a RADIUS server is called a
RADIUS client (or RAS client on some systems). Therefore, each CN3200 is
considered to be a RADIUS client and you must define client settings for each
one that you intend to install.
Configuration
settings
Managing shared
secrets
You may need to supply the following information when setting up a RADIUS
client entry:
• Client IP address: This is the IP address assigned to the CN3200’s Internet
port. If the CN3200 is using a PPTP connection to communicate with the
RADIUS server, then this is the address assigned to the CN3200 by the PPTP
server.
• Shared secret: Secret the CN3200 will use to authenticate the packets it
receives from the RADIUS server.
If you are using a PPPoE, DHCP, or PPTP VPN connection when communicating
with the RADIUS server, make sure that the shared secret for each CN3200 is
the same. Also, ensure that all possible IP addresses have been configured on
the RADIUS server.
The username and password assigned to each CN3200 can be different,
enabling you to differentiate between devices.
Chapter 16: Customizing CN3200 and customer settings214
DRAFT
Creating a profile for the CN3200 on the RADIUS server
Before it can activate the public access interface, the CN3200 must log into a
RADIUS server and retrieve certain operating settings that you must define.
Therefore, you must create at least one RADIUS profile for use by the CN3200. If
you have multiple CN3200s, they can all be associated with a single RADIUS
profile.
Supported standard
RADIUS attributes
This section presents all standard RADIUS attributes that are supported by a
CN3200 profile.
Note: In the following definitions, strings are defined as 1 to 253 characters in
length.
Access request
• Acct-Session-Id (32-bit unsigned integer): Random value generated per
authentication by the CN3200.
• NAS-Identifier (string): The NAS ID set on the Security > RADIUS page for the
RADIUS profile being used.
• NAS-Ip-Address 32-bit unsigned integer): The IP address of the port the
CN3200 is using to communicate with the RADIUS server.
• NAS-Port (32-bit unsigned integer): Always 0.
• NAS-Port-Type (32-bit unsigned integer): Always set to 19, which represents
WIRELESS_802_11.
• Calling-Station-Id (string): The MAC address of the CN3200’s LAN port in IEEE
format. For example: 00-02-03-5E-32-1A.
• Called-Station-Id (string): The MAC address of the CN3200’s LAN port in IEEE
format. For example: 00-02-03-5E-32-1A.
• User-Name (string): The username assigned to the CN3200 on the Security >
Authentication page.
• User-Password (string): The password assigned to the CN3200 on the
Security > Authentication page. Encoded as defined in RFC 2865. Only
present when the authentication method for the RADIUS profile is set to PAP.
• CHAP-Password (string): The password assigned to the CN3200 on the
Security > Authentication page. Encoded as defined in RFC 2865. Only
present when the authentication method for the RADIUS profile is set to CHAP.
• CHAP-Challenge (string): Randomly generated by the product. As defined in
RFC 2865. Only present when the authentication method for the RADIUS
profile is set to CHAP. Length = 19 bytes.
• MSCHAP-Challenge (string): As defined in RFC 2433. Only present when the
authentication method for the RADIUS profile is set to MSCHAPv1 or
MSCHAPv2. Length = 8 bytes.
• MSCHAP-Response (string): As defined in RFC 2433. Only present when the
authentication method for the RADIUS profile is set to MSCHAPv1. Length =
49 bytes.
• MSCHAPv2-Response (string): As defined in RFC 2759. Only present when
the authentication method for the RADIUS profile is set to MSCHAPv2. Length
= 49 bytes.
• EAP-Message (string): As defined in RFC 2869. Only present when the
authentication method for the RADIUS profile is set to EAP-MD5.
Chapter 16: Customizing CN3200 and customer settings215
• State (string): As defined in RFC 2865.
• Framed-MTU (32-bit unsigned integer): Hard-coded to 1496.
• Connect-Info (string): The string "HTTPS".
• Service-Type (32-bit unsigned integer): As defined in the config.cfg file. Token
name = service-type-device.
• Message-Authenticator (string): As defined in RFC 2869. Always present even
when not doing an EAP authentication. length = 16 bytes.
• Colubris-AVPair: See the description in the section that follows.
DRAFT
Access accept
• Acct-Interim-Interval (32-bit unsigned integer): When present, it enables the
transmission of RADIUS accounting requests of the Interim Update type.
Specify the number of seconds between each transmission.
• Session-Timeout (32-bit unsigned integer): Maximum time a session can be
active. The CN3200 re-authenticates itself when this timer expires. Omitting
this attribute or specifying 0 will disable the feature. (Note that the
authentication interval is also configurable on the Security > Authentication
page.
• Idle-Timeout (32-bit unsigned integer): Not supported.
• Class (string): As defined in RFC 2865.
• EAP-Message (string): Only supported when authentication is EAP-MD5. Note
that the content will not be read as the RADIUS Access Accept is overriding
whatever indication contained inside this packet.
• Colubris-AVPair: See the description in the section that follows.
Access reject
None.
Access challenge
None.
Accounting request
Accounting information is generated by default. To disable accounting support,
open the Security > Authentication -> Advanced Settings page.
• Acct-Session-Id (32-bit unsigned integer): Random value generated by the
CN3200.
• NAS-Identifier (string): The NAS ID set on the Security > RADIUS page for the
profile being used.
• NAS-Ip-Address (32-bit unsigned integer): The IP address of the port the
CN3200 is using to communicate with the RADIUS server.
• NAS-Port (32-bit unsigned integer): Always 0.
• NAS-Port-Type (32-bit unsigned integer): Always set to 19, which represents
WIRELESS_802_11.
• Calling-Station-Id (string): The MAC address of the CN3200’s LAN port in IEEE
format. For example: 00-02-03-5E-32-1A.
• Called-Station-Id (string): The MAC address of the CN3200’s LAN port in IEEE
format. For example: 00-02-03-5E-32-1A.
Chapter 16: Customizing CN3200 and customer settings216
• User-Name (string): The RADIUS username assigned to the CN3200 on the
Security > Authentication page.
• Class (string). As defined in RFC 2865.
• Framed-IP-Address (32-bit unsigned integer): IP Address of the CN3200’s LAN
port.
• Acct-Status-Type (32-bit unsigned integer): Supported values are Accounting-
On (7) and Accounting-Off (8).
• Acct-Event-Timestamp (32-bit unsigned integer): As defined in RFC 2869.
• Acct-Delay-Time (32-bit unsigned integer): As defined in RFC 2869.
• Acct-Authentic (32-bit unsigned integer): Always set to 1 which means
RADIUS.
DRAFT
Accounting response
None.
Colubris-AVPair
attribute
For each CN3200 profile you can specify one or more instances of a ColubrisAVPair attribute that will be returned upon successful authentication (RADIUS
Accept). Possible values for all instance are grouped into the following
categories:
FeatureDescription
Custom HTML pages and
URLs, and supporting files
Access listEnables you to create one or more access
White listThe white list defines the set of network
Custom security certificateEnables you to replace the Colubris Networks
Configuration fileEnables you to store a configuration file at a
MAC authenticationEnables you to authenticate devices based on
Enables you to customize the public access
interface. See Chapter 15 for details.
groups which define the set of network
resources that are available to authenticated
customers.
resources that are available to customers before
they are authenticated.
certificate with your own.
central location to automatically update all your
CN3200s.
their MAC addresses.
Access lists
Default user idle timeoutDefault idle timeout for all customers.
Default user session timeoutDefault session timeout for all customers.
Default SMTP serverDefault SMTP server to use for email redirection.
The value of a Colubris-AVPair attribute is always a string. These strings are
always of the form: <item>=<value>
Access lists enable you to create public areas on your network that all customers
can browse, and protected areas that are restricted to specific customer
accounts or groups.
Chapter 16: Customizing CN3200 and customer settings217
DRAFT
Each access list is a set of rules that governs how the CN3200 controls access to
network resources. You can create multiple access lists, each with multiple rules
to manage the traffic on your public access network.
Default setting
By default no access lists are defined. This means that:
• Unauthenticated customers cannot reach any network resources other than
the CN3200 login page.
• Authenticated customer have access to any network resource connected to the
CN3200’s Internet port.
How access lists work
Each customer and each access point can be associated with its own access list.
Incoming traffic cascades through the currently active lists. Traffic that is
accepted or denied by a list is not available to the list that follows it. Traffic that
passes through all lists without being accepted or denied is dropped.
Customer session
Site Profile Access List
DENY
Unauthenticated
Customer Profile Access List
DENY
How traffic flows through the access lists.
NO MATCHACCEPT
White List
NO MATCHACCEPT
Authenticated and no
user access list exists
Authenticated and
an access list exists
NO MATCHACCEPT
Internet portDropped
Note: The white list is a less-powerful version of the access list that is maintained
for compatibility with previous releases. Its functionality is completely superseded
by the access list feature. The access list feature should be used in its place.
Chapter 16: Customizing CN3200 and customer settings218
DRAFT
Within each access list, traffic cascades through the list rules in a similar manner.
Incoming traffic
Rule 1
DENY
Rule 2
DENY
Rule 3
DENY
NO MATCH
NO MATCH
NO MATCH
ACCEPT
ACCEPT
ACCEPT
DENY
How traffic flows through the access list rules.
NO MATCHACCEPT
Rules are numbered according to the order in which they are added. Only data
that is not accepted or denied by a rule is available to the next rule in the list.
Accounting support
Each rule in an access list can be configured with an account name for billing
purposes. The CN3200 will send billing information based on the amount of
traffic matched by the rule.
This lets you create rules to track and bill traffic to particular destinations.
Tips on using the access list
With certificates
• If you replaced the default SSL certificate on the CN3200 with one signed by a
well-known CA, you should define the access list to permit access to the CA
certificate for all non-authenticated customers. This enables the customer’s
browser to verify that the certificate is valid without displaying any warning
messages.
• Customers may have configured their web browsers to check all SSL
certificates against the Certificate Revocation List (CRL) maintained by the CA
that issued the certificate. The location of the CRL may be configured in the
browser, or embedded in the certificate. The access list should be configured
to permit access to the CRL, otherwise the customer’s browser will time out
before displaying the login page.
Remote login page
If you are using the remote login page feature, make sure that access to the web
server hosting the page must is granted to all unauthenticated customers.
SMTP redirect
If an unauthenticated customer establishes a connection to their email server, the
SMTP redirect feature will not work once the customer logs in. The customer’s
email will still be sent to the original email server.
To avoid this, do not use an access list to open TCP port 25 for unauthenticated
customers.
Chapter 16: Customizing CN3200 and customer settings219
DRAFT
Defining and activating access lists
Access lists are defined by adding the following Colubris-AVPair value string to
the RADIUS profile for a CN3200.
access-list=value
Access lists are activated by adding the following Colubris-AVPair value string to
the RADIUS profile for a CN3200 or a customer.
use-access-list=value
You can define up to 32 access lists. Only one list can be active per profile.
Specify a name (up to 32 characters long) to identify the access list
this rule applies to. If a list with this name does not exist, a new list
is created. If a list with this name exists, the rule is added to it.
Specify the name of an existing access list. This list is activated for
the current profile. Lists are checked in the order they are activated.
Specify what action the rule takes when it matches incoming traffic.
Two options are available:
• ACCEPT - Allow traffic matching this rule.
• DENY - Reject traffic matching this rule.
Specify the protocol to check: tcp, udp, icmp, all
Specify one of the following:
• IP address or domain name (up to 107 characters in length)
• Subnet address. Include the network mask as follows:
address/subnet mask For example: 192.168.30.0/24
• Use the keyword all to match any address.
• Use the keyword none if the protocol does not take an address
range (ICMP for example).
Specify a specific port to check or a port range as follows:
• none - Used with ICMP (since it has no ports).
• all - Check all ports.
• 1-65535[:1-65535] - Specify a specific port or port range.
account
interval
Specify the name of the customer account the CN3200 will send
billing information to for this rule. Account names must be unique
and can be up to 32 characters in length.
Specify time between interim accounting updates. If you do not
enable this option, accounting information is only sent when a
customer connection is terminated. Range: 5-99999 seconds in 15
second increments.
Chapter 16: Customizing CN3200 and customer settings220
DRAFT
Note: Spaces can be used instead of commas as separators.
Example
This topology shows wireless deployment for a fictitious university campus.
This definition creates three access lists: everyone, students, and faculty.
Everyone
This list applies to all users (students, teachers, guests), whether they are
authenticated or not. This is because the list is active on the CN3200, which is
accomplished with the entry:
use-access-list=everyone
It enables everyone to access the public web server.
Students
This list applies to authenticated students only. It is composed of the following
entries:
Enables all other traffic to reach the Internet (via routers on the backbone LAN
and the router in the NOC). If this last rule did not exist, this traffic would be
dropped.
Chapter 16: Customizing CN3200 and customer settings221
Faculty
This list applies to authenticated faculty members only. It is composed of the
following entries:
Enables all other traffic to reach the Internet (via routers on the backbone LAN
and the router in the NOC). If this last rule did not exist, this traffic would be
dropped.
DRAFT
White list
A white list enables you to specify the set of network resources that an
unauthenticated customer has access to. You can define a specific white list for
each CN3200. These definitions are automatically implemented by the CN3200
by adding the appropriate rules to the firewall.
Note: The white list has been superseded by the access list feature. However,
the white list remains supported for backwards compatibility.
Colubris-AVPair value string
white-list=protocol,address,[port]
Where:
ParameterDescription
protocol
address
port1
Specify the protocol to allow traffic on: tcp, udp, icmp, all.
Specify the IP address or domain name of a host, or the IP
address of a subnet. Use the keyword all to match any
address. When specifying an IP subnet you must include the
network mask in the following format:
address/subnet mask
Specify the specific port to allow traffic on, or a range. Not valid if
the all option is used for protocol. Use the following syntax to
specify a range:
1-65535[:1-65535]
A range must be suppled for tcp or udp. A single port must be
specified for icmp.
Note: Spaces can be used instead of commas as separators.
The white list applies to the CN3200 itself, and all client stations connected to it.
This means that if you are using customized URLs for the public access interface,
the URLs for the Login Error and Goodbye pages must specify hosts that are
included in the white list.
You can specify up to 128 Colubris-AVPair values containing white list definitions.
Chapter 16: Customizing CN3200 and customer settings222
The CN3200 can retrieve a custom SLL security certificate to replace the
Colubris Networks certificate that is included by default. For more information on
certificates, see Chapter 14.
Colubris-AVPair value string
ssl-certificate=URL [%s] [%n]
Where:
ParameterDescription
URL
By using the following placeholder, you can customize the URL for each CN3200.
This is useful when you need to update multiple units.
Placeholder Description
%sThe login name assigned to the CN3200.
%n
The certificate is encoded using PKCS#12 format, and will contain:
• the private key of the web server
• the certificate of the web server
The file is locked using a password.
Specify the URL that points to the new certificate.
Chapter 16: Customizing CN3200 and customer settings223
DRAFT
MAC authentication
The CN3200 can authenticate devices based on their MAC address. This is
useful for authenticating devices that do not have a web browser (cash registers,
for example). It can also be used to authenticate the CN300.
To make use of this feature you need to define a RADIUS user account for each
device as follows:
• username: Set this to the username you specified in the mac-address value
string. If no username is specified, set the account name to the MAC address
of the device. Use dashes to separate characters in the address. For example:
00-20-E0-6B-4B-44.
• password: Set this to the password you specified in the mac-address value
string. If no password is specified, set this to the same password that is used
for the user account you defined for the CN3200 on the Security >
Authentication page.
Important: The username and password are not encrypted for transmission so it
is important that the link with the RADIUS server is secure.
Colubris-AVPair value string
mac-address=address[,username[,password]]
Where:
ParameterDescription
address
Specify the MAC address of the device to authenticate. Use
dashes to separate characters in the address. Do not use
colons (:). For example: 00-20-E0-6B-4B-44.
Default user idle
timeout
username
password
Specify the username to associate with this MAC address.
Maximum 253 alphanumeric characters. The username field
cannot contain a comma.
Specify the password to associate with this MAC address.
Maximum 253 alphanumeric characters. The password field
cannot contain a comma.
Example
Consider the scenario where several CN300s are installed with a CN3200. If the
CN300s are going to perform firmware upgrades from a remote web or FTP
server, they will need to log in to the public access network. By using MAC-based
authentication, this can easily be accomplished. (This also requires that the
access list on the CN3200 permits access to the web or FTP server.)
Use this to set the default idle timeout for all customers whose RADIUS profile
does not contain a value for the RADIUS attribute idle-timeout.
Colubris-AVPair value string
default-user-idle-timeout=seconds
Where:
ParameterDescription
seconds
Specify the maximum amount of time a customer session
can be idle. Once this time expires, the session is
automatically terminated. A value of 0 means no timeout.
Loading...
+ 149 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.