<?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: Simple ASA5505 VPN server configuration? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/simple-asa5505-vpn-server-configuration/m-p/1087506#M895030</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dumb dumb dumb... I was using the second NIC on three linux boxes to test with - 192.168.3.253,252,251 and the ASA5505 was at 192.168.3.1.  Pings to 192.168.3.1 from the vpn client worked, the others did not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look at the vpnpool in the above config, you will discover that clients come in at 172.16.1.100-199... and there was no route for that on the linux boxes.  The default route remained on the production firewall via the primary NIC.  Adding a route for 172.16.1.0 to 192.168.3.1 fixed things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That error message on the client side still bothers me. I'd like to know what the problem is.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Oct 2008 14:09:15 GMT</pubDate>
    <dc:creator>clarke</dc:creator>
    <dc:date>2008-10-16T14:09:15Z</dc:date>
    <item>
      <title>Simple ASA5505 VPN server configuration?</title>
      <link>https://community.cisco.com/t5/network-security/simple-asa5505-vpn-server-configuration/m-p/1087505#M895029</link>
      <description>&lt;P&gt;I've been trying to get an ASA 5505 to act as an IPSec VPN server for a while now. I get a good connection but receive a series of error messages at startup about not being able to set a route ( on the client side, an XP laptop with Cisco VPN software ).  I'm attaching the log and the complete configuration for your enjoyment.  Be gentle, it's been a long day...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an unmodified config; there's nothing behind the ASA except a test linux box.  It's basicly a copy of a configuration in a cisco tech note.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/asa-remotevpn-asdm.pdf" target="_blank"&gt;http://www.cisco.com/warp/public/110/asa-remotevpn-asdm.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:58:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-asa5505-vpn-server-configuration/m-p/1087505#M895029</guid>
      <dc:creator>clarke</dc:creator>
      <dc:date>2019-03-11T13:58:00Z</dc:date>
    </item>
    <item>
      <title>Re: Simple ASA5505 VPN server configuration?</title>
      <link>https://community.cisco.com/t5/network-security/simple-asa5505-vpn-server-configuration/m-p/1087506#M895030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dumb dumb dumb... I was using the second NIC on three linux boxes to test with - 192.168.3.253,252,251 and the ASA5505 was at 192.168.3.1.  Pings to 192.168.3.1 from the vpn client worked, the others did not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look at the vpnpool in the above config, you will discover that clients come in at 172.16.1.100-199... and there was no route for that on the linux boxes.  The default route remained on the production firewall via the primary NIC.  Adding a route for 172.16.1.0 to 192.168.3.1 fixed things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That error message on the client side still bothers me. I'd like to know what the problem is.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Oct 2008 14:09:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-asa5505-vpn-server-configuration/m-p/1087506#M895030</guid>
      <dc:creator>clarke</dc:creator>
      <dc:date>2008-10-16T14:09:15Z</dc:date>
    </item>
  </channel>
</rss>

