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

assume an IP address object called dns1_address has already been defined for the first DNS server,
the command to specify the first DNS server is:
Device:/> set DNS DNSServer1=dns1_address
Assuming a second IP object called dns2_address has been defined, the second DNS server is
specified with:
Device:/> set DNS DNSServer2=dns2_address
B. DHCP - automatic configuration
All required IP addresses can alternatively be automatically retrieved from the ISP's DHCP server
by enabling DHCP on the interface connected to the ISP. If the interface on which DHCP is to be
enabled is ge2, then the command is:
Device:/> set Interface Ethernet ge2 DHCPEnabled=Yes
Once the required IP addresses are retrieved with DHCP, CorePlus automatically sets the relevant
address objects in the address book with this information.
For CorePlus to know on which interface to find the public Internet, a route has to be added to the
main CorePlus routing table which specifies that the network all-nets can be found on the interface
connected to the ISP and this route must also have the correct Default Gateway IP address specified.
This all-nets route is added automatically by CorePlus during the DHCP address retrieval process.
Automatic route generation is a setting for each interface that can be manually enabled and disabled.
After all IP addresses are set via DHCP and an all-nets route is added, the connection to the Internet
is configured but no traffic can flow to or from the Internet since there is no IP rule defined that
allows it. As was done in the previous option (A) above, we must therefore manually define an IP
rule that will allow traffic from a designated source interface and source network. (in this example,
the network ge3_net and interface ge3) to flow to the destination network all-nets and the
destination interface ge2.
C. PPPoE setup
For PPPoE connection, create the PPPoE tunnel interface on the interface connected to the ISP. The
interface ge2, is assumed to be connected to the ISP in the command shown below which creates a
PPPoE tunnel object called wan_ppoe:
Device:/> add Interface PPPoETunnel wan_ppoe
EthernetInterface=ge2 username=pppoe_username
Password=pppoe_password Network=all-nets
Your ISP will supply the correct values for pppoe_username and pppoe_password.
Your 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 CorePlus 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 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.
3.4. CLI Setup
Chapter 3. CorePlus Configuration
50