I am having problems getting traffic between the Extranet and DMZ interfaces. Traffic between the other interfaces works fine.
When trying to ping or WWW between Extranet and DMZ interfaces I see the following error message No route to 10.3.1.3 from 10.2.0.13. Since these networks are directly connected and I can ping these address from the PIX. Also since I can access each of these interfaces from the Inside interface, I doubt it really is a routing error.
I think its a translation issue, but cant figure out what. Id like to have the address from extranet and DMZ to be translated to themselves (i.e. traffic from 10.2.0.1 on the DMZ should be from 10.2.0.1 on the extranet).
Please check out my config and let me know if you have any idea. Config has been pruned of non-related info.
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security50
nameif ethernet3 extranet security15
nameif ethernet4 eth4 security20
nameif ethernet5 failover security25
access-list from-dmz permit tcp any any object-group Webservices
access-list from-dmz permit tcp object-group PS-Webservers any object-group PS_JOLT_PROD
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...