12.03.2015 Views

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

System Network<br />

Interface<br />

Name<br />

Virtual Domain<br />

IP<br />

Remote IP<br />

Administrative<br />

Access<br />

HTTPS<br />

PING<br />

HTTP<br />

SSH<br />

SNMP<br />

TELNET<br />

Description<br />

The name of the IPSec interface.<br />

Select the VDOM of the IPSec interface.<br />

If you want to use dynamic routing with the tunnel or be able to ping<br />

the tunnel interface, enter IP addresses for the local and remote<br />

ends of the tunnel. These two addresses must not be used<br />

anywhere else in the network.<br />

Select the types of administrative access permitted on this<br />

interface.<br />

Allow secure HTTPS connections to the web-based manager<br />

through this interface.<br />

Interface responds to pings. Use this setting to verify your<br />

installation and for testing.<br />

Allow HTTP connections to the web-based manager through this<br />

interface. HTTP connections are not secure and can be intercepted<br />

by a third party.<br />

Allow SSH connections to the CLI through this interface.<br />

Allow a remote SNMP manager to request SNMP information by<br />

connecting to this interface. See “Configuring SNMP” on page 143.<br />

Allow Telnet connections to the CLI through this interface. Telnet<br />

connections are not secure and can be intercepted by a third party.<br />

Optionally, enter a description up to 63 characters long.<br />

Interfaces only configurable with CLI <strong>com</strong>mands<br />

While nearly all types of interfaces can be configured from the GUI interface, a<br />

few, such as the loopback and inter-vdom virtual interface types, can only be<br />

configured using CLI <strong>com</strong>mands.<br />

Virtual interfaces are not connected to any physical devices or cables outside the<br />

<strong>FortiGate</strong> unit. They allow additional connections inside the <strong>FortiGate</strong> unit, which<br />

allow for more <strong>com</strong>plex configurations. Virtual interfaces also have the added<br />

benefit of speed - depending on CPU load they are considerably faster than<br />

physical interfaces. VLANs, loopback interfaces, and inter-vdom interfaces are all<br />

virtual interfaces.<br />

Loopback interface<br />

The loopback interface is a virtual interface. It was added to assist with blackhole<br />

routing where network traffic is just dropped. For more information on blackhole<br />

routing, see “Blackhole Routing” on page 234.<br />

A loopback interface is not connected to hardware, so it does not have hardware<br />

connection issues. As long as the <strong>FortiGate</strong> unit is functioning the loopback<br />

interface is active. This ‘always up’ feature is useful in a number of situations,<br />

such as dynamic routing.<br />

The CLI <strong>com</strong>mand to configure a loopback interface called loop1 with an IP<br />

address of 10.0.0.10 is:<br />

config system interface<br />

edit loop1<br />

set type loopback<br />

set ip 10.0.0.10 255.255.255.0<br />

end<br />

For more information, see config system interface in the <strong>FortiGate</strong> CLI Reference.<br />

<strong>FortiGate</strong> Version 3.0 MR5 <strong>Administration</strong> <strong>Guide</strong><br />

01-30005-0203-20070830 93

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

Saved successfully!

Ooh no, something went wrong!