cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
838
Views
0
Helpful
8
Replies

Communicate in the inside interface

adam.fenner
Level 1
Level 1

I can't communicate with anything connected on the inside interface.

See the attached command prompt ipconfig. I get an IP address and default gateway from the inside address pool of the ASA (100.100.100.240) but i can't communicate or ping anything that is directly connected in the 100.100.100.xxx network. I need to be able to get the 100.100.100.xxx ip address so that I can remotely communicate with control equipment.

See below config. that is on the ASA 5505 right now that was configured through ASDM and the Anyconnect VPN wizard.

Just trying to set up a simple VPN remote access. 

Hardware: ASA5505, 512 MB RAM, CPU Geode 500 MHz
:
ASA Version 9.1(6)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
names
ip local pool InsidePool 100.100.100.240-100.100.100.245 mask 255.255.255.0
!
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 100.100.100.252 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 10.8.8.8 255.255.255.0
!
ftp mode passive
object network obj_any
subnet 0.0.0.0 0.0.0.0
object network NETWORK_OBJ_100.100.100.240_29
subnet 100.100.100.240 255.255.255.248
pager lines 24
logging asdm informational
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
nat (inside,outside) source static any any destination static NETWORK_OBJ_100.10
0.100.240_29 NETWORK_OBJ_100.100.100.240_29 no-proxy-arp route-lookup
!
object network obj_any
nat (inside,outside) dynamic interface
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 100.100.100.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 information***

crypto ikev2 enable outside
crypto ikev2 remote-access trustpoint ASDM_Launcher_Access_TrustPoint_0
telnet timeout 5
no ssh stricthostkeycheck
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0

dhcpd auto_config outside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ssl trust-point ASDM_Launcher_Access_TrustPoint_0 outside
ssl trust-point ASDM_Launcher_Access_TrustPoint_0 inside vpnlb-ip
ssl trust-point ASDM_Launcher_Access_TrustPoint_0 inside
webvpn
enable outside
anyconnect image disk0:/anyconnect-win-4.4.01054-webdeploy-k9.pkg 1
anyconnect profiles Remote_client_profile disk0:/Remote_cli
ent_profile.xml
anyconnect enable
tunnel-group-list enable
group-policy GroupPolicy_Remote internal
group-policy GroupPolicy_Remote attributes
wins-server none
dns-server value 208.67.222.222 208.67.220.220
vpn-tunnel-protocol ikev2 ssl-client
default-domain none
webvpn
anyconnect profiles value RemoteBluebonnet_client_profile type user
username adam password tkIBSsROm4rG5812 encrypted
tunnel-group Remote type remote-access
tunnel-group Remote general-attributes
address-pool InsidePool
default-group-policy GroupPolicy_Remote
group-alias Remote enable
!
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
call-home reporting anonymous
Cryptochecksum:
: end

8 Replies 8

Marvin Rhoads
Hall of Fame
Hall of Fame

The configuration looks pretty good.

Is the ASA's VLAN 1 interface the default gateway for the equipment you are trying to reach?

Can you try a packet-tracer as follows:

packet-tracer input outside 100.100.100.241 1025 100.100.100.1 80

Be sure to use a source address that's not currently in use by your VPN client (link below explains why) and feel free to use a legitimate destination address and tcp port.

http://www.petenetlive.com/KB/Article/0001298

The default gateway for the controls equipment on the 100.100.100.xxx network is either 100.100.100.1 or it's not filled out. 

I'm not familiar with packet-tracer. When I try that command, it stops after "outside" and the only commands that i can give it are icmp, rawip, tcp, or UDP.

After i'm connected and given the IP address of .241, i can't ping or communicate with anything on the 100.100.100.xxx network. But If i connect a seperate PC into VLAN1 on the ASA, i can ping the inside interface and also .241 

I feel like the fix is going to be something stupid but I can't figure it out. it seems that i can talk to the "remote PC" but the remote PC can't communicate with anything. 

Sorry, I missed the tcp keyword in the command. Try:

packet-tracer input outside tcp 100.100.100.241 1025 100.100.100.1 80

You may need to tell the equipment to use the ASA VLAN 1 address as the gateway for your VPN address pool.

with the command "packet-tracer input outside tcp 100.100.100.242 1025 100.100.100.33 80" i get the below response. .242 is an unoccupied ip from my inside pool list and 33 is another PC that i physically connected to VLAN 1

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

I tried changing the default gateway on the .33 pc but that had no change. I can still ping everything from .33 but going out from.241 (ip given from inside pool) i can't ping anything.

OK, so the packet-tracer looks good.

Can you try changing your NAT exemption rule? I have sometimes seen problems when it specifies "any any" in the source fields. So let's use an object instead.

object network NETWORK_OBJ_100.100.100.0_24
subnet 100.100.100.0 255.255.255.0
!
no nat (inside,outside) source static any any destination static NETWORK_OBJ_100.10
0.100.240_29 NETWORK_OBJ_100.100.100.240_29 no-proxy-arp route-lookup
!
clear xlate
!
nat (inside,outside) source static NETWORK_OBJ_100.100.100.0_24 NETWORK_OBJ_100.100.100.0_24  destination static NETWORK_OBJ_100.10
0.100.240_29 NETWORK_OBJ_100.100.100.240_29 no-proxy-arp route-lookup

Nothing seemed to change. Below is what part of my config looks like. I still can't get out from .241


ftp mode passive
object network obj_any
subnet 0.0.0.0 0.0.0.0
object network NETWORK_OBJ_100.100.100.240_29
subnet 100.100.100.240 255.255.255.248
object network InsideGateway
host 100.100.100.1
object network ASAInside
host 100.100.100.252
object network NETWORK_OBJ_100.100.100.0_24
subnet 100.100.100.0 255.255.255.0
access-list global_access extended permit ip any any
access-list global_access extended permit ip 100.100.100.0 255.255.255.0 100.100
.100.0 255.255.255.0
access-list outsidetoinside extended permit icmp any any
pager lines 24
logging asdm informational
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
nat (inside,outside) source static NETWORK_OBJ_100.100.100.0_24 NETWORK_OBJ_100.
100.100.0_24 destination static NETWORK_OBJ_100.100.100.240_29 NETWORK_OBJ_100.1
00.100.240_29 no-proxy-arp route-lookup
!
object network obj_any
nat (inside,outside) dynamic interface
access-group global_access global
timeout xlate 3:00:00
timeout pat-xlate 0:00:30

Thanks for your help in trying to figure this out! I really appreciate it!

Can you do a packet capture (easiest in ASDM) when you try to connect? I'd filter on traffic to/from the inside host you are trying top reach.

That should show the traffic leaving the ASA from your VPN PC and going to the host. We should also see the return traffic and can go from there based on what is actiually observed.

I might have misspoken on the packet tracer. See the attached images while the vpn is active. 

I'm working on the packet capture wizard right now.