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...
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.
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.
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.
That error message on the client side still bothers me. I'd like to know what the problem is.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...