<?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: CSS - NAT, Groups and ACLs in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-nat-groups-and-acls/m-p/377233#M6546</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joerg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if I understand correctly, you want to nat the client ip address but only when going to specific servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we take a CSS11500, ACL permit/deny are applied in hardware even before doing a flow lookup.&lt;/P&gt;&lt;P&gt;ACL with enhanced function like sourcegroup select are done in software before doing the loadbalancing decision.&lt;/P&gt;&lt;P&gt;The ACL function will pass the nating argument to the  loadbalancing decision.&lt;/P&gt;&lt;P&gt;So at the time you do not, you don't know yet which real server will be used.&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>Mon, 07 Feb 2005 10:32:21 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2005-02-07T10:32:21Z</dc:date>
    <item>
      <title>CSS - NAT, Groups and ACLs</title>
      <link>https://community.cisco.com/t5/application-networking/css-nat-groups-and-acls/m-p/377232#M6545</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;basically I can do src NAT in two ways. Either I use groups and use &amp;gt;&amp;gt;add destination service XYZ&amp;lt;&amp;lt; OR I use ACLs and groups and put the group as a source-group in the ACL. In case of the last possibility isn't it possible to specifiy which services are affected for SRC-NAT by adding a add service X in the group config or is it only possible to limit it in the ACL due to only allowing a certain destination in the ACL and is this destination the real service (needs to be if I would be able to achive what I'm tryin to achive)? &lt;/P&gt;&lt;P&gt;Furthermore is there a paper stating the order of opperation for the CSS when happens ACL-Chechking when happens the NAT with ACLs and so on?&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt; Joerg&lt;/P&gt;</description>
      <pubDate>Sun, 06 Feb 2005 11:29:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-nat-groups-and-acls/m-p/377232#M6545</guid>
      <dc:creator>jfoerster</dc:creator>
      <dc:date>2005-02-06T11:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: CSS - NAT, Groups and ACLs</title>
      <link>https://community.cisco.com/t5/application-networking/css-nat-groups-and-acls/m-p/377233#M6546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joerg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if I understand correctly, you want to nat the client ip address but only when going to specific servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we take a CSS11500, ACL permit/deny are applied in hardware even before doing a flow lookup.&lt;/P&gt;&lt;P&gt;ACL with enhanced function like sourcegroup select are done in software before doing the loadbalancing decision.&lt;/P&gt;&lt;P&gt;The ACL function will pass the nating argument to the  loadbalancing decision.&lt;/P&gt;&lt;P&gt;So at the time you do not, you don't know yet which real server will be used.&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>Mon, 07 Feb 2005 10:32:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-nat-groups-and-acls/m-p/377233#M6546</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-02-07T10:32:21Z</dc:date>
    </item>
  </channel>
</rss>

