As was done for HTTP, NAT should also be enabled with this IP policy so all DNS queries are sent
out by cOS Core with the outgoing interface's IP address as the source IP.
For the Internet connection to work, a
route
also needs to be defined so that cOS Core knows on
which interface web browsing traffic should leave the firewall. This route defines the interface
where the network
all-nets
(in other words, any network) will be found. If the default
main
routing table is opened by going to Network > Routing > Routing Tables > main, the route
needed should appear as shown below.
This
all-nets
route is added automatically when the
Default Gateway
for an Ethernet interface is
specified, as was done earlier when setting up the required
IP4 Address
objects.
Note: Disabling automatic route generation
Automatic route generation is enabled and disabled with the setting "
Automatically
add a default route for this interface using the given default gateway
" which can
be found in the properties of the interface.
As part of the setup, it is also recommended that at least one DNS server is also defined in cOS
Core. A DNS server or servers (a maximum of three can be configured) will be used when cOS
Core itself needs to resolve URIs, such as with FQDN address objects. It can also be important for
certificate handling.
Assume an IPv4 address object called
wan_dns1
has already been defined in the address book
and this is the address for the first DNS server. By choosing System > Device > DNS, the DNS
server dialog will open and this object from the address book can be assigned as the first server.
Chapter 4: cOS Core Configuration
51
Содержание NetWall 100 Series
Страница 1: ...Clavister NetWall 100 Series Getting Started Guide...
Страница 16: ...Chapter 1 NetWall 100 Series Overview 16...
Страница 31: ...Chapter 3 Installation 31...
Страница 72: ...Chapter 4 cOS Core Configuration 72...