Clavister NetWall 100 Series, Руководство по началу работы

Страница: 53 / 81

An ISP will supply the correct values for pppoe_username and pppoe_password in the dialog
above.
The PPPoE 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 a route associated with the PPPoE tunnel to allow traffic to flow through it,
and this is automatically created in the
main routing table when the tunnel is defined. If we go to
Network > Routing > Routing Tables > main we can see this route.
If the 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 rule set entry that will allow traffic
from the source network and source interface to flow to the destination network
all-nets and the
destination interface. Here, the destination interface is the PPPoE tunnel that has been defined.
D. PPTP setup
For PPTP connections, a PPTP client tunnel interface object needs to be created. Let us assume
that the PPTP tunnel will be called
wan_pptp with a remote endpoint 203.0.113.1 which has been
defined as the IP4 Address object pptp_endpoint . Go to Network > Interfaces and VPN >
PPTP/L2TP Clients and select Add > PPTP/L2TP Client. The values can now be entered into the
properties dialog and the
PPTP option should be selected.
Your ISP will supply the correct values for pptp_username , pptp_password and the remote
endpoint. An Ethernet 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
Chapter 4: cOS Core Configuration
53