I have a feeling I'm trying to bypass the primary functionality of an ASA..but might as well pose the questions.
I've got an existing home-office lab network that relies on a Netscreen device as the firewall, using it to map a variety of lab servers/services to the public netblock I have from my ISP. I am installing the ASA for two reasons - testing IPSec VPN & testing SSL VPN.
I was hoping to configure up only an 'inside' network interface on the ASA for the home-office/lab network, map the private IP to an available public IP via the Netscreen, and then configure firewall policy on the Netscreen to allow the necessary ports/protocols for IPSec VPN/SSL VPN.
Every piece of documentation I'm finding seems to indicate that the ASA's 'outside' interface has to be configured on a different network for, really, any of it's features to work.
Can someone help me shed some light - is it possible for the ASA to support incoming VPN connections if only an 'inside' interface is configured?
I'm just not interested in setting up another firewall (the ASA) or replacing the existing Netscreen.
Thanks for your insight.