<?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: static pat on other interface than default gw  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-pat-on-other-interface-than-default-gw/m-p/1206475#M861487</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you can do it by configuring static PAT in the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00805733df.shtml" target="_blank"&gt;https://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00805733df.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a00804708b4.shtml" target="_blank"&gt;https://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a00804708b4.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Apr 2009 21:01:06 GMT</pubDate>
    <dc:creator>sadbulali</dc:creator>
    <dc:date>2009-04-02T21:01:06Z</dc:date>
    <item>
      <title>static pat on other interface than default gw</title>
      <link>https://community.cisco.com/t5/network-security/static-pat-on-other-interface-than-default-gw/m-p/1206474#M861483</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have an asa 5510 with software 8.0. We have to Internet Lines, 1 16 Mbit ADSL and 1 4 Mbit SDSL. Internal Users should use the ADSL for faster downloads so the default gw is the ADSL. VPN should use the SDSL. This isn't the problem, i can use a routing entry with the option tunneled. &lt;/P&gt;&lt;P&gt;But now the difficult: The static Pat for some servers in the dmz  should use the sdsl line because of the faster upload and multiple ip-addresses. Is there any way to manage this with the asa? Packets can go through the sdsl-interface and are forwarded to the server, but the answers will go through the adsl-line and therefore have a different Ip address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas, how to solve this problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:11:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-pat-on-other-interface-than-default-gw/m-p/1206474#M861483</guid>
      <dc:creator>seibertmedia</dc:creator>
      <dc:date>2019-03-11T15:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: static pat on other interface than default gw</title>
      <link>https://community.cisco.com/t5/network-security/static-pat-on-other-interface-than-default-gw/m-p/1206475#M861487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you can do it by configuring static PAT in the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00805733df.shtml" target="_blank"&gt;https://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00805733df.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a00804708b4.shtml" target="_blank"&gt;https://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a00804708b4.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Apr 2009 21:01:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-pat-on-other-interface-than-default-gw/m-p/1206475#M861487</guid>
      <dc:creator>sadbulali</dc:creator>
      <dc:date>2009-04-02T21:01:06Z</dc:date>
    </item>
  </channel>
</rss>

