When I design internal networks, I create /24 networks for all my internal VLANs
Servers are 10.1.10.0/24 Clients are 10.1.11.0/24 Management is 10.1.12.0/24 etc...
All these networks summarize nicely into a /16.
I would then address my DMZ in a different class network like 172.16.1.0/24.
Is there any reason why I shouldnt use a network that fits in my 10.1.0.0 /16 summarization? For example 10.1.200.0/24. All DMZ and internal networks will all be on separate physical interfaces and secured with ACLs, IPS, etc.
I'm just trying to clean up routing tables and lessen the administration when creating new DMZs.
You are keeping a different ip stack for dmz is just for identifying or isolating the dmz from internal ranges... or you want to avoid multiple routing at core level or at some level to multiple 10.x.x.x to go via internal or dmz..... instead if you have a single rule for each segments say all 10.0.0.0 go via internal core..... all 172.16.0.0 go via dmz zone....
Mixing up will always mess up in case of troubleshooting.... It just confuses.....
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...