Skip to main content

How to setup the internet access through the Cisco ASA firewall?

How to setup the internet access through the Cisco ASA firewall?

Basic Guidelines for setting Internet through the Cisco ASA firewall:
At first we need to configure the interfaces on the firewall.
!— Configure the outside interface.
interface GigabitEthernet0/0
nameif outside
security-level 0
ip address 10.165.200.226 255.255.255.224
!— Configure the inside interface.
interface GigabitEthernet0/1
nameif inside
security-level 100
ip address 10.1.1.1 255.255.255.0
The nameif command gives the interface a name and assigns a security level. Typical names are outside, inside, or DMZ.
Security levels are numeric values, ranging from 0 to 100, used by the appliance to control traffic flow. Traffic is permitted to flow from interfaces with higher security levels to interfaces with lower security levels, but not the other way. Access-lists must be used to permit traffic to flow from lower security levels to higher security levels. The default security level for an outside interface is 0. For an inside interface, the default security level is 100.
IP address- IP address of interface
The next step will be to setup the nat & route
!
!— Creates an object called OBJ_GENERIC_ALL.
!— Any host IP not already matching another configured
!— NAT rule will Port Address Translate (PAT) to the outside interface IP
!— on the ASA (or 10.165.200.226) for Internet bound traffic.
!
object network OBJ_GENERIC_ALL
subnet 0.0.0.0 0.0.0.0
!
nat (inside,outside) source dynamic OBJ_GENERIC_ALL interface
!
route outside 0.0.0.0 0.0.0.0 10.165.200.225
The nat statement, as shown above, tells the firewall to allow all traffic flowing from the inside to the outside interface to use whatever address is dynamically (DHCP) configured on the outside interface.
In the route statement at the end if you use the word interface instead the traffic is pat to firewall interface ‘route outside 0.0.0.0 0.0.0.0 interface’
The last step is to add the access-list to permit traffic.
Create the simple access-list to allow inside network access to internet.
hostname (config)# object-group service allow_internet_tcp tcp
hostname (config-service)# description allow tcp ports for allowing access internet access
hostname (config-service)# port-object eq 80
hostname (config-service)# port-object eq 443
hostname (config)# object-group service allow_internet_udp udp
hostname (config-service)# description allow udp ports for allowing access internet access
hostname (config-service)# port-object eq DNS
access-list INSIDE-IN extended permit tcp 10.1.1.0 255.255.255.0 <inside network >any eq allow_internet_tcp
access-list INSIDE-IN extended permit tcp 10.1.1.0 255.255.255.0 <inside network>any eq allow_internet_udp

Comments

Popular posts from this blog

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...

Check Throughput of Interfaces - Palo Alto Networks NGFW

Check Throughput of Interfaces - Palo Alto Networks NGFW Following command shows brief interface throughput. > show system statistics session To see the complete statistics, run the show system state browser command > show system state browser Press Shift+L and click on Ports To enable tracking and updates press Y and U To see additional ports, press space bar

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with  SASE (Secure Access Service Edge)  – the convergence of networking and security into one cloud service. Here’s why. 1990s – 2000s: MPLS and the Era of Clear Network Boundaries? Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations. MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is ...