# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 6.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-01-15 00:13+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.2.0\n"

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:2
msgid "WCCP Configuration"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:26
msgid ""
"`WCCP <http://cio.cisco.com/en/US/docs/ios/12_0t/12_0t3/feature/guide/wccp."
"html>`_ is de-facto semi-standard used by routers to redirect network "
"traffic to caches. It is available on most Cisco™ routers although it does "
"not appear to be officially supported by Cisco. The primary benefits of "
"WCCP are"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:32
msgid ""
"If already have a router that supports WCCP inline you do not have to "
"change your network topology."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:34
msgid ""
"WCCP fails open so that if the Traffic Server machine fails, it is bypassed "
"and users continue to have Internet access."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:37
msgid ""
"Use of WCCP only makes sense for client side transparency [1]_ because if "
"the clients are explicitly proxied by Traffic Server there's no benefit to "
"WCCP fail open, as the clients will continue to directly access the "
"unresponsive Traffic Server host. It would be better to adjust the routing "
"tables on the router for explicit proxying."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:43
msgid ""
"Because the router serves as the inline network element, Traffic Server "
"must run on a separate host. This host can be located anywhere as long as "
"Traffic Server is either on the same network segment or a GRE tunnel can be "
"maintained between the Traffic Server host and the router."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:48
msgid ""
"|important| This document presumes that the router is already properly "
"configured to handle traffic between the clients and the origin servers. If "
"you are not certain, verify it before attempting to configure Traffic "
"Server with WCCP. This is also a good state to which to revert should the "
"configuration go badly."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:55
msgid "Configuration overview"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:57
msgid ""
"Setting WCCP is a three step process, first configuring the router, the "
"Traffic Server host, and Traffic Server."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:60
msgid ""
"|image1| The router will **not** respond to WCCP protocol packets unless "
"explicitly configured to do so. Via WCCP, the router can be made to perform "
"packet interception and redirection needed by Traffic Server transparency. "
"The WCCP protocol in effect acts as means of controlling a rough form of "
"policy routing with positive heartbeat cutoff."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:66
msgid ""
"The Traffic Server host system must also be configured using ``iptables`` "
"to accept connections on foreign addresses. This is done roughly the same "
"way as the standard transparency use."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:70
msgid ""
"Finally Traffic Server itself must be configured for transparency and use "
"of WCCP. The former is again very similar to the standard use, while WCCP "
"configuration is specific to WCCP and uses a separate configuration file, "
"referred to by the :file:`records.config` file."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:75
msgid ""
"The primary concern for configuration in which of three basic topologies "
"are to be used."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:78
msgid ""
"Dedicated -- Traffic Server traffic goes over an interface that is not used "
"for client nor origin server traffic."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:80
msgid ""
"Shared -- Traffic Server traffic shares an interface with client or server "
"traffic."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:82
msgid "Inside Shared -- Traffic Server and client traffic share an interface."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:84
msgid ""
"Outside Shared -- Traffic Server and origin server traffic share an "
"interface."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:87
msgid ""
"In general the dedicated topology is preferred. However, if the router has "
"only two interfaces one of the shared topologies will be required [2]_ "
"Click the links above for more detailed configuration information on a "
"specific topology."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:93
msgid "Shared interface issues"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:95
msgid ""
"A shared interface topology has additional issues compared to a dedicated "
"topology that must be handled. Such a topology is required if the router "
"has only two interfaces, and because of these additional issues it is "
"normally only used in such cases, although nothing prevents it use even if "
"the router has three or more interfaces."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:101
msgid ""
"The basic concept for a shared interface is to use a tunnel to simulate the "
"dedicated interface case. This enables the packets to be distinguished at "
"layer 3. For this reason, layer 2 redirection cannot be used because the "
"WCCP configuration cannot distinguish between packets returning from the "
"origin server and packets returning from Traffic Server as they are "
"distinguished only by layer 2 addressing [3]_. Fortunately the GRE tunnel "
"used for packet forwarding and return can be used as the simulated "
"interface for Traffic Server."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:111
msgid "Frequently encountered problems"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:114
msgid "MTU and fragmentation"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:116
msgid ""
"In most cases the basic configuration using a tunnel in any topology can "
"fail due to issues with fragmentation. The socket logic is unable to know "
"that its packets will eventually be put in to a tunnel which will by its "
"nature have a smaller `MTU <http://en.wikipedia.org/wiki/"
"Maximum_transmission_unit>`_ than the physical interface which it uses. "
"This can lead to pathological behavior or outright failure as the packets "
"sent are just a little too big. It is not possible to solve easily by "
"changing the MTU on the physical interface because the tunnel interface "
"uses that to compute its own MTU."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:127
msgid "References"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:129
msgid ""
"`WCCP Router Configuration Commands - IOS 12.2 <http://www.cisco.com/en/US/"
"docs/ios/12_2/configfun/command/reference/frf018.html>`_"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:140
msgid ""
"Server side transparency should also be used, but it is not as significant. "
"In its absence, however, origin servers may see the source address of "
"connections suddenly change from the Traffic Server address to client "
"addresses, which could cause problems. Further, the primary reason for not "
"having server side transparency is to hide client addresses which is "
"defeated if the Traffic Server host fails."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:148
msgid "If your router has only one interface, it's hardly a *router*."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy/wccp-configuration.en.rst:151
msgid ""
"This is not fundamentally impossible, as the packets are distinct in layer"
msgstr ""
