You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2011/11/09 01:05:36 UTC
svn commit: r798329 - in
/websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy:
bridge.en.html wccp-configuration.en.html
Author: buildbot
Date: Wed Nov 9 00:05:36 2011
New Revision: 798329
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/wccp-configuration.en.html
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/bridge.en.html Wed Nov 9 00:05:36 2011
@@ -190,7 +190,8 @@ set it with</p>
</pre></div>
-<hr />
+<!-- Footnotes -->
+
<p>need to use <code>--physdev</code> instead of just <code>-i</code>. The actual packet processing
is identical.</p>
<!-- Abbr. -->
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/wccp-configuration.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/wccp-configuration.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/transparent-proxy/wccp-configuration.en.html Wed Nov 9 00:05:36 2011
@@ -62,7 +62,7 @@ officially supported by Cisco. The prima
<li>If already have a router that supports WCCP inline you do not not have to change your network topology.</li>
<li>WCCP fails open so that if the Traffic Server machine fails, it is bypassed and users continue to have Internet access.</li>
</ul>
-<p>Use of WCCP only makes sense for client side transparency[^1] because
+<p>Use of WCCP only makes sense for client side transparency<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup> 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
@@ -100,7 +100,7 @@ to be used.</p>
<li><a href="wccp-outside-shared.html">Outside Shared</a> -- Traffic Server and origin server traffic share an interface.</li>
</ul>
<p>In general the dedicated topology is preferred. However, if the router has
-only two interfaces one of the shared topologies will be required[^2].
+only two interfaces one of the shared topologies will be required<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup>.
Click the links above for more detailed configuration information on a specific
topology.</p>
<h3 id="Sharedinterfaceissues">Shared interface issues</h3>
@@ -113,7 +113,7 @@ or more interfaces.</p>
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].
+returning from Traffic Server as they are distinguished only by layer 2 addressing<sup id="fnref:3"><a href="#fn:3" rel="footnote">3</a></sup>.
Fortunately the GRE tunnel used for packet forwarding and return can be used
as the simulated interface for Traffic Server.</p>
<h3 id="Frequentlyencounteredproblems">Frequently encountered problems</h3>
@@ -130,18 +130,37 @@ the tunnel interface uses that to comput
<ul>
<li><a href="http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/frf018.html">WCCP Router Configuration Commands - IOS 12.2</a></li>
</ul>
-<hr />
-<p>[^1]: Server side transparency should also be used, but it is not as significant.
-In its absense, however, origin servers may see the source address of connections
+<!-- Footnotes -->
+
+<p>In its absense, 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.
-[^2]: If your router has only one interface, it's hardly a <em>router</em>.
-[^3]: This is not fundamentally impossible, as the packets are distinct in layer
-[^4]: However, the WCCP implementation does not seem to be able to use this information
-to correctly route packets. Further testing should be done.</p>
+host fails.</p>
+<p>to correctly route packets. Further testing should be done.</p>
<!-- abbr. -->
+
+<div class="footnote">
+<hr />
+<ol>
+<li id="fn:1">
+<p>Server side transparency should also be used, but it is not as significant.
+ <a href="#fnref:1" rev="footnote" title="Jump back to footnote 1 in the text">↩</a></p>
+</li>
+<li id="fn:2">
+<p>If your router has only one interface, it's hardly a <em>router</em>.
+ <a href="#fnref:2" rev="footnote" title="Jump back to footnote 2 in the text">↩</a></p>
+</li>
+<li id="fn:3">
+<p>This is not fundamentally impossible, as the packets are distinct in layer
+ <a href="#fnref:3" rev="footnote" title="Jump back to footnote 3 in the text">↩</a></p>
+</li>
+<li id="fn:4">
+<p>However, the WCCP implementation does not seem to be able to use this information
+ <a href="#fnref:4" rev="footnote" title="Jump back to footnote 4 in the text">↩</a></p>
+</li>
+</ol>
+</div>
</div>
</div>
<div class="fourcol last">