[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

Cisco ASA Bridge for VPN Only

Is it possible to bridge an ASA and have it maintain the VPN.  Here is my config

-------(+)------(+)-----Internet
      Cisco  ^  RTR
       ASA   ^
                 192.168.0.X/2

I wold like to bride the cisco so that the DHCP and port forwarding are all handled by the existing router making the ASA transparent but I need the ASA to maintain a VPN with a remote ASA.
0
sifugreg
Asked:
sifugreg
  • 3
  • 3
1 Solution
 
mcsweenSr. Network AdministratorCommented:
The ASA cannot be transparent if it is to be an endpoint for VPN.  The other ASA has to be able to communicate with it.

It is not good practice to have a device on the outside of your firewall maintaining services for the inside network.  I would suggest creating an internal LAN subnet and setup DHCP services on the ASA to assign addresses to your internal nodes.

You will either have to put the ISP's router in bridged mode or create a 1 to 1 NAT (might be called port forwarding rule) on the ISP's router to forward all traffic from the WAN address of the ISP router to the WAN (192.168.0.x) address of your ASA.  You may also have to turn off the firewall or create an exception on the ISP's router.
0
 
sifugregAuthor Commented:
Kinda what I figured.  So what about that 1 to 1 NAT.  How would one go about doing that?
0
 
mcsweenSr. Network AdministratorCommented:
Depends on what your ISP's "router" is.  I assume it's a cable modem or dsl router.  Look for something that says DMZ.  It usually allows you to put a single IP in there to expose it to the internet.  Enter the ASA's outside IP in this field.  This creates a 1 to 1 NAT.

This would make the ISP's router forward all traffic it receives on it's public IP to the ASA bypassing the ISP's firewall and letting the ASA handle firewall tasks.

If you don't see that option you may have to do a port forwarding rule on the ISP's router which is usually called Port Forwarding and is sometimes mixed in a section called Gaming or something like that.  You might need a rule for each service you want to allow in.

Your best bet is still to put the ISP's router in bridge mode if it is possible.  Sometimes you have to call them to get instructions how.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
sifugregAuthor Commented:
That one I understand.  I was hoping to use the cable modem for the configuration tasks.  It is much simpler for my limited needs than having to wrestle the cisco when I do not speak fluent cisco-ese.  I do agree that bridging the ISP router would make the most sense but I'm just not that comfortable at rapidly configuring the cisco ASA and I'm constantly dinking with port forwarding etc.  Oh well, maybe it is time to tackle the education.
0
 
Ernie BeekCommented:
Education is always good :) And to fill the gaps in you're knowledge we're here as well ;)

Like stated by mcsween, I'd go for making the rtr bridged. That way you only have to manage one device instead of to (because the bridged router will be transparent). This will also prevent issues with 'routing' the VPN through the modem/rtr to the ASA.

And if you have any issues/questions, just ask us.
0
 
mcsweenSr. Network AdministratorCommented:
Two commands that will get just about everything done on an ASA as far as ports, firewall, or NAT.

Firewall -
access-list 'ACL NAME' extended Permit/deny type port source destination

Open in new window

so to allow access to a web server on ip 24.24.24.24 from anywhere you would use
access-list ouside_access_in extended permit tcp 80 any 24.24.24.24 255.255.255.255

Open in new window


NAT -
Static (inside, outside) type publicIP public_Port privateIP private_port netmask 'subnet'

Open in new window

so to forward the port to an internal server at 192.168.0.10 for the firewall rule above you would use
static (inside,outside) tcp 24.24.24.24 80 192.168.0.10 80 netmask 255.255.255.255

Open in new window

0
 
sifugregAuthor Commented:
Thanks for the guidance.  I will apply the knowledge as soon as set up the home office.
0

Featured Post

Shaping tomorrow’s technology leaders, today

The leading technology companies all recognize the growing need for gender diversity. Through its Women in IT scholarship program, WGU is working to reverse this trend by empowering more women to earn IT degrees and become tomorrow’s tech-industry leaders.  

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