<?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: ASA 55xx issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001651#M938916</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your statics are backwards. Should be...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 208.xxx.xxx.163 192.168.1.220 netmask 255.255.255.255&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Apr 2008 15:02:24 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2008-04-21T15:02:24Z</dc:date>
    <item>
      <title>ASA 55xx issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001650#M938915</link>
      <description>&lt;P&gt;I'm having issues with a new ASA implementation. I have some direct one-to-one translations specificed and I want all the rest of my outbound traffic to go out the global PAT address, but for some reason, all traffic, including inside hosts with outside NATs are appearing as the global PAT address.  &lt;/P&gt;&lt;P&gt;Config attached&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 00:39:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001650#M938915</guid>
      <dc:creator>rjrii</dc:creator>
      <dc:date>2019-03-26T00:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 55xx issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001651#M938916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your statics are backwards. Should be...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 208.xxx.xxx.163 192.168.1.220 netmask 255.255.255.255&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2008 15:02:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001651#M938916</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-04-21T15:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 55xx issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001652#M938917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OMG! Sleep deprivation is not good, people! Thanks, acomiskey!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This setup is a conversion from an IP Chains linux firewall and I realize what I did. While documenting the static mappings I used Excel to create my internal and external columns. I then concatenated everything into the cisco static command format and switched my internal and external columns around.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Randy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2008 15:27:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-55xx-issue/m-p/1001652#M938917</guid>
      <dc:creator>rjrii</dc:creator>
      <dc:date>2008-04-21T15:27:58Z</dc:date>
    </item>
  </channel>
</rss>

