IP from e2 subnet works on e1 subnet - bug or feature?
PIX 515E w/6.2.1
Inside: 188.8.131.52/28 (e1 IF = 184.108.40.206)
DMZ: 220.127.116.11/28 (e2 IF = 18.104.22.168)
No translation all static.
I >accidentally< had a >Windows ME< computer on the Inside IF with the following config:
IP: 22.214.171.124 <<<<< out of range
Gateway: 126.96.36.199 <<<< or this is out of range
The OS didnt complain about the ip/gateway not being in the same range, but in any event, the config worked there was connectivity to the outside. (http://www.whatismyip resulted in 188.8.131.52).
Is this supposed to work? If so, its a feature! In the above scenario, I am wasting ips on the dmz that I would like to use on the inside. Why/how is the PIX allowing traffic from an IP on an interface that conflicts with another route/interface?
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...