10-14-2017 05:42 AM - edited 02-21-2020 06:29 AM
Hello,
I have an inside interface (vlan2) connected to a Linksys router. (security level 0)
From the hosts on the ASA (security level 100) I can ping the hosts on the Linksys no problem as this traffic is outbound from the ASA to the Linksys (i.e. it's getting inspected) But hosts on the Linksys are not able to ping or RDC to host on the ASA as it's considered new traffic ?( un-inspected ) and I suspect the ASA is denying access. (I can't see anything thru ASDM syslog)
Hosts on the Linksys are able access Internet on the ASA (ASA outside interface security level 0)) but nothing on the inside interfaces.
What am I missing... ? any help greatly appreciated.
Result of the command: "sh run"
: Saved
:
ASA Version 8.2(1)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
!
interface Vlan1
nameif outside
security-level 0
ip address dhcp setroute
!
interface Vlan2
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface Vlan12
nameif test1
security-level 100
ip address 172.100.20.1 255.255.255.0
!
interface Vlan22
nameif test2
security-level 100
ip address 172.100.30.1 255.255.255.0
!
interface Vlan32
nameif test3
security-level 100
ip address 172.100.40.1 255.255.255.0
!
interface Ethernet0/0
!
interface Ethernet0/1
switchport access vlan 2
!
interface Ethernet0/2
switchport access vlan 12
!
interface Ethernet0/3
switchport access vlan 22
!
interface Ethernet0/4
switchport access vlan 32
!
interface Ethernet0/5
shutdown
!
interface Ethernet0/6
shutdown
!
interface Ethernet0/7
shutdown
!
ftp mode passive
clock timezone EST -5
clock summer-time EDT recurring
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
access-list test2_nat0_outbound extended permit ip 172.100.30.0 255.255.255.0 172.100.20.0 255.255.255.0
access-list test2_nat0_outbound extended permit ip 172.100.30.0 255.255.255.0 172.100.40.0 255.255.255.0
access-list test2_nat0_outbound extended permit ip 172.100.30.0 255.255.255.0 10.100.10.0 255.255.255.0
access-list test1_nat0_outbound extended permit ip 172.100.20.0 255.255.255.0 172.100.30.0 255.255.255.0
access-list test1_nat0_outbound extended permit ip 172.100.20.0 255.255.255.0 172.100.40.0 255.255.255.0
access-list test1_nat0_outbound extended permit ip 172.100.20.0 255.255.255.0 10.100.10.0 255.255.255.0
access-list test3_nat0_outbound extended permit ip 172.100.40.0 255.255.255.0 172.100.30.0 255.255.255.0
access-list test3_nat0_outbound extended permit ip 172.100.40.0 255.255.255.0 172.100.20.0 255.255.255.0
access-list test3_nat0_outbound extended permit ip 172.100.40.0 255.255.255.0 10.100.10.0 255.255.255.0
access-list inside_nat0_outbound extended permit ip 192.168.1.0 255.255.255.0 interface test2
access-list inside_nat0_outbound extended permit ip 192.168.1.0 255.255.255.0 interface test3
access-list inside_nat0_outbound extended permit ip 192.168.1.0 255.255.255.0 172.100.20.0 255.255.255.0
pager lines 24
logging enable
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu test1 1500
mtu test2 1500
mtu test3 1500
no failover
no monitor-interface inside
icmp unreachable rate-limit 1 burst-size 1
asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 192.168.1.0 255.255.255.0
nat (test1) 0 access-list test1_nat0_outbound
nat (test1) 1 0.0.0.0 0.0.0.0
nat (test2) 0 access-list test2_nat0_outbound
nat (test2) 1 0.0.0.0 0.0.0.0
nat (test3) 0 access-list test3_nat0_outbound
nat (test3) 1 0.0.0.0 0.0.0.0
route inside 10.100.10.0 255.255.255.0 192.168.1.2 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
http server enable
http 192.168.1.0 255.255.255.0 inside
http 172.100.20.0 255.255.255.0 test1
http 172.100.30.0 255.255.255.0 test2
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 address 172.100.20.100-172.100.20.200 test1
dhcpd dns 24.200.241.37 interface test1
dhcpd domain connexion-ip.com interface test1
dhcpd enable test1
!
dhcpd address 172.100.30.100-172.100.30.200 test2
dhcpd dns 24.200.241.37 interface test2
dhcpd domain connexion-ip.com interface test2
dhcpd enable test2
!
dhcpd address 172.100.40.100-172.100.40.200 test3
dhcpd dns 24.200.241.37 interface test3
dhcpd domain connexion-ip.com interface test3
dhcpd enable test3
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ntp server 128.138.140.44 source outside
webvpn
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
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 netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
inspect icmp
inspect pptp
inspect icmp error
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:7338ea2b0e004ff63fa34adaf0e726b4
: end
Solved! Go to Solution.
10-16-2017 04:02 PM
Probably is this rule here:
nat (inside) 1 192.168.1.0
Your NAT config is confuse. There are too many rules. This should be more clear.
10-16-2017 04:25 PM - edited 10-16-2017 04:28 PM
I need this rule to NAT my 10.100.10.0/24 to the Internet. (via 192.168.1.0/24) (left side of the ASA)
But you're right, its a NAT issue. I need to revise it.
It's not confusing, I have 3 networks on the right side of the ASA, test1 vlan12 , test2 vlan 22 and test3 vlan 32
They all need to NAT to the Internet, but not to 10.100.10.0/24. This part is all working.
I need to tell the ASA to NAT traffic from 10.100.10.0 going to VLAN1, but not to NAT the traffic from 10.100.10.0/24 going to VLAN 12, 22, and 32.
Need to work on this...
10-16-2017 04:35 PM
If you understand all this, perfect.
But, could be something like this "nat (any,outside) dynamic interface"
This way, only traffic to the internet will be Nated. Just a suggestion.
-If I helped you somehow, please, rate it as useful.-
10-16-2017 05:33 PM
yes, I could create object network.
But how to I tell the ASA on VLAN2, to NAT hosts sitting on 10.100.10.0/24 only when destination IP is on VLAN1? An not to NAT VLAN2 when the destination IP is VLAN 12, 22 and 32 ?
Do I use extended ACL?
10-16-2017 06:00 PM
ACL could works as it limits which network will be natted.
But if you use only nat (any,outside) I think is enough. Only to outside will nat take place.
-If I helped you somehow, please, rate it as useful.-
10-17-2017 11:25 AM - edited 10-17-2017 11:43 AM
Sorry, I do not understant this command: nat (any,outside) dynamic interface
Can you explain please ?
basically I want to tell the ASA on the Inside interface to NAT when the packet destination IP is the Internet (VLAN1) and do not NAT when the packet destination IP is 172.100.20.0/24
How can you do that, using the nat (any,outside) dynamic interface command ?
10-21-2017 05:06 AM
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