I think that should be ok. It is kind of odd (just stepped into this job), but the ISP actually controls and configures the router on our end. From what I have been told, they have already configured the router with the new subnet.
They have given me a /27 subnet.
Lets just say the subnet is 126.96.36.199/27 (random numbers).
If it is already configured on the router, I don't need to setup anything on the ASA itself? I could just start using the IP addresses when i need them?
Can I still map a private IP address range to the new subnet? That is how we currently do it:
static (dmz,outside) 10.0.0.1 188.8.131.52
access-list out_in permit tcp any host 184.108.40.206 eq www
So in a nutshell, as long as the ISP has taken care of their part by configuring that block of IP's on the router, and I configure things properly on ASA (using static) then everything SHOULD be good to go.
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...