Clavister Eagle E20, Руководство по началу работы

Страница: 47 / 76

An ISP will supply the correct values for pptp_username , pptp_password and the remote
endpoint. An interface is not specified when defining the tunnel because this is determined by
cOS Core looking up the
Remote Endpoint IP address in its routing tables.
The PPTP client tunnel interface can now be treated exactly like a physical interface by the
policies defined in cOS Core rule sets.
There also has to be an associated route with the PPTP tunnel to allow traffic to flow through it,
and this is automatically created in the
main routing table when the tunnel is defined. The
destination network for this route is the Remote Network specified for the tunnel and for the
public Internet this should be all-nets .
If we go to Network > Routing > Routing Tables > main we can see this route.
If the PPTP tunnel object is deleted, this route is also automatically deleted.
At this point, no traffic can flow through the tunnel since there is no IP rule defined that allows it.
As was done in option A above, we must define an IP rule that will allow traffic from a designated
source network and source interface (in this example, the network
G1_net and interface G1 to
flow to the destination network all-nets and the destination interface which is the PPTP tunnel
that has been defined.
DHCP Server Setup
If the Clavister Security Gateway is to act as a DHCP server then this can be set up in the following
way:
First, create an IP4 Address object which defines the address range to be handed out. Here, it is
assumed that this has the name dhcp_range . It is also assumed that another IP4 Address object
dhcp_netmask has been created which specifies the netmask.
We now create a DHCP server object called dhcp_lan which will only be available on the G1
interface. To do this, go to Network > Network Services > DHCP Servers and select Add >
DHCP Server. The server properties can now be specified.
Chapter 4: cOS Core Configuration
47