Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 308
  • Last Modified:

why and how firewall respond to ip addresses other ips other then the outside ips of the interface

got a ASA 5505
let's say ISP have provided 83.83.83.16/28 ips to use it on outside interface
just want understand why and how firewall respond to ip addresses other ips other then the outside ips of the interface

example
firewall --- >e0-83.83.83.17 (outside)
firewall --->10.252.15.0/24 (inside)
what and how firewall will respond to other ips in the same subnet , what config i need to make on the firewall
I want firewall to respond to 83.83.83.19 to pings

Please can you help
0
mohannitin
Asked:
mohannitin
  • 4
  • 2
2 Solutions
 
Wilder_AdminCommented:
0
 
mohannitinAuthor Commented:
i want firewall to respond to different ip then the outside interface ip which i want to nat it to internal ip lets say switch
0
 
nickoargCommented:
You want to add NAT registries to the outside interface:

object network NatedServer
host INTERNAL_IP
nat (inside,outside) static 83.83.83.19 service tcp INTERNAL_PORT EXTERNAL_PORT

Open in new window


83.83.83.19 being the IP you've mentioned
0
The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

 
mohannitinAuthor Commented:
do i need to updated /add any access -list ?
0
 
mohannitinAuthor Commented:
whats the process
firewall outside interface receive the packet from isp for 83.83.83.19
firewall should drop the packet as it is not configured anywhere on the firewall ?
also there is not route for it
does it check the nat rule before responding the ISP ?
0
 
nickoargCommented:
The ASA receives the packet from the ISP to the 83.83.83.19 destination. If you don't have the nat rule, the ASA discards the packet. otherwise it will send it to the internal address defined by your nat rule, such as 10.252.15.X

The ASA processing order is:

1. Packet is reached at the ingress interface.

2. Once the packet reaches the internal buffer of the interface, the input counter of the interface is incremented by one.

3. Cisco ASA will first verify if this is an existing connection by looking at its internal connection table details. If the packet flow matches an existing connection, then the access-control list (ACL) check is bypassed, and the packet is moved forward.

If packet flow does not match an existing connection, then TCP state is verified. If it is a SYN packet or UDP packet, then the connection counter is incremented by one and the packet is sent for an ACL check. If it is not a SYN packet, the packet is dropped and the event is logged.

4. The packet is processed as per the interface ACLs. It is verified in sequential order of the ACL entries and if it matches any of the ACL entries, it moves forward. Otherwise, the packet is dropped and the information is logged. The ACL hit count will be incremented by one when the packet matches the ACL entry.

5. The packet is verified for the translation rules. If a packet passes through this check, then a connection entry is created for this flow, and the packet moves forward. Otherwise, the packet is dropped and the information is logged.

6. The packet is subjected to an Inspection Check. This inspection verifies whether or not this specific packet flow is in compliance with the protocol. Cisco ASA has a built-in inspection engine that inspects each connection as per its pre-defined set of application-level functionalities. If it passed the inspection, it is moved forward. Otherwise, the packet is dropped and the information is logged.
Additional Security-Checks will be implemented if a CSC module is involved.

7. The IP header information is translated as per the NAT/PAT rule and checksums are updated accordingly. The packet is forwarded to AIP-SSM for IPS related security checks, when the AIP module is involved.

8. The packet is forwarded to the egress interface based on the translation rules. If no egress interface is specified in the translation rule, then the destination interface is decided based on global route lookup.

9. On the egress interface, the interface route lookup is performed. Remember, the egress interface is determined by the translation rule that will take the priority.

10. Once a Layer 3 route has been found and the next hop identified, Layer 2 resolution is performed. Layer 2 rewrite of MAC header happens at this stage.

11. The packet is transmitted on wire, and Interface counters increment on the egress interface.
0
 
mohannitinAuthor Commented:
thanks man
0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now