Eagle Access Control Systems Eagle-E7 Specifications download pdf (Page 49)

For PPPoE connection, we must create a PPPoE tunnel interface associated with the physical

Ethernet interface. Assume that the physical interface is G2 and the PPPoE tunnel object created

is called wan_pppoe. Go to Network > Interfaces and VPN > PPPoE and select Add > PPPoE

Tunnel. These values can now be entered into the PPPoE Tunnel properties dialog.

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 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 interface and source network (in this example, the network G3_net and interface G3) to

flow to the destination network all-nets and the destination interface which 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 10.5.4.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.

Chapter 4: cOS Core Configuration

1 2 ... 44 45 46 47 48 49 50 51 52 53 54 ... 83 84

No comments

Eagle Access Control Systems Eagle-E7 Specifications Page 49