03-07-2006 12:02 PM - edited 02-21-2020 12:45 AM
Hi All,
I currently have my vpn users on a pix515e config over ipsec terminating on my outside int. I am ordering a asa 5510 as i need another firewall for a smaller location and decided to just upgrade here and move this one, there!
my question. how does the asa work? i would REALLY like to have my vpn users on an entirely separate vlan so that i may assign an entire 254 address as a pool. currently i have to pick and choose for the pool which often runs out. how does work? does the asa use interfaces basically the same way the pix does? i was told before to "terminate my vpn on my dmz", not sure i understand that. i want my users to be able to access the internet through me, currently they are cut off from the net altogether as i refuse to do split tunnel. could someone give me some guidance?
also...other than making sure the interfaces align, can i use the pix config on the asa?
TIA,
R
03-08-2006 02:53 AM
with asa or pix v7, it is capable to redirect internet traffic.
further, i was just wondering what you are referring to assign remote vpn to an entirely separate vlan. the vpn client pool should "never" overlap any network scheme that connects to the pix.
e.g.
pix inside = 192.168.1.0
pix dmz = 192.168.2.0
then vpn pool should not be 192.168.1.0 or 192.168.2.0.
03-08-2006 05:39 AM
I understand the overlapping deal, this is why I want to change it. I was handed this network and realize this is not a good thing to have, but do not know exactly how to change it. So basically I just need to assign a pool of addresses to vpn users and route them how? how does my internal network know to allow these users access to local resources?
03-08-2006 01:24 PM
providing the inside net is directly connected to the asa, and there is no other wan link/router as a default gateway, then no configuration will be required for routing.
e.g.
internet <--> asa <--> inside
internet <--> asa <--> dmz
with the simple topology above, no configuration will be required. one of the reason being the default gateway for all host would be asa.
alternatively,
internet <--> asa <--> inside <--> wan router <--> branch offices
with this topology, the default gateway of all host would be the wan router, thus either the wan router has the asa as the default gateway; or a static route for the vpn client pool has the asa as the next hop.
03-09-2006 05:38 AM
Its a little more complicated than that..of course!
internet<-->router<-->asa<-->core switch<-->wan router<-->branch offices
the asa is default for the core switch, the core switch is default for wan router.
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