topic Re: ASA 5510 NAT (probably problem) in Network Security

ASA 5510 NAT (probably problem)

alexrfhzcx — Tue, 12 Mar 2019 00:46:34 GMT

Hello

I use Cisco ASA 5510 IOS 8.4

I have cratd interfaces, access-list etc. but I can reach any adresses from inside to outside end vice versa.

I don't use NAT (outside and inside have not mapped adresses).

My config

: Saved

ASA Version 8.4(4)1

hostname ASA

enable password PVSASRJovmamnVkD encrypted

passwd PVSASRJovmamnVkD encrypted

names

interface Ethernet0/0

description Interfejs 0 do sieci

speed 1000

no nameif

no security-level

no ip address

interface Ethernet0/1

description Interfejs 1 do sieci Ngera Active

speed 1000

no nameif

no security-level

no ip address

interface Ethernet0/2

description Interfejs 2 do sieci w TP

speed 100

no nameif

no security-level

no ip address

interface Ethernet0/3

description Interfejs 3 do sieci Ngera Active

no nameif

no security-level

no ip address

interface Management0/0

nameif Manage

security-level 100

ip address 192.168.1.1 255.255.255.252

management-only

interface Redundant1

description Interfejs do out

member-interface Ethernet0/0

member-interface Ethernet0/2

nameif inpa

security-level 100

ip address 23.2.255.233 255.255.255.248

interface Redundant2

description Interfejs do NetM Active

member-interface Ethernet0/1

member-interface Ethernet0/3

no nameif

no security-level

no ip address

interface Redundant2.1

vlan 1

nameif Zarzadz

security-level 0

ip address 23.2.35.1 255.255.255.240

interface Redundant2.200

vlan 200

nameif outpa

security-level 0

ip address 23.2.34.254 255.255.255.0

banner login ASA5510

ftp mode passive

access-list outp extended permit ip any any

access-list inp extended permit ip any any

access-list inp extended permit ip host 23.2.11.122 23.2.35.0 23.2.35.240

pager lines 24

logging enable

logging trap debugging

logging host inpa 16.7.6.14

mtu Manage 1500

mtu SKA 1500

mtu NetMA 1500

mtu Zarzadz 1500

no failover

icmp unreachable rate-limit 1 burst-size 1

asdm history enable

arp timeout 14400

access-group inp in interface inpa

access-group outp in interface outpa

route inpa 0.0.0.0 0.0.0.0 23.2.255.238 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 192.168.1.0 255.255.255.0 Manage

no snmp-server location

no snmp-server contact

snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart

telnet 23.2.11.0 255.255.255.0 inpa

telnet 126.177.6.14 255.255.255.255 inpa

telnet timeout 5

ssh timeout 5

ssh key-exchange group dh-group1-sha1

console timeout 15

management-access SKA

threat-detection basic-threat

threat-detection statistics access-list

no threat-detection statistics tcp-intercept

ntp server 126.17.68.21

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:861e6627efc88896a4440449d02840ab

: end

My debug looks like :

2013-01-14T14:01:30.713461+01:00 asa5510 %ASA-7-609002: Teardown local-host SKA:23.2.11.122 duration 0:00:02

2013-01-14T14:01:30.713580+01:00 asa5510 %ASA-7-609002: Teardown local-host identity:23.2.34.254 duration 0:00:02

2013-01-14T14:01:44.191863+01:00 asa5510 %ASA-5-111008: User 'enable_15' executed the 'terminal monitor' command.

2013-01-14T14:01:44.191952+01:00 asa5510 %ASA-5-111010: User 'enable_15', running 'CLI' from IP 0.0.0.0, executed 'terminal monitor'

Do I have create NAT ?

Re: ASA 5510 NAT (probably problem)

jpeterson6 — Mon, 14 Jan 2013 16:22:27 GMT

Hello Aleksander.

You will need to have NAT between your two nameifs as they are configured with different security levels.

If you want to avoid using NAT, what you can do is set up Twice NAT (Manual NAT) to translate your IP addresses to themselves. It's similar in function to NAT Exempt in pre-8.3 syntax.

Please reference this document for details:

https://supportforums.cisco.com/docs/DOC-11639

Hope that helps.

Re: ASA 5510 NAT (probably problem)

alexrfhzcx — Tue, 15 Jan 2013 07:16:50 GMT

Hello

I add the folowing lines :

object network wlall

subnet 0.0.0.0 0.0.0.0

object network oball

subnet 0.0.0.0 0.0.0.0

nat (inpa,outpa) source static wlall wlall destination static oball oball

nat (outpa,inpa) source static oball oball destination static wlall wlall

But still I have errors 106016 and 609002

Could I ask for any advice ?

Regards

Alex

Re: ASA 5510 NAT (probably problem)

Karsten Iwen — Tue, 15 Jan 2013 08:02:32 GMT

With your ASA-version you do not need NAT. If you don't specify NAT, then the ASA will route the traffic as a "normal" router would do.

One problem is in the redundant-config. All redundant members have to share the same media-type, speed and duplex. In your config you mix 100 MBit-interfaces with 1000 MBit-interfaces. You have to combine Eth0/0 and 0/1 in the first redundant interface and Eth0/2 and 0/3 in the second redundant interface.

Regarding your log-messages:

609002 is just informational, you should see a corresponding "Build local host". For message 106016, mor iformation is needed on how you test traffic through the ASA.

--
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni

Re: ASA 5510 NAT (probably problem)

alexrfhzcx — Tue, 15 Jan 2013 08:29:50 GMT

I have removed second interfejs from Redundants.

I have remove all nat writes.

I set the same security level an both redundant interfaces.

Still errors 302014

Have any idea ?

Re: ASA 5510 NAT (probably problem)

Karsten Iwen — Tue, 15 Jan 2013 08:37:48 GMT

I set the same security level an both redundant interfaces.

do they need to commnicate? Then you need

same-security-traffic permit inter-interface

Still errors 302014

That's not an error message.

How do you test?

--
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni

ASA 5510 NAT (probably problem)

alexrfhzcx — Tue, 15 Jan 2013 08:47:08 GMT

I try to ping from outside network an interfejs on the inside side.

I can ping outside interface

From outside network I can rnot each by telnet ASA - I of course added telnet networks to config

By the way I add

same-security-traffic permit inter-interface

but with no effects

Re: ASA 5510 NAT (probably problem)

Karsten Iwen — Tue, 15 Jan 2013 08:57:15 GMT

I try to ping from outside network an interfejs on the inside side.

I can ping outside interface

That's not supported on the ASA. Try to reach an inside host. And for using ping, you should add the inspection of icmp-traffic:

policy-map global_policy

class inspection_default

inspect icmp

From outside network I can rnot each by telnet ASA - I of course added telnet networks to config

Telnet is not allowed on the outside interface on the ASA (it's by design). Use SSH instead.

--
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni