[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 198
  • Last Modified:

Build up a full routing capaciity in PIX

I have installed several Cisco PIX in HQ and different branch offices. Say HQ (192.168.1.0) BranchA (192.168.20.0), Branch B (192.168.30.0). Internet is the only WAN link connecting each Branchs office and HQ.

When my VPN client connecting ot HQ PIX, it could only route to the server located 192.168.1.0. Is there any way to configure my HQ PIX (or additional with any equipment) so that this VPN client could able to route to other Branch office through the HQ PIX.

My HQ has already divided in serveral VLAN. (192.168.2.0, 192.168.3.0) inaddition to 192.168.1.0. If I install a local router on my HQ which could allow it to route across these VLANs and my local lan. Afterwards, I install a static route in my HQ PIX. Could then allow my remote Cisco VPN client to access these VLAN once they form a tunnel with my  HQ PIX ?

HQ PIX (192.168.1.10)
route inside 192.168.2.0 255.255.255.0 [internal router]  -> enable VPN client to VLAN1
route inside 192.168.3.0 255.255.255.0 [internal router]  -> enable VPN client to VLAN2
 
 
 
0
AXISHK
Asked:
AXISHK
  • 2
3 Solutions
 
calvinetterCommented:
>...any way to configure my HQ PIX... so that this VPN client could able to route to other Branch office through the HQ PIX
  Not if the HQ PIX is running 6.x software.  PIX versions <7.x won't allow encrypted (VPN) traffic to enter & leave the same interface.

  See below for some examples with PIX v7.x:
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a008046f307.shtml
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/prod_configuration_examples_list.html

cheers
0
 
naveedbCommented:
You may configure multiple VPN connection, one to each location from the VPN Clients.

As calvinetter  said earlier, you can not do it from the single connection, unles you have newer version of PIX.
0
 
calvinetterCommented:
A possible workaround, if all your PIXes are 6.x:
- setup a "fully-meshed" site-to-site VPN between all PIXes
- also configure client VPN access to all PIXes
- IF you have a Terminal Server or users have a desktop PC available at one of the locations
...They could then connect to a single location via Cisco VPN client, RDP (or PCanywhere, VNC, etc) to a workstation & from there access all other branches.

  Here's an example of a fully-meshed config between 3 sites (example uses old version 6.1, but otherwise is a good example):
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00800a2cce.shtml
  Other IPSec config examples:
http://www.cisco.com/en/US/tech/tk583/tk372/tech_configuration_examples_list.html

cheers
0

Featured Post

New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now