Wide Area Network WAN
14.2.2 Wide Area Network WAN
Local area networks have revolutionized data transmission, and a number of new technologies for fast data transmission have been developed and implemented. An enormous quantity of data unimaginable in the past has become available through networking, promoting distributed data processing. Processing resources, and power, could be spread over the network and used more efficiently. Therefore, a distributed environment and the long−held dream of the processors pool that could handle incoming requests in an optimal way has become a reality. Despite all of their advantages, LANs can only connect computers that are geographically close. How could two computers on two sides of a city communicate, or two computers in two distant cities, or states, or even continents? LAN technologies are not very useful in these cases, and more traditional and expensive telecommunication techniques must be implemented. If two distant LANs are connected with a fast link, all participating hosts think that they share an equivalent fast computer network, regardless of what the actual distance between those hosts is. In this fashion, we now have a Wide Area Network WAN, as seen in Figure 14.2. In WANs there is always more traffic between neighboring hosts within the same LAN than among distant ones because many hosts run strictly local network applications; this means that the inter−LAN link could be even slower than LANs themselves, while WAN throughput remains acceptable. 324 Figure 14.2: Wide area network. WANs are widely used, and they are constantly evolving. Today, numerous WANs are connected into a unique worldwide WAN, a global computer network known as the Internet. Multiplying LANs within WANs had two positive effects: it decreased the costs of the requested links which became shorter and were shared among more participating LANs and provided alternative routes to reach any host in the network. However, the problem of reaching a distant host in a network still had to be solved. Special addressing mechanisms to uniquely identify each host in the WAN were implemented, and appropriate routing algorithms to transmitretransmit data in the network were developed. Special, dedicated hosts, known as routers have become a part of each LAN, with their only mission to route data toward distant LANs and hosts. There are many different LANs currently in use, and they are often mutually incompatible: different media, modulation techniques, protocols, etc. just compare Ethernet and Token−Ring LANs for a look at the variety possible. However, such different and incompatible LANs often need to be connected together. Therefore, special devices to overcome such incompatibility must be implemented, and in the case of protocol conversion, these devices are known as gateways. The terms gateway and router are often used interchangeably, mostly because gateways also provide routing services. However, the two terms are not interchangeable — routing and protocol conversions are two independent concepts, and they are not necessarily complementary. 325 The common thread that ties the enormous Internet community together is TCPIP network software. The name TCPIP refers to an entire suite of data communication protocols that define how different types of computers talk to each other. The suite gets its name from two of the protocols that belong to it: the transmission control protocol TCP and the Internet protocol IP. Although there are a number of other protocols in the suite, TCP and IP are the best known. In 1969 the Defense Advanced Research Projects Agency DARPA started a research and development project to create an experimental packet switching network. This network was named A R P A N E T , and was built to explore techniques for providing robust, reliable, and vendor−independent data communications. The project outputs far surpassed all expectations, and a number of modern data communication techniques were developed, or at least conceptually solved. The experimental ARPANET was so successful that many of the organizations attached to it began to use it for their daily needs. In 1975 the ARPANET was converted from an experimental network to an operational one, and the responsibility for administering the network was given to the Defense Communications Agency DCA, later renamed the Defense Information System Agency DISA. However, the development of ARPANET did not stop once the network became operational; the basic TCPIP protocols were developed after ARPANET was operational. In 1983 the TCPIP protocols were adopted as MIL standards, and all hosts computers connected to the network were required to convert to the new protocols. To ease this conversion, DARPA funded an expert team to implement TCPIP in BSD UNIX, thus beginning the marriage of UNIX and TCPIP and their triumphant, long−lasting journey. BBN Bolt, Beraneck and Newman, was chosen to facilitate the implementation. The company, located in Boston, MA, was well known in the field of acoustics. As it was located close to MIT the Massachusetts Institute of Technology, it attracted talented MIT graduates and very quickly gained a strong reputation in computer technologies. The project was a real success and was completed extraordinarily well. Todays Internet fully relies on the solutions introduced by BBN. UNIX itself also contributed to the development of inter−computer communication. Besides the TCPIP protocols used primarily to communicate throughout the local area network and more widely, UNIX also provides UUCP for communication with remote, isolated computer sites.14.3.1 TCPIP and the Internet
Parts
» Unix Administration. 7485KB Mar 29 2010 05:04:17 AM
» UNIX Operating System UNIX — Introductory Notes
» Berkeley Standard Distribution — BSD UNIX System V or ATT UNIX
» System Administrators Job UNIX System and Network Administration
» Computing Policies UNIX System and Network Administration
» Legal Acts Administration Guidelines
» Code of Ethics Administration Guidelines
» USENIX System Administrators Guild — SAGE
» In This Book UNIX System and Network Administration
» Introduction The Unix Model — Selected Topics
» Access Classes File ProtectionFile Access
» Default File Mode File ProtectionFile Access
» Plain Regular File Socket Named Pipe
» Special File Names Special File Creation
» Process Types Process Attributes
» Process Life Cycles Processes
» System V ATT Flavored ps Command
» Destroying Processes The UNIX kill command will eliminate a process entirely:
» Becoming a Superuser Communicating with Other Users
» The man Command UNIX Online Documentation
» The uptime Command The uptime command displays:
» Personal Documentation UNIX Administration Starters
» Shell Script Execution UNIX Shell Scripts
» Shell Variables UNIX Shell Scripts
» Double Command−Line Scanning
» Introductory Notes System Startup and Shutdown
» The Bootstrap Program System Startup
» The Kernel Execution System Startup
» System States System Startup
» The Outlook of a Startup Procedure
» Initialization Scripts System Startup
» The BSD rc Scripts BSD Initialization Sequence
» BSD−Like Initialization System V Initialization
» An Example Shutdown Procedures
» Introduction to the UNIX Filesystem
» System V Filesystem Directory Organization
» Mounting a Filesystem home, users
» Dismounting a Filesystem home, users
» Automatic Filesystem Mounting Removable Media Management
» BSD Filesystem Configuration File
» Filesystem Types A Few Other Filesystem Issues
» Swap Space — Paging and Swapping
» Loopback Virtual Filesystem A Few Other Filesystem Issues
» Display Filesystem Statistics: The df Command
» Checking Filesystems: The fsck Command
» Introduction UNIX Filesystem Layout
» Disk Partitions Physical Filesystem Layout
» Filesystem Structures Physical Filesystem Layout
» The mkfs Command Filesystem Creation
» File Identification and Allocation
» File Storage vs. File Transfer
» Reserved Free Space Filesystem Performance Issues
» Logical Volume Manager — AIX Flavor
» Logical Volume Manager — Solaris Flavor
» Redundant Array of Inexpensive Disks RAID
» The Volume Snapshot Snapshot
» The Filesystem Snapshot Snapshot
» Virtual UNIX Filesystem Logical Filesystem Layout
» Disk Space Upgrade UNIX Filesystem Layout
» User Database — File etcpasswd
» Initialization Template Files UNIX Login Initialization
» User Login Initialization Files
» Systemwide Login Initialization Files
» Restricted User Accounts Users and Secondary Groups
» Assigning User Passwords Standard UNIX Users and Groups
» Managing Disk Usage by Users
» System V Accounting Accounting
» AIX−Flavored Accounting Accounting
» Physical Security Passwords UNIX Lines of Defense
» File Permissions UNIX Lines of Defense
» Backups Password Encryption UNIX Lines of Defense
» Setting Password Restrictions UNIX Lines of Defense
» The Wheel Group Secure Terminals — Other Approaches
» History of the Root Account Tracking User Activities
» The syslogd Daemon The Concept of System Logging
» The Configuration File etcsyslog.conf
» Linux Logging Enhancements The logger Command
» Testing System Logging System Logging Configuration
» The last Command Limiting the Growth of Log Files
» BSD Printing Subsystem UNIX Printing Subsystem
» The lp, lpstat, and cancel Commands
» The etcprintcap File BSD Printer Configuration and the Printer Capability Database
» Filters BSD Printer Configuration and the Printer Capability Database
» The Printer Database Directory Hierarchy on System V
» Setting a Remote Printer on HP−UX
» BSD and AIX Cross−Printing Solaris and BSD Cross−Printing
» Third−Party Printer Spooling Systems
» The tput Command The tset, tput, and stty Commands
» The stty Command The tset, tput, and stty Commands
» The tar Command Tape−Related Commands
» The cpio Command Tape−Related Commands
» The dd Command Tape−Related Commands
» The mt Command Magnetic Tape Devices and Special Device Files
» The SVR3 and SVR4 backup Commands
» The fbackup Command Backup and Dump Commands
» The dumpufsdump Command Backup and Dump Commands
» Interactive Restore The restore Commands
» The frecover Command Restoring Files from a Backup
» Tape Control UNIX Backup and Restore
» The NTP Daemon Network Time Distribution
» The crontab Files Network Time Distribution
» The crontab Command Network Time Distribution
» Linux Approach Network Time Distribution
» Programs Scheduled for a Specific Time
» UNIX and Networking Network Fundamentals
» TCPIP and the Internet ISO OSI Reference Model
» TCPIP Protocol Architecture Computer Networks
» Internet Protocol IP Internet Layer and IP Protocol
» Network Access Layer Transport Layer and TCP and UDP Protocols
» Application Layer TCPIP Layers and Protocols
» IP Address Classes Data Delivery
» Dynamic Routing Internet Routing
» Protocols, Ports, and Sockets
» UNIX Database Files Multiplexing
» The arp Command Address Resolution ARP
» The portmapper Daemon The etcrpc File
» The ifconfig Command Configuring the Network Interface
» The netstat Command Configuring the Network Interface
» The inetd Daemon Super Internet Server
» Further Improvements and Development
» Host Names and Addresses Domain Name Service DNS
» The Local Host Table — etchosts
» Handling the NIC Host Table — A Journey into the Past
» Other Resolver Parameters BIND Configuration
» Name Servers UNIX Name Service — BIND
» The Configuration File etcnamed.boot
» The named.local File The named.cache file
» Subdomains and Parenting BIND Version 8.X.X
» The nslookup Interactive Mode
» A Few Examples of nslookup Usage
» Purpose and Concepts Network Information Service NIS
» To Create an NIS Client NIS Domain Name
» The etcnetgroup File DatabasesNIS Maps
» Security Issues NIS Management
» The showmount Command Mounting Remote Filesystems
» An Example The Automount Maps
» The rlogin Command The rcp Command
» The HOME.rhosts File Using UNIX r−Commands — An Example
» SSH Configuration Secure Shell SSH
» Root Access SSH Installation and User Access Setup
» SSH — Version 2 Secure Shell SSH
» Simple Mail Transport Protocol SMTP
» Rewriting an E−mail Address Pattern Matching
» Address Transformation The Parsing of E−mail Addresses
» Testing Rewrite Rules The sendmail −bt Command
» The Debugging Level Checking the Mail Queue
» Mail Subcommands The Mail Program and .mailrc File
» POP Transactions Post Office Protocol POP
» Internet Message Access Protocol IMAP
» Finger Common UNIX Network Applications
» The ping Command Host Connectivity
» The traceroute Command Host Connectivity
» The X Administration Philosophy
» Window Managers An Introduction to the X Window System
» xdm Configuration Files The X Display Managers
» Vendor−Specific X Flavors — a Configuration Example
» XDMCP Queries The Xaccess File
» Other Access Control Mechanisms
» Components of the xdm−Based User X Environment
» Other Startup Methods The User X Environment
» A Permanent X11 Installation
» Introduction to Kernel Reconfiguration
» Kernel Configuration Database Kernel Reconfiguration
» The config Command BSD−Like Kernel Configuration Approach
» HP−UX 10.x Kernel Configuration
» UNIX and Modems Introduction to Modems
» Terminal Lines and Modem Control
» C−Kermit Third−Party Communication Software
» UUCP Versions UUCP Chat−Transfer Session
» The UUCP Daemons UUCP Commands, Daemons, and Related Issues
» The UUCP Spool Directories and Files
» Additional Security in BNU UUCP
» Additional Security in Version 2 UUCP
» Intranet vs. Internet Introduction to Intranet
» Intranet Design Approach Introduction to Intranet
» Life Cycle of a Virus Virus Types
» The Viruswall Implementation Viruswalls
» Application Proxies SOCKS Proxies
» Web Services Intranet Front−End Services
» Other External Services Intranet Front−End Services
» Network Infrastructure and Desktops
» Dynamic Host Configuration Protocol DHCP
» UNIX and Not−UNIX Platform Integration
» HP−UX Installation UNIX Installation Procedures
» Linux Installation UNIX Installation Procedures
» Solaris Patch Installation HP−UX Patch Installation
» Solaris and Lost Root Password HP−UX and Lost Root Password
» Solaris Procedure to Create an Alternate Boot Partition
» Solaris Recovery of the Failed Mirrored Boot Disk
Show more