06.03.2015 Views

iPECS SBG-1000 User Manual

iPECS SBG-1000 User Manual

iPECS SBG-1000 User Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong> <strong>User</strong> <strong>Manual</strong> (DATA Features)<br />

Allow SNMP Control and Diagnostic Requests Used to allow Simple Network Management<br />

Protocol (SNMP) requests to remotely configure and monitor <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong>. For more<br />

information, refer to Section 6.7.2.<br />

Diagnostic Tools Used to allow the Ping and Traceroute utilities on a remote computer to<br />

communicate with <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong> in order to test its connectivity.<br />

TR-069 TR-069 is a WAN management protocol intended for communication between Customer<br />

Premise Equipment (CPE) and an Auto-Configuration Server (ACS). It defines a mechanism that<br />

encompasses secure auto configuration of a CPE, and also incorporates other CPE management<br />

functions into a common framework.<br />

To allow remote access to <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong>’s administrative services:<br />

1. Select the services that you would like to make available to computers on the Internet. The<br />

following should be taken into consideration:<br />

• Although the Telnet service is password-protected, it is not considered a secured protocol.<br />

When allowing incoming access to a Telnet server, if port forwarding is configured to use<br />

port 23, select port 8023 to avoid conflicts.<br />

• When allowing incoming access to the WBM, if one of your port forwarding rules is<br />

configured to use port 80, select port 8080 to avoid conflicts.<br />

Note: A remote administration service will have precedence over the port forwarding<br />

rule created for a local server, when both are configured to utilize the same port. For<br />

example, when both the Web server (running on your LAN host) and a remote<br />

administration service (utilized by the ISP) are configured to use port 80, <strong>iPECS</strong><br />

<strong>SBG</strong>-<strong>1000</strong> will grant access to the remote administration traffic. The traffic destined<br />

for your Web server will be blocked until you disable the remote administration<br />

service or change its dedicated port. For more information about the port forwarding<br />

rules created for local servers, refer to Section 5.2.3.<br />

2. Click ‘OK’ to save the settings.<br />

The encrypted remote administration over the Web, which is performed using a secure (SSL)<br />

connection, requires an SSL certificate. When accessing <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong> for the first time using<br />

encrypted remote administration, you will encounter a warning message generated by your<br />

browser regarding certificate authentication. This is due to the fact that <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong>’s SSL<br />

certificate is self-generated. When encountering this message under these circumstances, ignore it<br />

and continue.<br />

It should be noted that even though this message appears, the self-generated certificate is safe,<br />

and provides you with a secure SSL connection. It is also possible to assign a user-defined<br />

certificate to <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong>. To learn about certificates, refer to Section 6.9.4.<br />

If you wish to securely administrate <strong>iPECS</strong> <strong>SBG</strong>-<strong>1000</strong> via its CLI, establish a Telnet over SSL<br />

connection to the gateway by performing the following:<br />

1. Select the ‘Using Secure Telnet over SSL Port’ check box (see Figure 6.284). By default,<br />

307

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!