User manual

Basic Installation and Setup 2-3
3
Note: To verify your network settings, use the list networks
command. You can also check the connection by using the ping
<ip address> command.
2.
Set a default gateway. If the NETServer does not know where
to send a packet, it forwards the packet to the default
gateway or router addressed in this step. Default gateways
must be on the same subnet as the NETServer.
You also need to supply a metric (hop count) for each type of
default gateway. Possible values range from 1 (default) to
15. Note that since the actual metric of a default gateway is
only 1 hop, the value entered here is used to control the
perceived cost of the gateway to other routers on your
network. For example, a high metric will limit the number
of hops that the route is broadcast and may cause other
routers to see it as a less preferable route.
If the NETServer is configured to listen for IP default route
the IP Default Gateway can be overridden by a default route
broadcast with a lower hop count.
To add the default gateway, use the following command:
add ip defaultroute gateway
<defaultrout gateway ip address>
metric
<integer>
For example:
add ip defaultroute gateway 192.75.202.40 metric 1
Note: Check the default router setting with list ip routes.
Important: If you want to use a Domain Name Server (DNS),
continue below. If not, skip to step 6.
3.
Specify the IP address of the server you want to function as
the DNS server. The DNS server translates your host names
into their corresponding IP addresses - when queried - and
saves that information in its local host table.
NETServer supports one name service only - DNS. You can
name up to ten DNS servers using the command shown