ASA 5505 new install and inside hosts cannot access the internet

Click Click — Tue, 12 Mar 2019 04:36:31 GMT

Hello

Im having a problem with inside hosts access the internet. Setup is

Internet --> VDSL Router 192.168.1.1 --> Cisco ASA 5505 192.168.1.2 = inside network 192.168.200.0/24

hosts on the internet can get to my ftp server located on the inside network = so that works

hosts on the outside network can access hosts on the inside network and vice versa however hosts on the inside cann view/access sites on the internet.

Im seeing a lots of messages on the log view relating to SYN time outs

Here is my config. if you could help me fix this, that would be great 🙂

thanks

ASA Version 8.2(5)
!
hostname ASA
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd snip encrypted
names
!
interface Ethernet0/0
description LINK TO VDSL ROUTER
!
interface Ethernet0/1
description LINK TO TPLINK SWITCH
switchport access vlan 200
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
interface Vlan1
nameif outside
security-level 0
ip address 192.168.1.2 255.255.255.0
!
interface Vlan4
nameif dmz
security-level 50
ip address dhcp
!
interface Vlan200
nameif inside
security-level 100
ip address 192.168.200.1 255.255.255.0
!
boot system disk0:/asa825-k8.bin
ftp mode passive
clock timezone CET 1
dns domain-lookup outside
dns domain-lookup inside
dns server-group DefaultDNS
name-server 192.168.1.1
name-server 8.8.8.8
object-group network DM_INLINE_NETWORK_1
object-group service DM_INLINE_TCP_1 tcp
object-group service DM_INLINE_UDP_1 udp
port-object eq bootpc
port-object eq bootps
access-list inside_access_in extended permit ip 192.168.200.0 255.255.255.0 any
access-list inside_access_in extended permit udp any interface inside object-group DM_INLINE_UDP_1
access-list inside_access_in_1 extended permit ip 192.168.200.0 255.255.255.0 any
access-list inside_access_in_1 extended permit ip host 192.168.1.15 any
access-list inside_access_in_1 extended permit ip host 162.11.173.93 any
access-list outside_access_in extended permit ip host 192.168.1.15 192.168.200.0 255.255.255.0
access-list outside_access_in extended permit tcp object-group DM_INLINE_NETWORK_1 host 192.168.200.10 object-group DM_INLINE_TCP_1
access-list outside_access_in extended permit icmp host 192.168.1.1 192.168.200.0 255.255.255.0
access-list outside_access_in extended deny ip any any
pager lines 24
logging enable
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu dmz 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
icmp permit 192.168.1.0 255.255.255.0 outside
icmp permit any inside
asdm image disk0:/asdm-731.bin
no asdm history enable
arp timeout 14400
static (inside,outside) 192.168.200.0 192.168.200.0 netmask 255.255.255.0
access-group outside_access_in in interface outside
access-group inside_access_in_1 in interface inside control-plane
access-group inside_access_in in interface inside
route outside 0.0.0.0 0.0.0.0 192.168.1.1 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 outside
http 192.168.200.0 255.255.255.0 inside
http snip 255.255.255.255 outside
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
crypto ca trustpoint ASDM_Launcher_Access_TrustPoint_0
enrollment self
subject-name CN=192.168.1.2,CN=ASA
crl configure
crypto ca certificate chain ASDM_Launcher_Access_TrustPoint_0
certificate c270e553
snip
quit
telnet timeout 5
ssh 192.168.1.15 255.255.255.255 outside
ssh timeout 5
console timeout 0
management-access inside
dhcpd dns 192.168.1.1 8.8.8.8
!
dhcpd address 192.168.200.200-192.168.200.254 inside
dhcpd dns 192.168.1.1 8.8.8.8 interface inside
dhcpd lease 999999 interface inside
dhcpd update dns interface inside
dhcpd option 3 ip 192.168.200.1 interface inside
dhcpd enable inside
!

threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ntp server 213.171.220.65 source outside prefer
ssl trust-point ASDM_Launcher_Access_TrustPoint_0 outside
ssl trust-point ASDM_Launcher_Access_TrustPoint_0 outside vpnlb-ip
webvpn
username admin password snip 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:d95abed5ffe822e624a00e46e16846bb
: end
asdm image disk0:/asdm-731.bin
no asdm history enable

log entry

Aug 10 2014

12:12:56

302014

173.194.41.128

192.168.200.11

50613

Teardown TCP connection 12785 for outside:173.194.41.128/80 to inside:192.168.200.11/50613 duration 0:00:30 bytes 0 SYN Timeout

Hi,you do not have any PAT

nkarthikeyan — Sun, 10 Aug 2014 11:57:23 GMT

Hi,

you do not have any PAT configured on your FW for internet access

Example:

nat (inside) 1 <local lan> <netmask>

global (outside) 1 interface

Also you do not have any public interface on the outside and so your NAT is controlled by your vdsl router?

Regards

Karthik

Regards

Karthik

thank you for the reply and

Click Click — Sat, 16 Aug 2014 08:24:45 GMT

thank you for the reply and it was a nat issue. is it possibler to nat on the vdsl router for networks that are a hop or 2 away? is that a way to avoid natting on the asa in this senario?

Hi, if you have that option

nkarthikeyan — Sat, 16 Aug 2014 08:31:43 GMT

Hi,

if you have that option then you can do that.... you can have just the nat exempt in fw.... and your vdsl will have the NAT with public ip to equivalent private ip..... you should have the proper routes in router to reach those private segments routed via asa fw.... it purely depends on ip schema and architecture of your network..

Regards

Karthik

topic Hi, if you have that option in Network Security

ASA 5505 new install and inside hosts cannot access the internet

Hi,you do not have any PAT

thank you for the reply and

Hi, if you have that option