09-16-2015 12:55 AM - edited 03-05-2019 02:19 AM
I'm new to networking, so sorry for asking, but I'm trying to get a ASA 5512-x configured to access the internet. The internet connection works, if I bypass the 5512-x. I will add a switch to interface gigabitethernet0/1, but for the moment I've plugged in a pc with the same ip address to see if I can ping out or browse the web, I can't. Here's my running config:
show running-config
: Saved
:
ASA Version 9.1(2)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
names
!
interface GigabitEthernet0/0
nameif Outside
security-level 0
ip address xxx.xxx.xxx.xxx 255.255.255.128
!
interface GigabitEthernet0/1
nameif Inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface GigabitEthernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/4
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/5
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
management-only
nameif management
security-level 100
ip address 10.0.0.1 255.255.255.0
!
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object network Internal-lan
subnet 192.168.1.0 255.255.255.0
description Internal Lan
pager lines 24
logging asdm informational
mtu management 1500
mtu Outside 1500
mtu Inside 1500
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
!
object network Internal-lan
nat (any,Outside) dynamic interface
route Outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx 1
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
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
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
http server enable
http 10.0.0.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpool policy
telnet timeout 5
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
!
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
no call-home reporting anonymous
Cryptochecksum:4c417703c9aea0e9baea7c277a768ec4
: end
I have added to the above:
icmp permit any Outside & icmp permit any Inside
still not able to ping from either my pc or the ASA
09-16-2015 11:20 AM
What's handling your dhcp or are you statically assigning addresses? Can you ping your gateway from the ASA at all?
HTH,
John
09-17-2015 12:27 AM
Hi John,
Thanks for the reply. The switch will be configured as a dhcp server. With the above config, I could not ping the gateway.
My boss has now taken the ASA away and is having a go at configuring it himself, off site!
I was hoping I'd missed something simple and the above config would highlight it. I'll wait a short while and delete this discussion.
09-17-2015 02:10 AM
Hello
I am not that up on ASA fw but it could be that your nat statement doesnt look correct, the inside interface is not mapped..
object network Internal-lan
subnet 192.168.1.0 255.255.255.0
nat (inside,outside) dynamic interface
res
Paul
09-18-2015 12:40 AM
Our ISP gave us the wrong ip address!!! It's now working!
I will delete this soon, as its not helpful to anyone!
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