Asa 5505 no internet

[nyer4life]

I been trying to setup a new Cisco ASA 5505 for the past week and can't get the internal network to get out to the internet. I'm sure it's something very simple that I'm missing. I have configured everything that I have gathered online. Here is my show run. Any help would be greatly appreciated.

config)# show run
: Saved
:
ASA Version 8.2(5)
!
hostname asa
enable password y7jWi9Ir.Didp encrypted
passwd 2KFQnbNIdI.2OU encrypted
names
!
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
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 24.x.x.x 255.255.255.248
!
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object-group protocol TCPUDP
protocol-object udp
protocol-object tcp
access-list outside_access_in extended permit icmp any interface outside
access-list outside_access_in extended permit ip any interface outside
access-list outside_access_in extended permit tcp any any eq www
access-list inside_access_in extended permit ip any any
access-list inside_access_in extended permit icmp any any
access-list inside_access_in extended permit object-group TCPUDP any any
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 24.x.x.x 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
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
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
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address 192.168.1.5-192.168.1.132 inside
dhcpd dns 167.206.x.x 167.206.x.x interface inside
dhcpd enable inside
!

threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username cisco password Ot.D2KMyR7d encrypted privilege 15
!
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:a976dfc6262074f441652bc6c4f1a388
: end

][-]

[nyer4life]

show route command:
C 24.x.x.x 255.255.255.248 is directly connected, outside
C 192.168.1.0 255.255.255.0 is directly connected, inside
S* 0.0.0.0 0.0.0.0 [1/0] via 24.x.x.x, outside ....this is my outside gw address

[Jon Are Endrerud]

First off, any  chance you could upgrade past the 8.2 version ? The 8.2 version is running the old NAT standard that Cisco used. Everything after 8.3 --> is diffrent. 

I would propose checking the NAT rules to make the traffic from inside to outside PAT (hide) behind the outside interface. 

[nyer4life]

Ok I will work on the upgrade. I have the dynamic Nat rule in place to allow any inside hosts to Pat to the outside interface. (This was there once I completed the setup wizard thru asdm).
Shouldn't that take care of the Nat/Pat? Or should I be looking elsewhere?

[Marvin Rhoads]

HAve you confirmed that  the ASA itself reach the Internet?

Your access-lists are over-broad and might be giving you an issue. There's generally no need to do an inside-access-in like you have. I would remove that one completely. You can disable it to troubleshoot or just run:

no access-group inside_access_in

Are your test clients getting an IP address from the ASA? Is their traffic hitting the ASA?

You can test your configuration logic with packet-tracer like this:

packet-tracer input inside tcp 192.168.1.10 1024 8.8.8.8 80

[nyer4life]

The ASA can't reach the internet. I can ping from ASA to the inside interface, ping the inside host, ping the outside interface. CANNOT ping the outside gateway or Cannot ping out to 4.2.2.2 or 8.8.8.8.

I purposely created those access-list so everything is opened for me to troubleshoot.

Inside hosts receives IP 192.168.1.x from ASA. I see traffic moving in the asdm logs. But not sure if it's being blocked or not.

[Marvin Rhoads]

For ping to work through an ASA you need to add “inspect icmp” to your list of inspections in the default class-map.

A better test is to do an nslookup (udp flow) or browse to a website (tcp connection)

However if the ASA itself cannot reach the internet or upstream gateway then you have other issues as well. 

Did you try the packet-tracer command?

[nyer4life]

On the access-list I had allowed icmp echo-reply both inside and outside while doing the pings.

Yes I did try the packet-tracer thru asdm...the result showed "The packet is allowed".

[nyer4life]

I added inspect icmp” to the list of inspections in the default class-map. Still can't ping outside from the asa or my internal hosts. Here is the result of the packet-tracer command:

packet-tracer input inside tcp 192.168.1.6 http 8.8.8.8 80

Phase: 1
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in 0.0.0.0 0.0.0.0 outside

Phase: 2
Type: ACCESS-LIST
Subtype: log
Result: ALLOW
Config:
access-group inside_access_in in interface inside
access-list inside_access_in extended permit ip any any
Additional Information:

Phase: 3
Type: IP-OPTIONS
Subtype:
Result: ALLOW
Config:
Additional Information:

Phase: 4
Type: NAT
Subtype:
Result: ALLOW
Config:
nat (inside) 1 0.0.0.0 0.0.0.0
match ip inside any outside any
dynamic translation to pool 1 (asa-outside [Interface PAT])
translate_hits = 326, untranslate_hits = 0
Additional Information:
Dynamic translate 192.168.1.6/80 to asa-outside/162 using netmask 255.255.255.255

Phase: 5
Type: NAT
Subtype: host-limits
Result: ALLOW
Config:
nat (inside) 1 0.0.0.0 0.0.0.0
match ip inside any inside any
dynamic translation to pool 1 (No matching global)
translate_hits = 0, untranslate_hits = 0
Additional Information:

Phase: 6
Type: HOST-LIMIT
Subtype:
Result: ALLOW
Config:
Additional Information:

Phase: 7
Type: IP-OPTIONS
Subtype:
Result: ALLOW
Config:
Additional Information:

Phase: 8
Type: FLOW-CREATION
Subtype:
Result: ALLOW
Config:
Additional Information:
New flow created with id 10707, packet dispatched to next module

Result:
input-interface: inside
input-status: up
input-line-status: up
output-interface: outside
output-status: up
output-line-status: up
Action: allow

[Marvin Rhoads]

The fact that your ASA itself cannot ping Internet hosts or even its upstream gateway tells us there is a problem on that leg of the connectivity. Until you resolve that there is no way any host on the inside of the ASA will reach the Internet.

Can you instead plug a PC directly into the connection that the ASA uses for the outside interface and test whether it can reach the Internet?

[nyer4life]

Asa is able to ping internal hosts and outside interface. Just not the outside gateway or 8.8.8.or 4.2.2.2..

I connected my laptop directly to the modem(asa uses as outside interface). I can reach the internet without any issues.

[Marvin Rhoads]

When connected to the modem directly, does your PC get a DHCP address or are you replicating the static IP (and default gateway) that you have indicated in the ASA configuration above?

[nyer4life]

I type in the static IP, gateway, dns servers that was provided by isp. We have business internet with static ips.

[Marvin Rhoads]

Sorry but from everything you described it should work.

You plug a PC configured with the same address and gateway as the ASA into the modem connection and it works.

The ASA itself when plugged into that connection does not work - even when initiating traffic from the ASA.

[nyer4life]

I upgraded to the latest version of IOS 9.x as suggested. I still don't get any internet from my internal host.

In addition, the link light on interface 0/0 is only lit yellow on the left side of the interface. Does this mean anything? I tried to force full duplex and 100MB thru asdm. Didn't help.