I have an established VPN site to site between a PIX 501 at the remote end, and a 515e at the main site. Subnets are 192.168.50.x at the remote site, 192.168.44.0 (255.255.254.0 mask at main site end) which is working properly.
I can, with persistent routes on systems at each end, see the needed addresses on the 44/45 subnet from 50, and the 50 subnet from 44/45, and traffic moves appropriately.
At the main end I now have added a 192.168.53.x subnet, with a router at 192.168.44.24 to handle it, and from the pix at 192.168.45.1 I can see addresses on this subnet.
What I am trying to do is to get a route esablished from the pix at 192.168.50.1 so that addresses on the 192.168.50.x subnet can see the 53.x subnet addresses (So I can place some VoIP phones at the remote site to connect to the PBX here, which is using the 53.x subnet.
I can ping addresses from the pix at the main site (45.1) on the 53.x subnet, and I can ping the 44.24 address of the router to the 53.x subnet from addresses on 50.x subnet.
I know I am missing a route from the 50.x subnet to find the next hop, but I cannot seem to determine where it goes from here. I would assume the 50.1 pix should have a route to 53.x with a gateway address of 50.1, and that would pass to the 45.1 pix, which has a route to the 44.24 as a gateway to 53.x, but I can't seem to make that work.
So, what am I missing, or am I missing the boat entirely on the process? I am good enough with tcp routing to understand the answer, but not quite good enough to spot it apparently.