443
DP-C405/C305/C265
FEB 2008
Ver. 1.1
5. Managing Network Route Tables
In the simplest case a router connects two network segments. In this model, the system used to join
the two segments needs to know only about these segments.
The routing table for router R1 in this case is simple; the following table shows its key routes:
When the Unit at 192.168.3.5 attempts to communicate with the Unit at 192.168.1.x, IP performs the
ANDing process to find two things: The local network ID is 192.168.3.0, and the destination network ID
is not. This means, that the destination host is not on the local network.
IP, is responsible to find a route to the remote network, and therefore, it consults the routing table.
Here, the local host normally determines that the next step in the route is the Default Gateway, and
sends the packet to router R1.
The router R1, receives the packet. After determining that the packet is for another host and not the
router itself, it checks the routing table. It finds the route to 192.168.1.0 and sends the packet through
the interface to the Unit at 192.168.1.x, which receives the packet. This is a simple route that took only
a single hop.
When another network is added as the number of hosts grows, it gets complicated, and the systems on
the most distant networks cannot communicate. When the router receives a packet in this case, it
cannot find a route to the remote network. It then discards the packet and a message indicating
"destination host unreachable" is sent to the originator.
Here, is where the ROUTE command-line utility is useful when dealing with more than two networks,
and is used by Administrators to statically manage a route table by adding, deleting, changing and
clearing the route table. It has a number of options that are used to manipulate the routing tables, some
are shown below:
• MASK
If this switch is present, the next parameter is interpreted as the netmask parameter.
• Netmask
If included, specifies a sub-net mask value to be associated with this route entry. If not specified, it
defaults to 255.255.255.255.
• Gateway
Specifies the gateway.
• METRIC
Specifies the metric / cost for the destination.
All symbolic names used for the destination are looked up in the network database file NETWORKS.
The symbolic names for the gateway are looked up the host name database file HOSTS.
Network Address
Netmask
Gateway
Interface
192.168.3.0
255.255.255.0
192.168.3.254
192.168.3.254
192.168.1.0
255.255.255.0
192.168.1.253
192.168.1.253
Summary of Contents for Workio DP-C305
Page 2: ...2...
Page 3: ...3...
Page 5: ...5...
Page 6: ...6 For PB and Other Destinations not for PU USA Canada...
Page 11: ...11...
Page 12: ...12...
Page 13: ...13...
Page 14: ...14 memo...
Page 220: ...220 FEB 2008 Ver 1 1 DP C405 C305 C265 Color Test Chart 101 P N PJQRC0119Z LDR PJQRC0120Z A3...
Page 232: ...232 FEB 2008 Ver 1 1 DP C405 C305 C265 3 20 720K PM Kit DQ M35S72 DQ M32N72...
Page 400: ...400 FEB 2008 Ver 1 1 DP C405 C305 C265 LVPS CN6 LVPS CN7 Refer to SCN PC Board...
Page 401: ...401 FEB 2008 Ver 1 1 DP C405 C305 C265 LVPS CN8 Europe Specification Only...
Page 404: ...404 FEB 2008 Ver 1 1 DP C405 C305 C265 CST PCB CN603 CST PCB CN604...
Page 405: ...405 FEB 2008 Ver 1 1 DP C405 C305 C265 CST PCB CN605...
Page 406: ...406 FEB 2008 Ver 1 1 DP C405 C305 C265...
Page 407: ...407 FEB 2008 Ver 1 1 DP C405 C305 C265 CST PCB CN606...
Page 408: ...408 FEB 2008 Ver 1 1 DP C405 C305 C265...
Page 409: ...409 FEB 2008 Ver 1 1 DP C405 C305 C265 CST PCB CN607...
Page 410: ...410 FEB 2008 Ver 1 1 DP C405 C305 C265 CST PCB CN608...
Page 412: ...412 FEB 2008 Ver 1 1 DP C405 C305 C265 TRU PCB CN613...
Page 414: ...414 FEB 2008 Ver 1 1 DP C405 C305 C265 RLB PCB CN176...
Page 615: ...615 DP C405 C305 C265 FEB 2008 Ver 1 1 1 2 3 4 5 6 7 8...
Page 752: ...752 FEB 2008 Ver 1 1 DP C405 C305 C265 memo...
Page 847: ...847 DP C405 C305 C265 FEB 2008 Ver 1 1 2 Motor PCBs Fig 5 009 M1 M2 M8 M5 M4 M3 M7 M6 1...
Page 919: ......
Page 920: ...Published in Japan...