09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• Ease of use<br />

• Reliability<br />

• Control<br />

• Security<br />

• Efficiency<br />

The reason static routing is so popular is because of its ease of use,<br />

reliability, and control. UNIX/NT system administra<strong>to</strong>rs (who usually<br />

get stuck with managing <strong>the</strong> IP <strong>network</strong>) are <strong>the</strong> most common<br />

advocates of <strong>the</strong> use of static routes. System administra<strong>to</strong>rs love its<br />

simplicity almost as much as <strong>the</strong>y love having control over what goes<br />

on with <strong>the</strong> systems <strong>the</strong>y administer. Static routing can be set up on<br />

most modern operating systems'TCP/IP implementations.<br />

An administra<strong>to</strong>r can build a master route table for <strong>the</strong> <strong>network</strong> and<br />

distribute it <strong>to</strong> end-stations so <strong>the</strong> routes are added <strong>to</strong> <strong>the</strong> local table<br />

when <strong>the</strong> system boots up. If a change is needed, <strong>the</strong> file can be<br />

copied over <strong>the</strong> <strong>network</strong> <strong>to</strong> <strong>the</strong> end-stations, <strong>the</strong> is rebooted, and <strong>the</strong><br />

new route is added. Although ease of use is always an advantage, <strong>the</strong><br />

bigger win with using static routing table entries is <strong>the</strong> control and<br />

reliability <strong>the</strong>y provide. Because static routing tables are entered<br />

manually, unless a is made or a hardware failure occurs, <strong>the</strong> tables<br />

are absolutely correct. Dynamic routing pro<strong>to</strong>cols can fail or be<br />

misconfigured. They also suffer from <strong>network</strong> convergence latency<br />

and potential routing loops.<br />

It is commonly held that static routing provides an element of security.<br />

Fundamentally, this is true. An end-station cannot reach a <strong>network</strong> <strong>to</strong><br />

which it has no route. This approach is not exactly security in <strong>the</strong><br />

formal sense but ra<strong>the</strong>r, "security through obscurity." It accomplishes<br />

<strong>the</strong> same end goal that a traditional security approach would—limiting<br />

<strong>network</strong> availability through <strong>the</strong> use of access control lists (ACLs). But,<br />

it does so by an obscure means (omitting routes from certain<br />

workstations), instead of a secure one (creating an access list that<br />

only allows certain hosts <strong>to</strong> access <strong>the</strong> <strong>network</strong> segment and reporting<br />

when an attempt is made by an end-station that is not permitted).<br />

Although static routing might fall short on <strong>the</strong> security side, it makes<br />

up forit in efficiency. If static routing is anything, it is <strong>network</strong> and<br />

router friendly. Dynamic routing pro<strong>to</strong>cols add <strong>to</strong> <strong>network</strong> traffic and<br />

use memory and processor cycles on <strong>the</strong> router. With static routing,<br />

none of <strong>the</strong> router resources are used for route acquisition and no<br />

additional <strong>network</strong> traffic is generated by sending and receiving<br />

dynamic routing updates.

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

Saved successfully!

Ooh no, something went wrong!