<?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 ASA 5505....beware in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5505-beware/m-p/763728#M422117</link>
    <description>&lt;P&gt;I'd just like to share with the group something that I learned the hard way.  It's ebarassing, but I'd like to keep anyone from getting as frustrated as I was.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About 24 hours straight of battling a pair of 5510's and a 5505 and they will now finally pass traffic via the VPN as well as split tunnel.  The fix......changed the VLANs from the defaults.  There is a little note in the EasyVPN 5505 documentation the states in a not so well way that the "home vlan" will only support NAT-T and not native IPSEC.  It seems to me that something like that warrants a bit more attention than a little note as an after thought.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is probably old news but wanted to share anyway just in case there is someone else out there like me that can't read.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What the heck is a "home VLAN" anyway!?  That's dumb.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 09:33:39 GMT</pubDate>
    <dc:creator>m-ketchum</dc:creator>
    <dc:date>2020-02-21T09:33:39Z</dc:date>
    <item>
      <title>ASA 5505....beware</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-beware/m-p/763728#M422117</link>
      <description>&lt;P&gt;I'd just like to share with the group something that I learned the hard way.  It's ebarassing, but I'd like to keep anyone from getting as frustrated as I was.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About 24 hours straight of battling a pair of 5510's and a 5505 and they will now finally pass traffic via the VPN as well as split tunnel.  The fix......changed the VLANs from the defaults.  There is a little note in the EasyVPN 5505 documentation the states in a not so well way that the "home vlan" will only support NAT-T and not native IPSEC.  It seems to me that something like that warrants a bit more attention than a little note as an after thought.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is probably old news but wanted to share anyway just in case there is someone else out there like me that can't read.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What the heck is a "home VLAN" anyway!?  That's dumb.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:33:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-beware/m-p/763728#M422117</guid>
      <dc:creator>m-ketchum</dc:creator>
      <dc:date>2020-02-21T09:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5505....beware</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-beware/m-p/763729#M422118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmmm, interesting, thanks for the heads up I'll be checking that now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 11:05:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-beware/m-p/763729#M422118</guid>
      <dc:creator>aaron.mason</dc:creator>
      <dc:date>2007-06-07T11:05:17Z</dc:date>
    </item>
  </channel>
</rss>

