07-13-2011 02:26 PM - edited 03-11-2019 01:58 PM
When I try to use my vpn client to connect to another ASA firewall from home, my home ASA seems to block it. The VPN seems to connect, I cant use any services.
Been reading various description of the problem and tried to fix it, but no luck so far. Hope someone could help here, I'm just starting out with the ASA.
Config follows:
: Saved
:
ASA Version 8.4(1)
!
hostname troll
domain-name hemma
enable password qo.OrRMCak4uVCfZ encrypted
passwd XXXXX encrypted
names
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface Vlan2
mac-address AAAA.BBBB.CCCC
nameif outside
security-level 0
ip address dhcp
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
ftp mode passive
dns domain-lookup inside
dns server-group DefaultDNS
name-server 8.8.8.8
name-server 8.8.4.4
domain-name hemma
object network obj_any
subnet 0.0.0.0 0.0.0.0
object network outside-network
host 123.123.123.123
description outside-network
access-list inside_access_in extended permit ip any any
pager lines 24
logging enable
logging asdm errors
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
!
nat (inside,outside) after-auto source dynamic any interface
access-group inside_access_in in interface inside
route outside 0.0.0.0 0.0.0.0 123.123.123.123 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
aaa authentication enable console LOCAL
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto isakmp nat-traversal 3600
crypto ikev1 enable outside
telnet timeout 5
ssh scopy enable
ssh 192.168.1.0 255.255.255.0 inside
ssh timeout 60
ssh version 2
console timeout 0
management-access inside
dhcp-client client-id interface outside
dhcpd address 192.168.1.5-192.168.1.36 inside
dhcpd dns 192.168.1.1 8.8.4.4 interface inside
dhcpd domain troll interface inside
dhcpd enable inside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username test password password encrypted privilege 0
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
inspect ipsec-pass-thru
policy-map type inspect ipsec-pass-thru map_name
parameters
esp
ah
!
service-policy global_policy global
prompt hostname context
call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email callhome@cisco.com
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
Cryptochecksum:e775asc3beasc8basc8234356457782234asc34a234sc2
: endf
no asdm history enable
Solved! Go to Solution.
07-13-2011 09:22 PM
Hi,
As you can see the translation is failing for IP protocol 50. Since you are running PAT on your home ASA, when the client connects and starts encapulating everything on ESP (IP protocol 50) it hides the transport layer and above. Since PAT depends on ports in order to create the translation, you are goint to get this error message.
You may say, well, I can connect if I use my $80 lynksys router, or across a cisco router. That is because those devices let the IP protocols pass thru without being inspected. The ASA drops them by design and for security purposes.
How to solve it? On the Endpoint device, the VPN server, the ASA on the office, you need to put the following command.
Crypto isakmp nat-traversal
And make sure that the Client its using it as well. That way the connection should run fine.
Hope this helps,
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008060f25c.shtml
Mike
07-13-2011 09:22 PM
Hi,
As you can see the translation is failing for IP protocol 50. Since you are running PAT on your home ASA, when the client connects and starts encapulating everything on ESP (IP protocol 50) it hides the transport layer and above. Since PAT depends on ports in order to create the translation, you are goint to get this error message.
You may say, well, I can connect if I use my $80 lynksys router, or across a cisco router. That is because those devices let the IP protocols pass thru without being inspected. The ASA drops them by design and for security purposes.
How to solve it? On the Endpoint device, the VPN server, the ASA on the office, you need to put the following command.
Crypto isakmp nat-traversal
And make sure that the Client its using it as well. That way the connection should run fine.
Hope this helps,
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008060f25c.shtml
Mike
07-21-2011 11:30 PM
Thanks for taking your time helping me out, very appricated !
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide