03-16-2018 05:50 AM - edited 02-21-2020 07:31 AM
Hello . I have configured Cisco ASA 5510 and its failed to ping outside.
Device Config below.
-----------------------------
ciscoasa# sh run
: Saved
:
ASA Version 8.2(2)
!
hostname ciscoasa
enable password /yB/dTCJeUBCqR7U encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
!
interface Ethernet0/0
nameif outside
security-level 0
ip address 175.110.102.214 255.255.255.252
!
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.5.1 255.255.255.0
!
interface Ethernet0/2
no nameif
no security-level
no ip address
!
interface Ethernet0/3
no nameif
no security-level
no ip address
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
management-only
!
ftp mode passive
clock timezone PKT 5
access-list inside_access_in extended permit ip any any
access-list inside_access_in_1 extended permit ip any any
access-list inside_access_in_1 extended permit icmp any any
access-list inside_access_in_1 extended permit icmp 192.168.5.0 255.255.255.0 any
access-list outside_access_in extended permit ip any any
pager lines 24
logging enable
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu management 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 192.168.5.0 255.255.255.0
access-group outside_access_in in interface outside
access-group inside_access_in in interface inside control-plane
access-group inside_access_in_1 in interface inside
route outside 0.0.0.0 0.0.0.0 175.110.102.213 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
aaa authentication ssh console LOCAL
aaa authentication telnet console LOCAL
http server enable
http 192.168.1.0 255.255.255.0 management
http 192.168.5.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh 192.168.5.0 255.255.255.0 inside
ssh timeout 5
console timeout 0
management-access inside
dhcpd address 192.168.5.50-192.168.5.100 inside
dhcpd dns 8.8.8.8 4.4.4.4 interface inside
dhcpd enable inside
!
dhcpd address 192.168.1.50-192.168.1.100 management
dhcpd enable management
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username admin password JptQHJ2xW4tQ5Yrz encrypted privilege 15
username usman password iCzy/Y1GwxFWggO6 encrypted
username usman attributes
service-type nas-prompt
username netsole password g6vKtLanLDMN1LFf encrypted privilege 15
username netsole attributes
service-type admin
!
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
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:addfd48cb487b5c2c1dc89d0be31e1b1
: end
--- Screen shots ---
Please help here thanks .
03-16-2018 07:05 AM
ASA doesn't let you ping an IP reachable via the outside interface from the inside interface.
Same applies when trying to reach ASAs interfaces, you can't ping the inside interface from outside.
The only exception is for VPN traffic for the interface configured with management-access.
HTH
Bogdan
03-16-2018 07:27 AM
OK got it but from our LAN we are unable to ping outside
C:\Users\Faisal>ping 4.2.2.2 -t
Pinging 4.2.2.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
03-16-2018 07:36 AM
03-16-2018 07:36 AM
Hi FarhatAslam
You need to configure a nat from inside to outside.
nat (inside) 1 [your network]
global (outside) 1 interface
Regards.-
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