TCP/IP协议详解：从理论到实战

需积分: 1 126 浏览量更新于2024-07-31 收藏 11.96MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

Introduction

This book describes the TCP/IP protocol suite, but from a different perspective than other texts on TCP/IP. Instead

of just describing the protocols and what they do, we'll use a popular diagnostic tool to watch the protocols in

action. Seeing how the protocols operate in varying circumstances provides a greater understanding of how they

work and why certain design decisions were made. It also provides a look into the implementation of the protocols,

without having to wade through thousands of lines of source code.

When networking protocols were being developed in the 1960s through the 1980s, expensive, dedicated hardware

was required to see the packets going "across the wire." Extreme familiarity with the protocols was also required

to comprehend the packets displayed by the hardware. Functionality of the hardware analyzers was limited to that

built in by the hardware designers.

Today this has changed dramatically with the ability of the ubiquitous workstation to monitor a local area network

[Mogul 1990]. Just attach a workstation to your network, run some publicly available software (described in

Appendix A), and watch what goes by on the wire. While many people consider this a tool to be used for

diagnosing network problems, it is also a powerful tool for understanding how the network protocols operate,

which is the goal of this book.

This book is intended for anyone wishing to understand how the TCP/IP protocols operate: programmers writing

network applications, system administrators responsible for maintaining computer systems and networks utilizing

TCP/IP, and users who deal with TCP/IP applications on a daily basis.

Organization of the Book

The following figure shows the various protocols and applications that are covered. The italic number by each box

indicates the chapter in which that protocol or application is described.

(Numerous fine points are missing from this figure that will be discussed in the appropriate chapter. For example,

both the DNS and RFC use TCP, which we don't show.)

We take a bottom-up approach to the TCP/IP protocol suite. After providing a basic introduction to TCP/IP in

Chapter 1, we will start at the link layer in Chapter 2 and work our way up the protocol stack. This provides the

required background for later chapters for readers who aren't familiar with TCP/IP or networking in general.

This book also uses a functional approach instead of following a strict bottom-to-top order. For example, Chapter

3 describes the IP layer and the IP header. But there are numerous fields in the IP header that are best described

in the context of an application that uses or is affected by a particular field. Fragmentation, for example, is best

understood in terms of UDP (Chapter 11), the protocol often affected by it. The time-to-live field is fully described

when we look at the Traceroute program in Chapter 8, because this field is the basis for the operation of the

program. Similarly, many features of ICMP are described in the later chapters, in terms of how a particular ICMP

message is used by a protocol or an application.

We also don't want to save all the good stuff until the end, so we describe TCP/IP applications as soon as we

have the foundation to understand them. Ping and Traceroute are described after IP and ICMP have been

discussed. The applications built on UDP (multicasting, the DNS, TFTP, and BOOTP) are described after UDP has

been examined. The TCP applications, however, along with network management, must be saved until the end,

after we've thoroughly described TCP. This text focuses on how these applications use the TCP/IP protocols. We

do not provide all the details on running these applications.

Systems Used for Testing

Every example in the book was run on an actual network and the resulting output saved in a file for inclusion in the

text. Figure 1.11 shows a diagram of the different hosts, routers, and networks that are used. (This figure is also

duplicated on the inside front cover for easy reference while reading the book.) This collection of networks is

simple enough that the topology doesn't confuse the examples, and with four systems acting as routers, we can

see the error messages generated by routers.

Most of the systems have a name that indicates the type of software being used: bsdi, svr4, sun, Solaris,

aix, slip, and so on. In this way we can identify the type of software that we're dealing with by looking at the

system name in the printed output.

A wide range of different operating systems and TCP/IP implementations are used:

BSD/386 Version 1.0 from Berkeley Software Design, Inc., on the hosts named bsdi and slip. This

system is derived from the BSD Networking Software, Release 2.0. (We show the lineage of the various

BSD releases in Figure 1.10.)

Unix System V/386 Release 4.0 Version 2.0 from U.H. Corporation, on the host named svr4. This is vanilla

SVR4 and contains the standard implementation of TCP/IP from Lachman Associates used with most

versions of SVR4.

SunOS 4.1.3 from Sun Microsystems, on the host named sun. The SunOS 4.1.x systems are probably the

most widely used TCP/IP implementations. The TCP/IP code is derived from 4.2BSD and 4.3BSD.

Solaris 2.2 from Sun Microsystems, on the host named Solaris. The Solaris 2.x systems have a different

implementation of TCP/IP from the earlier SunOS 4.1.x systems, and from SVR4. (This operating system is

really SunOS 5.2, but is commonly called Solaris 2.2.)

AIX 3.2.2 from IBM on the host named aix. The TCP/IP implementation is based on the 4.3BSD Reno

release.

4.4BSD from the Computer Systems Research Group at the University of California at Berkeley, on the host

vangogh.cs.berkeley.edu. This system has the latest release of TCP/IP from Berkeley. (This system

isn't shown in the figure on the inside front cover, but is reachable across the Internet.)

Although these are all Unix systems, TCP/IP is operating system independent, and is available on almost every

popular non-Unix system. Most of this text also applies to these non-Unix implementations, although some

programs (such as Traceroute) may not be provided on all systems.

剩余846页未读，继续阅读

shuzailiangcang

粉丝: 1
资源: 2

TCP/IP协议详解：从理论到实战

TCP-IP详解卷二：实现34(1-16)上部.rar

TCP-IP详解卷1：协议.pdf+TCP-IP详解卷二：实现.pdf

tf6310-tcp-ip.exe

jt808-tcp-netty-master.zip

基于zynq的xvc(xilinx virtual cable)实现tcp-jtag调试经验.pdf

假如有一台服务器的ip是192.168.0.100，现在我想实现只有ip地址是192.168.0.10 - 192.168.0.88的服务器可以ssh连接到这台服务器，请问可以用哪些方法可以实现呢？请详细描述下实现过程。

linux DNAT -A PREROUTING -s 192.168.1.26 -p tcp --dport 8033 -j DNAT --to-destination 192.168.1.206:8033 端口不同tcp&udp客户端192.168.1.26 8033与 服务端192.168.1.206 端口8033

有一台服务器IP为192.168.0.100现在想实现只有IP地址在192.168.0.10-192.168.0.00的服务器可以ssh连接到这台服务器，请问可以有哪些方法实现，请详细描述下实现过程

linux DNAT -A PREROUTING -s 192.168.1.26 -p tcp --dport 8033 -j DNAT --to-destination 192.168.1.206:8033 端口不同tcp&udp测试不通

ucos-iii-tcpip.a

linux DNAT -A PREROUTING -s 192.168.1.26 -p tcp --dport 8033 -j DNAT --to-destination 192.168.1.206:8033 端口不同tcp&udp192.168.1.26客户端8033 服务端192.168.1.206 端口8033

翻译#mount -t nfs -o nolock -o tcp 192.168.1.200:/nfs /mnt

-bind=192.168.30.11 \

计算机数据包分片命令,TCP-IPIP数据报分片实验

tcpreplay -i em2 -K -M 5000 --loop=0 --duration=1800 --unuque-ip xxx.pcap

centos7 -A FORWARD -p tcp -d 192.168.1.206 --dport 8033 -j ACCEPT

iptables的常用策略

最新资源

linux DNAT -A PREROUTING -s 192.168.1.26 -p tcp --dport 8033 -j DNAT --to-destination 192.168.1.206:8033 端口不同tcp&udp客户端192.168.1.26 8033与服务端192.168.1.206 端口8033