通信网络实验报告

通讯网络实验报告实验一隐终端和裸露终端问题剖析一、实验目的1、认识无线网络中的载波检测体制；2、熟习节点的传输范围、矛盾扰乱范围、载波检测范围和噪声扰乱范围的观点；3、认识载波检测接入体系中存在的隐终端问题和裸露终端问题；4、联合仿真切验剖析载波检测无线网络中的隐终端问题和裸露终端问题。二、实验结果Node:1,Layer:AppCbrClient,(0)Serveraddress:2Node:1,Layer:AppCbrClient,(0)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(0)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(0)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(0)Throughput(bitspersecond):409600Node:2,Layer:AppCbrServer,(0)Clientaddress:1Node:2,Layer:AppCbrServer,(0)Firstpacketreceivedat[s]:Node:2,Layer:AppCbrServer,(0)Lastpacketreceivedat[s]:Node:2,Layer:AppCbrServer,(0)Averageend-to-enddelay[s]:Node:2,Layer:AppCbrServer,(0)Sessionstatus:NotclosedNode:2,Layer:AppCbrServer,(0)Totalnumberofbytesreceived:4975616Node:2,Layer:AppCbrServer,(0)Totalnumberofpacketsreceived:9718Node:2,Layer:AppCbrServer,(0)Throughput(bitspersecond):398078Node:3,Layer:AppCbrClient,(0)Serveraddress:4Node:3,Layer:AppCbrClient,(0)Firstpacketsentat[s]:Node:3,Layer:AppCbrClient,(0)Lastpacketsentat[s]:Node:3,Layer:AppCbrClient,(0)Sessionstatus:NotclosedNode:3,Layer:AppCbrClient,(0)Totalnumberofbytessent:5120000Node:3,Layer:AppCbrClient,(0)Totalnumberofpacketssent:10000Node:3,Layer:AppCbrClient,(0)Throughput(bitspersecond):409600Node:4,Layer:AppCbrServer,(0)Clientaddress:3Node:4,Layer:AppCbrServer,(0)Firstpacketreceivedat[s]:Node:4,Layer:AppCbrServer,(0)Lastpacketreceivedat[s]:Node:4,Layer:AppCbrServer,(0)Averageend-to-enddelay[s]:Node:4,Layer:AppCbrServer,(0)Sessionstatus:NotclosedNode:4,Layer:AppCbrServer,(0)Totalnumberofbytesreceived:5120000Node:4,Layer:AppCbrServer,(0)Totalnumberofpacketsreceived:10000Node:

4,Layer:

AppCbrServer,(0)Throughput(bitspersecond):409612三、实验结果剖析经过仿真结果能够看出，节点

2没法收到数据。因为节点

3是节点

1的一个隐终端，节点

1没法经过物理载波检测侦听到节点

3的发送，且节点

3在节点

2的传输范围外，节点3没法经过虚构载波检测延缓发送，因此在节点

1传输数据的过程中，节点

3达成退避发送时将惹起矛盾。四、思虑题1、RTS/CTS能完整解决隐终端问题吗？假如不可以，请说明原因。从理论剖析上看，RTS/CTS协议仿佛能够完整解决数据链隐蔽终端问题，但是在实质网络中并不是这样，特别是在AdHoc网络中。以节点为中心，存在发送地区和扰乱区域。在发送地区内，在没有扰乱的状况下，数据包可正常收发；该地区的大小由站点的功率等参数确立，可视为定值。扰乱地区是有关于接受节点而言的，在该地区内，节点能够遇到来自非有关节点发送的数据的扰乱，造成矛盾、丢包。RTS/CTS对隐蔽终端问题的屏蔽其实是成立在两地区相等的基础上的，即全部的隐蔽终端都位于接受节点发送范围内。其中假定其实不可立，扰乱地区与收发节点间距有关。实验二无线局域网DCF协议饱和吞吐量考证一、实验目的1、认识IEEEDCF协议的基来源理。2、理解网络饱和吞吐量的观点。3、经过仿真对DCF协议饱和吞吐量的二维马尔可夫链模型进行考证。二、实验结果Node:1,Layer:AppCbrClient,(4)Serveraddress:55Node:1,Layer:AppCbrClient,(4)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(4)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(4)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(4)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(4)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(4)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(3)Serveraddress:54Node:1,Layer:AppCbrClient,(3)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(3)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(3)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(3)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(3)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(3)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(2)Serveraddress:53Node:1,Layer:AppCbrClient,(2)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(2)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(2)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(2)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(2)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(2)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(1)Serveraddress:52Node:1,Layer:AppCbrClient,(1)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(1)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(1)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(1)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(1)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(1)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(0)Serveraddress:51Node:1,Layer:AppCbrClient,(0)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(0)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(0)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(0)Throughput(bitspersecond):409600Node:51,Layer:AppCbrServer,(0)Clientaddress:1Node:51,Layer:AppCbrServer,(0)Firstpacketreceivedat[s]:Node:51,Layer:AppCbrServer,(0)Lastpacketreceivedat[s]:Node:51,Layer:AppCbrServer,(0)Averageend-to-enddelay[s]:Node:51,Layer:AppCbrServer,(0)Sessionstatus:NotclosedNode:51,Layer:AppCbrServer,(0)Totalnumberof5102592Node:51,Layer:AppCbrServer,(0)Totalnumberof9966Node:51,Layer:AppCbrServer,(0)Throughput(bitspersecond):408219Node:52,Layer:AppCbrServer,(1)Clientaddress:1Node:52,Layer:AppCbrServer,(1)Firstpacketreceivedat[s]:Node:52,Layer:AppCbrServer,(1)Lastpacketreceivedat[s]:Node:52,Layer:AppCbrServer,(1)Averageend-to-enddelay[s]:Node:52,Layer:AppCbrServer,(1)Sessionstatus:NotclosedNode:52,Layer:AppCbrServer,(1)Totalnumberof5102592Node:52,Layer:AppCbrServer,(1)Totalnumberof

bytesreceived:packetsreceived:bytesreceived:packetsreceived:9966Node:52,Layer:AppCbrServer,(1)Throughput(bitspersecond):408233Node:53,Layer:AppCbrServer,(2)Clientaddress:1Node:53,Layer:AppCbrServer,(2)Firstpacketreceivedat[s]:Node:53,Layer:AppCbrServer,(2)Lastpacketreceivedat[s]:Node:53,Layer:AppCbrServer,(2)Averageend-to-enddelay[s]:Node:53,Layer:AppCbrServer,(2)Sessionstatus:NotclosedNode:53,Layer:AppCbrServer,(2)Totalnumberofbytesreceived:3926016Node:53,Layer:AppCbrServer,(2)Totalnumberofpacketsreceived:7668Node:53,Layer:AppCbrServer,(2)Throughput(bitspersecond):314112Node:54,Layer:AppCbrServer,(3)Clientaddress:1Node:54,Layer:AppCbrServer,(3)Firstpacketreceivedat[s]:Node:54,Layer:AppCbrServer,(3)Lastpacketreceivedat[s]:Node:54,Layer:AppCbrServer,(3)Averageend-to-enddelay[s]:Node:54,Layer:AppCbrServer,(3)Sessionstatus:NotclosedNode:54,Layer:AppCbrServer,(3)Totalnumberofbytesreceived:22016Node:54,Layer:AppCbrServer,(3)Totalnumberofpacketsreceived:43Node:54,Layer:AppCbrServer,(3)Throughput(bitspersecond):1761Node:55,Layer:AppCbrServer,(4)Clientaddress:1Node:55,Layer:AppCbrServer,(4)Firstpacketreceivedat[s]:Node:55,Layer:AppCbrServer,(4)Lastpacketreceivedat[s]:Node:55,Layer:AppCbrServer,(4)Averageend-to-enddelay[s]:Node:55,Layer:AppCbrServer,(4)Sessionstatus:NotclosedNode:55,Layer:AppCbrServer,(4)Totalnumberofbytesreceived:22016Node:55,Layer:AppCbrServer,(4)Totalnumberofpacketsreceived:43Node:55,Layer:AppCbrServer,(4)Throughput(bitspersecond):1761三、实验结果剖析各发送节点发包间隔较大，当网络中发送节点较少时，网络还未饱和。逐渐往网络中增添负载，网络总吞吐量逐渐增大，以后，网络吞吐量逐渐趋势于安稳，此时，网络即达到了饱和状态。四、思虑题1、总结IEEE协议饱和吞吐量和哪些要素有关。任选一个时隙，网络中有节点在发送数据的概率当有节点在发送数据包时，数据包发送成功的概率数据包发送成功和发送失败所需的时间2、为何在数据包长度较长时，采纳RTS/CTS模式更合理？隐蔽终端"多发生在大型单元中（一般在室外环境），这将带来效率损失，并且需要错误恢复体制。当需要传递大容量文件时，特别需要根绝"隐蔽终端"现象的发生。实验三动向源路由协议路由选择考证一、实验目的1、认识DSR路由协议的优弊端。2、理解DSR路由协议中路由发现过程和路由保护过程。3、掌握DSR路由协议性能的仿真剖析方法。二、实验结果Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:3-2Time(s):,Node:1,Routepath:3-2Time(s):,Node:1,Routepath:3-2Time(s):,Node:1,Routepath:3-2Time(s):,Nod