Managing M1112
E Copyright Nokia Networks Oy
C33907001SE_00
5-5
Automatically generated address ranges use LAN/VBRIDGE IP
address as gateway and DNS server addresses. If one address range is
defined, then automatic binding will be disabled. If optional address
range parameters like gateway or DNS addresses are not defined,
LAN/VBRIDGE IP addresses are used as in automatic binding.
Typically, when DHCP is used, the advertised DSN addresses point to
LAN/VBRIDGE interfaces. In such cases, the DNS proxy forwards
the DNS request to statically configured DNS servers or to DNS
servers learned dynamically vie PPP/IPCP.
The following commands are used to configure DHCP and DNS
settings:
M1112(conf-common)#dhcp?
usage: dhcp mode
dhcp address
dhcp gateway
dhcp dns
dhcp lease-time
dhcp domain-name
M1112(conf-common)#dhcp mode server ; this enables
DHCP server
Normally, there is no need to configure the DNS addresses. If the
service provider does not support automatic DNS address allocation,
the DNS servers can be configured as shown by the following
example:
M1112(conf-common)# dns address primary 1.2.3.4
M1112(conf-common)# dns address secondary 1.2.3.5
M1112(conf-common)#
5.2.2 Configuring static and dynamic routing
Routing entries in the routing table are needed in order to forward the
IP packets to the correct interface. M1112 has both static and dynamic
routes. Static routes are configured manually and dynamic routes are
learned automatically using RIP v1 and RIP v2 protocols. The
following examples show how to configure static routes to M1112.
Default gateway for an interface that learns the next hop automatically:
M1112(conf-common)# ip route 0.0.0.0 0.0.0.0 0.0.0.0
vcc1