Adding an additional route to a PIX 525?

I believe we are in the same boat, or at least rowing next to each other. (-;

I think that as someone replied to my message, you also need to add the remote networks to the proper ACLs (Inbound/Outbound NAT, & Crypto ACLs) to allow it to pass traffic to/from the remote network. You have to be sure that the traffic is not NATed on either end too.

I'm pretty sure I have all of that in, though I'm missing something. I'm going one step further and have another subnet beyond the remote VPN subnet.

ScottI have a PIX 525 (172.16.1.181/16) that serves as the default gateway

You can't do this on the Pix. You can't bounce packets off the inside interface and route them back inside the network to another host. I'm sure that Walter is sick of telling people this ;-)

Chris2.

Hello,

What you have to do is to define with ACL which traffic goes to the VPN (should be encrypted). PIX can't route packets throught the same port, so I presume that your VPN connection is made on your outside port.

As I've said earlier, check Cisco.com, you have a lot of cookbooks regarding this specific sceanario.

h.

What he is trying to do is have the Pix as the default gateway on

172.16.1.181 but then have that route traffic destined for the remote network back inside to a different gateway, 172.16.188 (doesn't say what that is). The pix won't 'route on a stick'.

Chris.

Is another name for this a "hairpin" connection? It seems unfortunate that I can't get this accomplished... :-( having to add 10 static routes to 100 client machines is a lot more work than adding one static route on a PIX!

Chris