HI
You have to use routebased vpn's with ospf enabled. If you enable ECMP (equal cost) so you can even loadbalance the traffic or as an alternative you can use different metrics to have a failover solution.
Here´s ahow to do a route-based VPN solution using the WebUI between two Netscreens:
Firewall A -> Internet -> Firewall B
- Log into Firewall A through the WebUI
Configure tunnel interface
-
- Click Network -> Interfaces
- Ensure the dropdown in the top left says Tunnel IF, click New
- Put it in the Untrust zone if you want all VPN traffic to pass throug my Untrust->Trust policy
- Click unnumbered and select the untrust interface
- click OK
- Configure your VPN Gateway
- Click VPNs -> AutoKey Advanced -> Gateway
- click New
- Name the gateway "FirewallB-gw"
- I always select the custom security level, you´ll see why in a following step
- Enter the public IP address of Firewall B
- Carefully enter your preshared key
- select untrust for your outgoing interface
- click advanced
- select User defined (custom)
- in the first dropdown select pre-g2-aes128-sha
- click return at the bottom
- click OK at the bottom
- Create the VPN
- on the menu on the left select VPNs -> Autokey Advanced
- click New
- name it FirewallB-vpn
- select Custom
- leave predefined checked and select your FirewallB-GW in the dropdown
- click Advanced
- select custom
- in the first dropdown, select g2-esp-aes128-sha
- turn on replay protection
- Bind to tunnel interface, and select your tunnel interface you created in step 2
- turn on VPN monitor (this will bring up the VPN right away and keep it up even when there´s no traffic on it)
- click Return
- click OK
- You need to add routes to the remote network. You can configure the tunnel interfaces to run OSPF, or you can add a static. I will tell you how to add a static.
- on the menu click Network -> Routing -> Destination
- click new
- type in the network address behind Firewall B
- Select Gateway
- Select your tunnel interface in the dropdown
- click ok
- Add your policy to allow access to/from the remote network. If you are not in NAT mode on your trust interface, make sure you check position at top when creating a Trust->Untrust rule, or it will NAT the traffic to your untrust IP or DIP pool and then send it across the tunnel, which you probably don´t want. Create an Untrust->Trust policy which allows access from the Network behind FirewallB to hosts or the network behind FirewallB. You probably want to allow Ping at a minimum.
- Repeat steps 1-6 on Firewall B. Substituting Firewall A´s data.
The VPN should pop up and everything should work. You can also use the little wizard thing, but I haven´t tried it. If you use it, I don´t think it picks the most secure cipher for P1 and P2, this is why we set this up manually. If one or both of your Netscreens is behind something that does NAT, you will also have to turn on NAT traversal on both ends.
If you don´t want static routes and want to use OSPF instead, you can create an OSPF instance under the trust VR. Make sure you add the tunnel interfaces and your internal interfaces to it, and tell it to advertise your private networks. You will then have to go under each interface that you added, and turn on OSPF. On tunnel interfaces, you can enable demand circuit and add it to the area, apply the changes, and then Enable OSPF on it.
