All right so we have finished the first setup.
We have created Phase 1 Phase 2 in our IP SEC tunnel.
And we have also created a firewall address object of the remote locale.
Now let's create a static crowd that will tell our 48 how to reach the remote local area network.
So we will move over to network static crowd
and let's create a new standard crowd.
We'll use the name to address since we have configured the remote IP seq land address object and our
interface is the
two branch IP set tunnel interface.
We're not using the web interface we're using the new virtual interface that was created once we have
setup our tunnel.
All right so we also have a static crowd.
And now let's configure the policy the policy that will allow our local area network to reach the remote
local area network.
So we we'll name it to remote IP Sec.
The incoming interface is our new virtual adapter which is the two branch channel interface.
The outgoing is our well interface source can be all we can also set up a user group or a specific users.
But for now we will use the whole destination all service all.
We do not need.
In our policy and that's our first policy to remote IP sec.
Now let's create this second policy
from a remote IP sac and this policy will be the opposite.
That's the policy that will allow traffic coming from our or when reaching our new VPN.
All right.
So we have to two policies in place to allow traffic between our remote local area network and our local
area network using IP SEC VPN.
No we have actually finished setting up our VPN tunnel from our site.
The next thing to do is to setup the remote for the gate the remote 48 it will be setup exactly the
same using the same pressure key the same encryption algorithm the same in different phases the same
hash values.
The only difference is the IP addresses of the remote Gateway and the remote local area network which
should be configured in the Phase 1 and Phase 2 configuration.
Another thing to do is to setup the policies the security policies and the static route.