<?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: user logging with NAT in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447307#M8249</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way to log end user activity except with the use of specific ACL's where you could keep track of how many hits a particular, very specific, ACL gets hit when using source/dest ip's in it. This is probably not really feasible, but the only way possible at this point on the CSS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pete..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Aug 2005 12:27:00 GMT</pubDate>
    <dc:creator>pknoops</dc:creator>
    <dc:date>2005-08-04T12:27:00Z</dc:date>
    <item>
      <title>user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447304#M8246</link>
      <description>&lt;P&gt;IS their a way to have logs on end user activity with a one arm design using source IP NAT.&lt;/P&gt;&lt;P&gt;On the end systems all connections comes from this NAT address.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2005 14:53:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447304#M8246</guid>
      <dc:creator>cebetant</dc:creator>
      <dc:date>2005-08-03T14:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447305#M8247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What type of hardware are we talking about here. CSM, CSS ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2005 15:04:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447305#M8247</guid>
      <dc:creator>pknoops</dc:creator>
      <dc:date>2005-08-03T15:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447306#M8248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CSS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 12:07:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447306#M8248</guid>
      <dc:creator>cebetant</dc:creator>
      <dc:date>2005-08-04T12:07:17Z</dc:date>
    </item>
    <item>
      <title>Re: user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447307#M8249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way to log end user activity except with the use of specific ACL's where you could keep track of how many hits a particular, very specific, ACL gets hit when using source/dest ip's in it. This is probably not really feasible, but the only way possible at this point on the CSS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pete..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 12:27:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447307#M8249</guid>
      <dc:creator>pknoops</dc:creator>
      <dc:date>2005-08-04T12:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447308#M8250</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bad news... You ask the first question because CSM could do it in some way?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 12:32:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447308#M8250</guid>
      <dc:creator>cebetant</dc:creator>
      <dc:date>2005-08-04T12:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447309#M8251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, the CSM does not do it either, but the ACL option is not available in the CSM, so I did not want to mix things up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pete..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 12:39:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447309#M8251</guid>
      <dc:creator>pknoops</dc:creator>
      <dc:date>2005-08-04T12:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: user logging with NAT</title>
      <link>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447310#M8252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The CSM has the HTTP header insert function that let's you insert the original client ip address into the HTTP header.&lt;/P&gt;&lt;P&gt;HTTP servers can then extract this value to determine the origin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Aug 2005 06:22:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/user-logging-with-nat/m-p/447310#M8252</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-09T06:22:06Z</dc:date>
    </item>
  </channel>
</rss>

