<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SSL source IP in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247289#M3563</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The SSL module does not have an IP address assigned to it, so it cannot use its own. The server should see the client IP address, unless you configure source nat specifically by using groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Mar 2004 17:43:44 GMT</pubDate>
    <dc:creator>stevehall</dc:creator>
    <dc:date>2004-03-08T17:43:44Z</dc:date>
    <item>
      <title>SSL source IP</title>
      <link>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247287#M3561</link>
      <description>&lt;P&gt;When using SSL modules in the CSS, does the client source IP address show up on the web server?  Or does the CSS do a source NAT so the packet comes back to the SSL module?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2004 16:29:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247287#M3561</guid>
      <dc:creator>cisco123456</dc:creator>
      <dc:date>2004-03-08T16:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: SSL source IP</title>
      <link>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247288#M3562</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the client ip address is preserved.&lt;/P&gt;&lt;P&gt;That's why you need to make sure the response goes back  to the CSS either by pointing the default gateway at the CSS pr by using some sort of policy routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Mar 2004 16:31:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247288#M3562</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-03-08T16:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSL source IP</title>
      <link>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247289#M3563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The SSL module does not have an IP address assigned to it, so it cannot use its own. The server should see the client IP address, unless you configure source nat specifically by using groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Mar 2004 17:43:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ssl-source-ip/m-p/247289#M3563</guid>
      <dc:creator>stevehall</dc:creator>
      <dc:date>2004-03-08T17:43:44Z</dc:date>
    </item>
  </channel>
</rss>

