Cisco ACNS Software Configuration Guide for Locally Managed Deployments, Release 5.5.13 - Appendix B: Reference Material for Standalone Content Engine Deployments [Cisco Application and Content Networking System (ACNS) Software]

Table Of Contents

Reference Material for Standalone Content Engine Deployments

Supported Network Protocols

Supported Streaming Media Protocols

Supported WCCP Services

Matrix of Supported Caching, Filtering, and Authentication Methods

Supported Access Control and Filtering Services for Content Requests

ACNS Software CLI Command Modes for Standalone Content Engines

ACNS Software CLI Online Help and Keyboard Shortcuts

Unusable Multicast Address Assignments

Reference Material for Standalone Content Engine Deployments

This appendix contains important reference material that is pertinent to configuring and monitoring standalone Content Engines.

This appendix includes the following sections:

•Supported Network Protocols

•Supported Streaming Media Protocols

•Supported WCCP Services

•Matrix of Supported Caching, Filtering, and Authentication Methods

•Supported Access Control and Filtering Services for Content Requests

•ACNS Software CLI Command Modes for Standalone Content Engines

•ACNS Software CLI Online Help and Keyboard Shortcuts

•Unusable Multicast Address Assignments

Note The term standalone Content Engines is used throughout this guide to refer to Content Engines that the ACNS administrators have intentionally not registered with a Content Distribution Manager (if there is one in the network) so that they can configure, manage, and monitor these Content Engines as standalone devices. This information is the focus of this guide. For information about configuring, managing, or monitoring Content Engines that are registered with a Content Distribution Manager, see the Cisco ACNS Software Configuration Guide for Centrally Managed Deployments, Release 5.5.

Supported Network Protocols

Table B-1 lists the network protocols that standalone Content Engines, which are running the ACNS 5.1 software and later releases, can use to serve content to the web client. Support for HTTP, FTP, TFTP, HTTPS and the IETF standard RTP/RTSP protocols is included as part of the ACNS software product. Support for the following two product features each need a separate license:

•The WMT product feature that offers Windows Media Services requires a WMT license.

•The RealNetworks' RealProxy feature that uses RealNetworks' RTSP protocol, which includes proprietary extensions to the standard IETF standard RTSP protocol, requires a RealProxy license.

To enable the licensed WMT product feature on a Content Engine, you must have a WMT license key, which is supplied on a certificate shipped with the Content Engine. If you are downloading the ACNS 5.x software, you can purchase a WMT license though the Cisco.com website. For more information, see the "Configuring WMT RTSP Streaming and Caching Services on Standalone Content Engines" section on page 9-14.

To enable the licensed RealProxy product feature on a Content Engine, you must have a RealProxy license key, which is supplied on a certificate shipped with the Content Engine. If you are downloading the ACNS 5.x software, you can purchase a RealProxy license though the Cisco.com website. For more information, see the "Configuring RealMedia Services" section on page 8-9.

Table B-1 Supported Network Protocols

Network
Protocol

More Information

HTTP

The main protocol used on the web for communication between web browsers and web servers. There are two commonly implemented HTTP versions today: HTTP 1.0 and HTTP 1.1. The ACNS 5.x software supports both HTTP 1.0 and HTTP 1.1. See the "Configuring HTTP Caching for Standalone Content Engines" section on page 7-7.

FTP

The prevalent file transfer protocol before HTTP became the main protocol. FTP is typically used in applications such as software distribution applications. For more background information, see the "Overview of FTP Caching with Standalone Content Engines" section on page 7-36. For information about configuring FTP caching on a standalone Content Engine, see the "Configuring FTP Caching for Standalone Content Engines" section on page 7-36.

TFTP

A simple file transfer protocol that is similar to FTP but has fewer features and is less complicated. This protocol is still being used by devices that need to download boot images or configurations using a simple protocol (for example, it is used by routers and IP phones). For more background information, see the "Configuring the TFTP Server and Gateway for Standalone Content Engines" section on page 7-58.

HTTPS

The HTTPS protocol is essentially the HTTP protocol running over a Secure Socket Layer (SSL) transport. SSL is a protocol that provides a secure channel between two machines (for example, a client and a server). SSL uses public-key crypotography to ensure the security and privacy of the conversation between the client browser and the server. HTTPS uses a unique URL that begins with an https:// (for example, https://abc.com). The default port number for HTTPS is port 443 instead of port 80, which is the default port for HTTP.

In the ACNS 5.1 software, HTTPS requests could only be SSL-terminated on the Content Engine in WCCP mode (client browsers' HTTPS requests are transparently redirected to the Content Engine through WCCP Version 2). In the ACNS 5.1 software, in WCCP mode only HTTPS requests to specific sites (HTTPS origin servers that the Content Engine was specifically configured to support) were SSL terminated. In the ACNS 5.1 software, the Content Engine would bypass HTTPS requests that were directed to HTTPS servers that it had not been explicitly configured to support.

In the ACNS 5.2 software and later releases, HTTPS requests are SSL-terminated on the Content Engine in manual proxy mode (direct proxy routing in which client browsers send their HTTPS requests directly to the Content Engine). See the "Pointing Client Browsers Directly to a Standalone Content Engine" section on page 4-36.

RTSP

A standard Internet streaming control protocol (RFC 2326). This widely used application-level protocol controls the delivery of data with real-time properties, such as video and audio. Apple QuickTime, RealNetworks, and the Cisco Streaming Engine use RTSP as a streaming control protocol. See the "Supported Streaming Media Protocols" section.

Supported Streaming Media Protocols

Table B-2 lists the streaming media protocols, control channels, the corresponding data format, and transport types that can be used to deliver streaming media files with standalone Content Engines.

Table B-2 Streaming Media Protocols

Streaming Media Protocol

Control Channel

Data Format

Transport Protocol

Windows Media format

TCP

RTSP¹

UDP,² TCP, HTTP, IP multicast

RealNetworks media format

TCP

RTSP, PNA³

UDP, TCP, HTTP, IP multicast

¹RTSP=Real Time Streaming Protocol

²User Datagram protocol

³PNA=Progressive Networks Audio

Supported WCCP Services

The type of WCCP services supported by a standalone Content Engine and a WCCP-enabled router varies based on whether WCCP Version 1 or Version 2 is used, as indicated in Table B-3. All of the services except for the standard web-cache service (service 0) requires that WCCP Version 2 (as opposed to WCCP Version 1) is running on the router and the standalone Content Engine for a particular WCCP service to be supported. These services are called predefined WCCP services.

Some of the WCCP services that the routers can supply have a well known set of criteria and have a predefined service identifier. For instance, the standard web-cache service (service 0) is a currently supported web-caching service that has a predefined service identifier and well know set of criteria (for example, redirects HTTP requests to port 80). See Table B-3 for a list of WCCP services that have a predefined service identifier (service number).

Other services, that are not well known, may be defined by the configuration of a set of criteria and assigned a service identifier to it. This configuration can be performed by the Content Engines (web caches) that form a particular WCCP service group so that they can define what the criteria is as new WCCP services are developed, but is gated by the routers that need to enable the acceptance of the particular service identifier that the Content Engines are defining the criteria for. WCCP services 90 to 97 are provided to allow you to configure such user-defined services, define the criteria for the new service, and then assign it a service number (identifier).

Note In the ACNS software releases earlier than the ACNS 5.2 software release, a maximum of eight active WCCP services were supported by a WCCP Version 2-enabled router and a Content Engine. In the ACNS 5.2.1 software release, up to 25 active WCCP Version 2 services are supported. In the ACNS 5.2 software release, there are 17 WCCP Version 2 services that can be configured. In the ACNS 5.3.1 software release, there are 18 WCCP Version 2 services that can be configured. In the ACNS 5.3.1 software release, service 83 was added.
Table B-3 Supported WCCP Services with Standalone Content Engines
Service
Number

Service
Name

Type of
Service

Service Description

0

web-cache

Predefined

Web-caching service that permits WCCP Version 1 or Version 2-enabled router to redirect HTTP traffic to a single port on the Content Engine. The Content Engine is functioning as a transparent forward proxy server. Only a single WCCP-enabled router is supported with WCCP Version 1. Multiple WCCP-enabled routers (those on the router list) are supported with WCCP Version 2.

The Content Engine listens for redirected HTTP requests on the standard HTTP port (default port 80). To enable the Content Engine to listen for WCCP-intercepted HTTP traffic on ports other than the default port, configure the custom-web-cache service or a user-defined WCCP service (services 90 to 97). See the "Configuring the Standard Web-Cache Service (Service 0) on a Router" section on page 6-27.

53

dns

Predefined

DNS-caching service that permits WCCP Version 2-enabled routers to redirect client requests transparently to a Content Engine for the Content Engine to resolve the DNS name. After the Content Engine resolves the DNS name, it stores the resolved DNS name locally so that it can use the resolved names for future DNS requests. See the "Configuring the DNS Caching Service (Service 53) on a Router" section on page 6-28.

60

ftp-native

Predefined

Caching service that permits WCCP Version 2-enabled routers to redirect FTP native requests transparently to a single port on the Content Engine. The Content Engine retrieves the requested FTP content, stores a copy locally, and serves the requested content to the requester. See the "Configuring the FTP-Native Caching Service (Service 60) on a Router" section on page 6-29.

Note In the ACNS 5.3.1 software release, the name of this WCCP service was changed from ftp to ftp-native to clearly differentiate between FTP native requests and FTP-over-HTTP requests. Service 60 (the ftp-native service) only applies to transparent redirection of FTP native requests and does not apply to FTP-over-HTTP requests.
70

https-
cache

Predefined
Caching service that permits WCCP Version 2-enabled routers to intercept port 443 TCP traffic and redirect this HTTPS traffic to the Content Engine (acting as a transparent forward proxy server that is configured for HTTPS transparent caching). The Content Engine retrieves the requested content, stores a copy locally (HTTPS transparent caching), and serves the requested content to the client.

In the ACNS 5.2.1 software release, another interception mode (the accept-all mode) was added for the WCCP https-cache service. This mode was added to support the filtering of HTTPS traffic. This mode works the same way as the traditional WCCP services (for example, the web-cache service that intercepts all web traffic by default).

By default, the Content Engine accepts all HTTPS traffic.

ContentEngine(config)# wccp https-cache ?
accept-all Accept all https traffic by default
mask Specify mask used for CE assignement
router-list-num Router list number
If the wccp https-cache accept-all global configuration command is used, the HTTPS cache (the Content Engine that has the https-cache service configured and enabled) operates in accept-all mode (all HTTPS traffic is intercepted by the Content Engine); otherwise, the Content Engine (the HTTPS cache) works in accept-only mode, as in the ACNS 5.1.x software.

The Content Engine listens for redirected HTTPS requests on the standard HTTPS port (default port 443). To intercept HTTPS traffic on ports other than the default port, configure a user-defined WCCP service (services 90 to 97). See the "Configuring the HTTPS-Cache Service (Service 70) on a Router" section on page 6-29.
80

rtsp

Predefined

Media-caching service that permits WCCP Version 2-enabled routers to redirect RTSP client requests transparently to a single port on a Content Engine (RealMedia transparent caching).

The Content Engine listens for redirected RTSP requests on the standard RTSP port (default port 554). To intercept RTSP traffic on ports other than the default port (port 554), configure a user-defined WCCP service (services 90 to 97). To configure transparent interception of RTSP requests from RealMedia clients, you only need to configure the rtsp service (service 80) on the WCCP Version 2-enabled router. For information about configuring service 80 on a router, see the "Configuring the RTSP Service (Service 80) on a Router" section on page 6-30.

In contrast, you must configure the rtsp service (service 80) as well as the wmt-rtspu service (service 83) on the WCCP Version 2-enabled router to configure transparent interception of WMT RTSP requests. For information about configuring service 83 on a router, see the "Configuring the WMT-RTSPU Service (Service 83) on a Router" section on page 6-31.

83

wmt-rtspu

Predefined

Media-caching service that permits WCCP Version 2-enabled routers to redirect RTSP requests from Windows Media Services 9 clients (Windows Media 9 players) transparently to a single port on a Content Engine (port 5005). The Content Engine listens for redirected RTSP requests from Windows Media 9 Players on the standard Windows Media RTSPU port (default port 5005). To intercept RTSP requests from Windows Media 9 players on ports other than the default port, configure a user-defined WCCP service (services 90 to 97). To configure transparent interception of WMT RTSP requests, you must configure the rtsp service (service 80) as well as the wmt-rtspu service (service 83) on the WCCP Version 2-enabled router. For information about configuring service 83 on a router, see the "Configuring the WMT-RTSPU Service (Service 83) on a Router" section on page 6-31.

90-97

User-
configurable

User-
defined

Eight user-defined (dynamic) WCCP services that each support multiple ports (up to eight ports per WCCP service). In order to configure these services (services 90 to 97), you must create one port list for each user-defined service that will be used (for example, create port list number 1 for service 90). The port list contains the port numbers on which the WCCP Version 2-enabled router will support WCCP redirection for that particular WCCP service. When configuring these user-defined services, you must specify whether the traffic is to be redirected to the HTTP caching application, HTTPS caching application, or the streaming application on the Content Engine.

To configure the Content Engine to cache web traffic using multiple ports, configure a user-defined WCCP service (services 90 to 97) Use these user-defined WCCP services to support WCCP redirection of HTTP, HTTPS, and RTSP requests on multiple ports (up to eight ports per service) for standard WCCP services (for example, the https-cache, rtsp, mmst, and reverse-proxy services) that ordinarily only support a single port. See the "Configuring User-Defined WCCP Services (Services 90-97) on a Router" section on page 6-31.

98

custom-
web-cache

Predefined

Caching service that permits WCCP Version 2-enabled routers to redirect HTTP traffic to a Content Engine on multiple ports other than port 80. The Content Engine is functioning as a transparent forward proxy server. This service allows you to support WCCP redirection of HTTP requests on multiple ports (up to eight ports) without having to configure a user-defined WCCP service (services 90 to 97). See the "Configuring the Custom-Web-Cache Service (Service 98) on a Router" section on page 6-32.

99

reverse-
proxy

Predefined

Caching service that permits WCCP Version 2-enabled routers to redirect HTTP reverse proxy traffic to a Content Engine (a transparent reverse proxy server) on a single port (port 80). To intercept reverse proxy traffic on ports other than the default port (port 80), configure a user-defined WCCP service (services 90 to 97). See the "Configuring the Reverse-Proxy Service (Service 99) on a Router" section on page 6-33.
Matrix of Supported Caching, Filtering, and Authentication Methods

Table B-4 lists the caching, filtering, and authentication methods supported by standalone Content Engines that are running the ACNS 5.4.1 software and later releases. An asterisk (*) indicates a feature is supported for that particular protocol.

Table B-4 Caching, Filtering, and Authentication Methods and Related Protocol Support

Filtering

Proxy Authentication

Protocol

Caching

N2H2

Websense

SmartFilter

RADIUS

LDAP

NTLM

TACACS+

HTTP

*

*

*

*

*

*

*

*

FTP-over-HTTP

*

*

*

*

*

*

*

*

HTTPS-over-
HTTP

*

*

*

*

*

*

*

*

RTSPG

*

MMS-over-HTTP

*

*

*

HTTP-WCCP

*

*

*

*

*

*

*

Nontransparent native FTP

*

*

*

*

*

Transparent native FTP

*

HTTPS-WCCP

*

*

*

RTSPG-WCCP

*

MMS-over-HTTP
-WCCP

*

*

*

Supported Access Control and Filtering Services for Content Requests

Table B-5 lists the access control and filtering content services that are supported with standalone Content Engines that are running the ACNS 5.4.1 software and later releases. An asterisk (*") indicates a feature is supported for that particular protocol.

Table B-5 Supported Access Control and Filtering Services for Standalone Content Engines

Protocol

Access
Control

URL Filtering

ICAP

Rules

Caching

HTTP

*

*

*

*

HTTPS

*

*

*

FTP-over-HTTP

*

*

*

*

Native FTP

*

Streaming

RTSP

*
Local list URL filtering only

*

For more information, see the following chapters in this guide:

•Chapter 10, "Configuring Content Authentication and Authorization on Standalone Content Engines"

•Chapter 11, "Configuring Content Preloading and URL Filtering on Standalone Content Engines"

•Chapter 12, "Configuring ICAP on Standalone Content Engines"

•Chapter 13, "Configuring the Rules Template on Standalone Content Engines"

ACNS Software CLI Command Modes for Standalone Content Engines

The ACNS software device mode determines whether the device is functioning as a Content Engine, Content Distribution Manager, Content Router, or IP/TV Program Manager. The commands available from a specific CLI mode are determined by the ACNS software device mode in effect. The default device operation mode is Content Engine.

Table B-6 summarizes the purpose of the different CLI command modes that are available from the Content Engine CLI, which is configured as a standalone Content Engine that is running the ACNS 5.x software. The table also describes how to access the different command modes. The predefined admin account has superuser privileges. By default, the username is admin and the password is default for this predefined admin superuser account. Global configuration commands are device-level commands; subglobal configuration commands are not device-level.

Note Examples of subglobal configuration modes are the following: interface configuration mode, HTTPS server configuration mode, standard IP ACL configuration mode, and extended IP ACL configuration mode. For more detailed information about these modes, see the Cisco ACNS Software Command Reference, Release 5.5 publication.
Table B-6 ACNS Software CLI Command Modes for Standalone Content Engines
CLI Command
Mode

Purpose

Access

Prompt

Exit
User EXEC

Monitors the operation of the unit (the standalone Content Engine) and issue some system commands such as telnet, traceroute, and ping.
If you log in using an account that does not have superuser privileges, the following CLI prompt is displayed:

ContentEngine>
To access user EXEC mode from privileged EXEC mode, enter:

ContentEngine# disable
where ContentEngine is the hostname of the standalone Content Engine.
ContentEngine>

Use the exit or end command:

ContentEngine> exit
Privileged EXEC

Sets up, monitors, and debugs the standalone Content Engine, including all commands in user EXEC mode.
From user EXEC mode, enter:

ContentEngine> enable
Can also access privileged EXEC mode by logging into the CLI with an account with superuser privileges.
ContentEngine#
Use the disable command to return to user EXEC mode.

ContentEngine#
disable
Global
configuration

Configures an ACNS software feature for the entire unit.

From privileged EXEC mode, enter:

ContentEngine#
configure

ContentEngine
(config)#

Use the exit or end command to return to privileged EXEC mode.

Alternatively, press Ctrl-Z simultaneously.

Interface
configuration

Configures a particular interface on a standalone Content Engine.

From global configuration mode, use the interface global configuration command. For example, enter:

ContentEngine(config)#
interface FastEthernet 0/1
ContentEngine(config-if)#

ContentEngine
(config-if)#

Use the exit command to return to the previous configuration mode.

Use the end command to exit directly to privileged EXEC mode.

HTTPS
server
configuration

Configures the HTTPS server on a standalone Content Engine.

From global configuration mode, enter:

ContentEngine(config)#
https server
HTTPS_server_name

ContentEngine
(config-https)#

Use the exit command to return to the previous configuration mode.

Use the end command to exit directly to privileged EXEC mode.

Standard
IP ACL
configuration

Configures standard IP access control lists (ACLs) on a standalone Content Engine.

From global configuration mode, enter:

ContentEngine(config)#
ip access-list standard
acl-name | acl-num

ContentEngine
config-std-nacl)#

Use the exit command to return to the previous configuration mode.

Use the end command to exit directly to privileged EXEC mode.
Extended
IP ACL
configuration

Configures extended IP ACLs on a standalone Content Engine.
From global configuration mode, enter:
ContentEngine(config)# 
ip access-list extended 
acl-name | acl-num
ContentEngine
(config-ext-nacl)#

Use the exit command to return to the previous configuration mode.

Use the end command to exit directly to privileged EXEC mode.
ACNS Software CLI Online Help and Keyboard Shortcuts

To view the CLI online help, enter a ? as follows:

•View a list of the commands that are available in the current mode:
ContentEngine(config-std-nacl)# ?
delete Delete a condition
deny Specify packets to reject
exit Exit from this submode
insert Insert a condition
list List conditions
Move Move a condition
no Negate a command or set its defaults
permit Specify packets to accept
ContentEngine(config-std-nacl)#
•View the available command parameters:
ContentEngine(config)# ip access-list extended ?
<100-199> Extended IP access-list number
WORD Access-list name (max 30 characters)
•View the possible completions of a partially typed keyword.

To view a description of the online help for the ACNS software CLI, enter the help command.

As a shortcut, you can abbreviate commands to the fewest letters that make them unique. For example, the letters sho can be entered for the show command.

Certain EXEC commands display multiple screens with the following prompt at the bottom of the screen:
--More--
Press the Spacebar to continue the output, or press Return to display the next line. Press any other key to return to the prompt. Also, at the --More-- prompt, you can enter a ? to display the help message.

Table B-7 summarizes the keyboard shortcuts.

Table B-7 Command-Line Processing Keystroke Combinations

Keystroke Combinations

Function

Ctrl-A

Jumps to the first character of the command line.

Ctrl-B or the Left Arrow key

Moves the cursor back one character.

Ctrl-C

Escapes and terminates prompts and tasks.

Ctrl-D

Deletes the character at the cursor.

Ctrl-E

Jumps to the end of the current command line.

Ctrl-F or the Right Arrow key¹

Moves the cursor forward one character.

Ctrl-K

Deletes from the cursor to the end of the command line.

Ctrl-L

Repeats the current command line on a new line.

Ctrl-N or the Down Arrow key¹

Enters the next command line in the history buffer.

Ctrl-P or the Up Arrow key¹

Enters the previous command line in the history buffer.

Ctrl-T

Transposes the character at the cursor with the character to the left of the cursor.

Ctrl-U; Ctrl-X

Deletes from the cursor to the beginning of the command line.

Ctrl-W

Deletes the last word typed.

Esc-B

Moves the cursor back one word.

Esc-D

Deletes from the cursor to the end of the word.

Esc-F

Moves the cursor forward one word.

Delete key or Backspace key

Erases a mistake when entering a command; reenter the command after using this key.

¹The arrow keys function only on ANSI-compatible terminals such as VT100s.

Unusable Multicast Address Assignments

The Internet Assigned Numbers Authority (IANA) controls the assignment of IP multicast addresses. The IANA has assigned the IPv4 Class D address space to be used for IP multicast. Therefore, all IP multicast group addresses fall in the range from 224.0.0.0 through 239.255.255.255. However, some combinations of source and group address should not be routed for multicasting purposes. Table B-8 lists the unusable multicast address ranges and the reasons they should not be used.

Some of these addresses have been reserved for use by multicast applications through the IANA. For example, IP address 224.0.1.1 has been reserved for the Network Time Protocol (NTP).

IP addresses reserved for IP multicast are defined in RFC 1112, Host Extensions for IP Multicasting. More information about reserved IP multicast addresses can be found at the following location:
http://www.iana.org/assignments/multicast-addresses

Note You can find all RFCs and Internet Engineering Task Force (IETF) drafts on the IETF website (http://www.ietf.org). The Class D address range is used only for the group address or destination address of IP multicast traffic. The source address for multicast datagrams is always the unicast source address.

Table B-8 Unusable Multicast Address Assignments

Address Range

Reason

224.0.1.2/32

Known insecure service address. See the "Insecure Services" section on page 2-16.

224.0.1.3/32

Reserved for the discovery of resources within the administrative domain. See the "Limited Scope Addresses" section on page 2-16.

224.0.1.22/32

Known insecure service address.

224.0.1.35/32

Reserved for the discovery of resources within the administrative domain.

224.0.1.39/32

Reserved for the discovery of resources within the administrative domain.

224.0.1.40/32

Reserved for the discovery of resources within the administrative domain.

224.0.2.2./32

Known insecure service address.

224.77.0.0/16

Used to copy files between servers and clients in a local network. See the "Copying Files Between Servers and Clients" section on page 2-16.

224.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches. See the "Layer 2 Multicast Addresses" section on page 2-17.

225.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

225.1.2.3/32

Used to copy files between servers and clients in a local network.

225.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

226.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

226.77.0.0/16

Used to copy files between servers and clients in a local network.

226.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

227.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

227.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

228.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

228.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

229.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

229.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

230.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

230.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

231.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

231.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

232.0.0.0/24

Source-specific multicast address. See the "Source-Specific Multicast Addresses" section on page 2-16.

232.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

233.0.0.0/8

GLOP address. See the "GLOP Addresses" section on page 2-17.

233.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

233.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

234.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

234.42.42.42/32

Used to copy files between servers and clients in a local network.

234.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

234.142.142.42/31

Used to copy files between servers and clients in a local network.

234.142.142.44/30

Used to duplicate files between clients and servers in a local network.

234.142.142.48/28

Used to copy files between servers and clients in a local network.

234.142.142.64/26

Used to copy files between servers and clients in a local network.

234.142.142.128/29

Used to copy files between servers and clients in a local network.

234.142.142.136/30

Used to copy files between servers and clients in a local network.

234.142.142.140/31

Used to copy files between servers and clients in a local network.

234.142.142.142/32

Used to copy files between servers and clients in a local network.

235.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

235.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

236.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

236.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

236.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

236.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

237.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

237.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

238.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

238.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

239.0.0.0/8

Administratively scoped address that should not be passed between administrative domains. See the "Limited Scope Addresses" section on page 2-16.

239.0.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.

239.128.0.0/24

Local address that maps to an Ethernet multicast address range and may overwhelm the mapping table of LAN switches.