3030 and PIX both connected on internal side to CAT 6506 with L3
If I connect to the 3030 using a VPN client (3.0) from the outside and I assign a pool-address from the same subnet as the internal network, the client has no issues connecting to the internal or DMZ leg of the PIX. If I assign a pool-address using some other private subnet, the Client can browse the internal but not the DMZ.
I've added subnet route statements to the 6506 to forward the pool-address back to the 3030 and not out to the PIX (default gateway for the 6506) but it doesn't help with the DMZ access. Static translations across the DMZ don't work either.
Well - thought that might be the issue but I can't even ping the inside interface of the PIX through the 6506 when using different subnets (other than internal address range). I can ping other internal IP addresses just not the PIX. I do have routing statements in the 6506 to forward all replies back to the Concentrator gateway.
I tried setting up static statements across the interfaces but it didn't seem to help.
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...