I've recently undertaken an initiative to remove backdoor access to a data-reporting server, and to swing the connection to an external interface on our firewall.
Currently we have a server that is dual-homed--one NIC is connected to our internal network, and the other goes to a dumb switch that allows access from 4 outside corporations. In other words, this secondary NIC has 4 different IPs that allow these companies to access the data on the server.
Here's what I propose to do:
I want to configure a switch that will VLAN-separate each company's network and trunk them to a single interface on our firewall. I'll configure the port with sub-interfaces for each company--utilizing the IP addresses that were previously associated with the secondary NIC on the reporting server. Finally, I will NAT traffic destined to those IPs to the IP on the primary server NIC.
I have tested this configuration in my lab and it works perfectly. But here's the catch... I have a second ASA in standby mode for failover. So my question is this: Is there a way to make the standby IPs of the sub-interfaces transparent? I understand that when the alternate ASA takes over, it assumes the IP of the primary interface, but I've found that the standby interface is still an active presence on the network even when in standby mode (i.e. it can be pinged, etc.)
The reason I ask is because I don't necessarily want to try to obtain an unused IP address from these other companies, but I don't want to use one that will jack up their routing either... I understand that normally a change in the infrastructure like this would normally be coordinated with everyone involved, however this server is only accessed during specific periods and is not "critical" to business operation. Ideally, I could make the change and nobody would ever have to be the wiser!
Hopefully someone out there can help me with this one?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...