Bit confused over how to handle a likely simple routing issue.
I VPN into my Cisco ASA on 10.1.x.x subnet. Now, I would like to not only interact with private 10.1.x.x, but also with dmz on 172.16.x.x.
In a TAC session Cisco rep confirmed that traffic is allowed for my VPN user on both subnets; he said the issue is that while traffic is flowing from 10.1.x.x to 172.16.x.x just fine, traffic is not passing back from 172 to 10; therefore a routing issue on the target server.
On a Linux system (CentOS), how would one add a route so that traffic initiated from say, 10.1.50.1 to 172.16.50.1 (the default gw and primary server nic) can flow back and forth?
While I like experimenting I'd prefer not to butcher the route and have customers complain that their websites are not loading ;-)
Example setup: eth0 is 172.16.50.1 and has gateway of 172.16.1.1 with mask 255.255.0.0 eth1 is 10.1.50.1 with mask 255.255.0.0 VPN user IP is in the 10.1 subnet, e.g. 10.1.200.1
Thanks for pointers!