• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

PIX vpn problem

We have a call out to Cisco as well for help on this but thought I would give you guys a shot.

The situation is that we have a central location with a PIX firewall (lets call him A). we have two satellite locations with pix firewalls that maintain ipsec tunnels to (A) - lets call them B and C. now the issue is that traffic from B wont flow to C and vice-versa. B and C can hit A and beyond into the network but cant ping or trace. I?m guessing the pix is locking down the tunnels to prevent any "cross-contamination" - keeping clients from each other.

Any ideas?
 
That's exactly what they are doing. By default this behavior isn't allowed.

search cisco for configuration hub-spoke VPNs and allowing the spokes to communicate.

I can't recall off the top of my head, but if you look at the configuration pages for PIX it is right there.
 
Back
Top