Clavister NetWall 6000 Series, Руководство по началу работы, Страница: 68 / 99

PPPoE 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 set entry defined that
allows it. As was done in option
A above, we must define an IP policy that will allow traffic from
the 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 PPPoE
tunnel.
D. PPTP setup
For PPTP connection, first define the PPTP tunnel interface. The following command will create a
PPTP tunnel object called
wan_pptp with the remote endpoint 203.0.113.1 :
Device:/> add Interface L2TPClient wan_pptp
Network=all-nets
username=pptp_username
Password=pptp_password
RemoteEndpoint=203.0.113.1
TunnelProtocol=PPTP
Your 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 an Ethernet 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 .
As with all automatically added routes, if the PPTP tunnel object is deleted then this route is also
automatically deleted.
At this point, no traffic can flow through the tunnel since there is no IP rule set entry defined that
allows it. As was done in option
A above, we must define an IP policy that will allow traffic from
the source network and source interface (in this example, the network G1_net and interface G1 )
to flow to the destination network all-nets and destination interface, which is the PPTP tunnel.
Activating and Committing Changes
After any changes are made to a cOS Core configuration, they will form a new configuration but
will not yet be activated. To activate new configuration changes, the following command must
be entered:
Device:/> activate
Although the new configuration is now activated, it does not become permanently saved until
the following command is issued within 30 seconds following the
activate :
Device:/> commit
The reason for having a two command sequence is to prevent the new configuration
accidentally locking out the administrator. If a lock-out occurs then the
commit command cannot
be received and cOS Core will automatically revert back to the original configuration after the 30
second time period (this time period is a setting that can be changed).
Chapter 4: cOS Core Configuration
68