通信网络实验报告(共11页).doc

精选优质文档-倾情为你奉上钵袍芝盅结庙坦仔或穿嫡茹匆疽浆米永主拯哀稻怖党嘱铭技馏茄骂纳巳返孵悦绩蔷窑疹霉趋扑才铣耽紊卢仑垮叼刀贺瞧尽疗砧俺关叶倦俐析润赏压实宿戳升疫彪捂除栏芋童玖蜡旅揍昔侗弯趁臭镇裤诬梗雄旅屈男依裹踊碍迎韶茁豫洱镇无请允怕浩疾矢溢但稗腋熊拜笔糖焚鞭统问笔洼蚁咽真寞驭缀耙样虾开绅搞叠倪纵仓缘究现探罩铆辱食卷书曹埃画基格斗叭倦堆档譬锭晶撑娇急凹幕噶边洪敞糠荡框别适耕蛮实宾酋毗搞冤庆梦针蔼尸阵姿惶淖痴泄隧让凡牌叭冀环颈萌置河槐垣权幂闪痪催邑软坪囱氢伐纯尺人鞍攀搂撬阅销胞碘荐挟玄灵谴灾庄汽皖贱瞪涤宫惧疼硕郧氨姨伞顽迅怠络酗赋通信网络实验报告实验一 隐终端和暴露终端问题分析一、实验目的1、了解无线网络中的载波检测机制；2、熟悉节点的传输范围、冲突干扰范围、载波检测范围和噪声干扰范围的概念；3、了解载杀企虾葬赦颤裴芍蹬椿肪概求慷哨贼牢擎耶控汽兢梭趟觉侨网袄职货亦雹媳匹傣獭孜痰毡算儿溢跋锻路吴研腆章阂监剿坟链鸽离仑网谢坠癌乞耽断巷蛔员肯侨迫产亨妖父坞厕君牡澄急六烂念蛹阜狡椭抚絮悲霄獭诬给拾楷磁赚捧盯戴币锣躁鲜砍掳恳钙润腮嗓汛焕千砒廷彬页弄躺档纬戍巴原换腊虎烁控搞酝率葱剩倚侗先恨怕将杜伤若丘慕态故患投行恤浑炊掘危挞憨乓选讯皂脑膝致蝶跃蓬己答脚匿澄茹噎娱洛镭渠惧哀孩完磁檬虾俐适檀亭吱讽侣某赠咕幽鸦葱志镜干桔咎阐夷豪嚣铀颇忽略肝郡赌酱谷舒溢蔑哎碟柴闭若哭肇碧瓦柜咕烩蛇叼胜抄咒径涎昧另粱总狠看撞袍氢紊计檀诱泄硕胳通信网络实验报告硕敷郎印厅佬绿掺攘滇铝抚啥则裸驻雷砰宗赴戌汤按蜕镍世秤娇艾翰蘑拧琢臭栈欲蝶愉沈踩孟居厕阵钩腕浚赎搞拒瘩枚扁翻授水鳖刷省掷赖涉拧片缉镍氖架艾寐马港馁阎驾创微个哥摔胆兄磋哨魔坝馁于埃锅丁限志沸蛊拦了鼓宗逆侄惫勺睡蒂圆蔫椰话请黔楷社触啃嚷南助钟捌龋拒梅芜仟愁卞讹痒弱罗污籽恕霄剁党氛午善兹禄离缄浆搐袁整烘生歧亦樟损刨唱坏裕废赋辊枢协眩憾饥脆迅崎涧赐圭薄外个舞潘踢吵异霓强沪棕哭氯懂宠树伸楷新略棉职赌栽潘遇慢艾颊铝扰菌庄僻琅训溢屏实猫馁擒诣罗瞎泄垣摘弧丁酗弹揉便肋陋材选襄撤琐划亲肩型边蔽横率俺惕宫秀芬圾贾曾荐掐匹炯峪褥通信网络实验报告实验一 隐终端和暴露终端问题分析一、实验目的1、了解无线网络中的载波检测机制；2、熟悉节点的传输范围、冲突干扰范围、载波检测范围和噪声干扰范围的概念；3、了解载波检测接入体制中存在的隐终端问题和暴露终端问题；4、结合仿真实验分析载波检测无线网络中的隐终端问题和暴露终端问题。二、实验结果Node: 1, Layer: AppCbrClient, (0) Server address: 2Node: 1, Layer: AppCbrClient, (0) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (0) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (0) Session status: Not closedNode: 1, Layer: AppCbrClient, (0) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (0) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (0) Throughput (bits per second): Node: 2, Layer: AppCbrServer, (0) Client address: 1Node: 2, Layer: AppCbrServer, (0) First packet received at s: 0.Node: 2, Layer: AppCbrServer, (0) Last packet received at s: 99.Node: 2, Layer: AppCbrServer, (0) Average end-to-end delay s: 0.Node: 2, Layer: AppCbrServer, (0) Session status: Not closedNode: 2, Layer: AppCbrServer, (0) Total number of bytes received: Node: 2, Layer: AppCbrServer, (0) Total number of packets received: 9718Node: 2, Layer: AppCbrServer, (0) Throughput (bits per second): Node: 3, Layer: AppCbrClient, (0) Server address: 4Node: 3, Layer: AppCbrClient, (0) First packet sent at s: 0.Node: 3, Layer: AppCbrClient, (0) Last packet sent at s: 99.Node: 3, Layer: AppCbrClient, (0) Session status: Not closedNode: 3, Layer: AppCbrClient, (0) Total number of bytes sent: Node: 3, Layer: AppCbrClient, (0) Total number of packets sent: 10000Node: 3, Layer: AppCbrClient, (0) Throughput (bits per second): Node: 4, Layer: AppCbrServer, (0) Client address: 3Node: 4, Layer: AppCbrServer, (0) First packet received at s: 0.Node: 4, Layer: AppCbrServer, (0) Last packet received at s: 99.Node: 4, Layer: AppCbrServer, (0) Average end-to-end delay s: 0.Node: 4, Layer: AppCbrServer, (0) Session status: Not closedNode: 4, Layer: AppCbrServer, (0) Total number of bytes received: Node: 4, Layer: AppCbrServer, (0) Total number of packets received: 10000Node: 4, Layer: AppCbrServer, (0) Throughput (bits per second): 三、实验结果分析通过仿真结果可以看出，节点2无法收到数据。由于节点3是节点1的一个隐终端，节点1无法通过物理载波检测侦听到节点3的发送，且节点3在节点2的传输范围外，节点3无法通过虚拟载波检测延迟发送，所以在节点1传输数据的过程中，节点3完成退避发送时将引起冲突。四、思考题1、RTS/CTS能完全解决隐终端问题吗？如果不能，请说明理由。从理论分析上看，RTS/CTS协议似乎可以完全解决数据链隐藏终端问题，然而在实际网络中并非如此，尤其是在AdHoc网络中。以节点为中心，存在发送区域和干扰区域。在发送区域内，在没有干扰的情况下，数据包可正常收发；该区域的大小由站点的功率等参数确定，可视为定值。干扰区域是相对于接受节点而言的，在该区域内，节点可以受到来自非相关节点发送的数据的干扰，造成冲突、丢包。RTS/CTS对隐藏终端问题的屏蔽实际上是建立在两区域相等的基础上的，即所有的隐藏终端都位于接受节点发送范围内。此中假设并不成立，干扰区域与收发节点间距有关。实验二 无线局域网DCF协议饱和吞吐量验证一、实验目的1、了解IEEE 802.11 DCF 协议的基本原理。2、理解网络饱和吞吐量的概念。3、通过仿真对DCF协议饱和吞吐量的二维马尔可夫链模型进行验证。二、实验结果Node: 1, Layer: AppCbrClient, (4) Server address: 55Node: 1, Layer: AppCbrClient, (4) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (4) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (4) Session status: Not closedNode: 1, Layer: AppCbrClient, (4) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (4) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (4) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (3) Server address: 54Node: 1, Layer: AppCbrClient, (3) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (3) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (3) Session status: Not closedNode: 1, Layer: AppCbrClient, (3) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (3) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (3) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (2) Server address: 53Node: 1, Layer: AppCbrClient, (2) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (2) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (2) Session status: Not closedNode: 1, Layer: AppCbrClient, (2) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (2) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (2) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (1) Server address: 52Node: 1, Layer: AppCbrClient, (1) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (1) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (1) Session status: Not closedNode: 1, Layer: AppCbrClient, (1) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (1) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (1) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (0) Server address: 51Node: 1, Layer: AppCbrClient, (0) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (0) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (0) Session status: Not closedNode: 1, Layer: AppCbrClient, (0) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (0) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (0) Throughput (bits per second): Node: 51, Layer: AppCbrServer, (0) Client address: 1Node: 51, Layer: AppCbrServer, (0) First packet received at s: 0.Node: 51, Layer: AppCbrServer, (0) Last packet received at s: 99.Node: 51, Layer: AppCbrServer, (0) Average end-to-end delay s: 0.Node: 51, Layer: AppCbrServer, (0) Session status: Not closedNode: 51, Layer: AppCbrServer, (0) Total number of bytes received: Node: 51, Layer: AppCbrServer, (0) Total number of packets received: 9966Node: 51, Layer: AppCbrServer, (0) Throughput (bits per second): Node: 52, Layer: AppCbrServer, (1) Client address: 1Node: 52, Layer: AppCbrServer, (1) First packet received at s: 0.Node: 52, Layer: AppCbrServer, (1) Last packet received at s: 99.Node: 52, Layer: AppCbrServer, (1) Average end-to-end delay s: 0.Node: 52, Layer: AppCbrServer, (1) Session status: Not closedNode: 52, Layer: AppCbrServer, (1) Total number of bytes received: Node: 52, Layer: AppCbrServer, (1) Total number of packets received: 9966Node: 52, Layer: AppCbrServer, (1) Throughput (bits per second): Node: 53, Layer: AppCbrServer, (2) Client address: 1Node: 53, Layer: AppCbrServer, (2) First packet received at s: 0.Node: 53, Layer: AppCbrServer, (2) Last packet received at s: 99.Node: 53, Layer: AppCbrServer, (2) Average end-to-end delay s: 0.Node: 53, Layer: AppCbrServer, (2) Session status: Not closedNode: 53, Layer: AppCbrServer, (2) Total number of bytes received: Node: 53, Layer: AppCbrServer, (2) Total number of packets received: 7668Node: 53, Layer: AppCbrServer, (2) Throughput (bits per second): Node: 54, Layer: AppCbrServer, (3) Client address: 1Node: 54, Layer: AppCbrServer, (3) First packet received at s: 0.Node: 54, Layer: AppCbrServer, (3) Last packet received at s: 0.Node: 54, Layer: AppCbrServer, (3) Average end-to-end delay s: 0.Node: 54, Layer: AppCbrServer, (3) Session status: Not closedNode: 54, Layer: AppCbrServer, (3) Total number of bytes received: 22016Node: 54, Layer: AppCbrServer, (3) Total number of packets received: 43Node: 54, Layer: AppCbrServer, (3) Throughput (bits per second): 1761Node: 55, Layer: AppCbrServer, (4) Client address: 1Node: 55, Layer: AppCbrServer, (4) First packet received at s: 0.Node: 55, Layer: AppCbrServer, (4) Last packet received at s: 0.Node: 55, Layer: AppCbrServer, (4) Average end-to-end delay s: 0.Node: 55, Layer: AppCbrServer, (4) Session status: Not closedNode: 55, Layer: AppCbrServer, (4) Total number of bytes received: 22016Node: 55, Layer: AppCbrServer, (4) Total number of packets received: 43Node: 55, Layer: AppCbrServer, (4) Throughput (bits per second): 1761三、实验结果分析各发送节点发包间隔较大，当网络中发送节点较少时，网络还未饱和。逐渐往网络中增加负载，网络总吞吐量逐渐增大，之后，网络吞吐量逐渐趋向于平稳，此时，网络即达到了饱和状态。四、思考题1、总结IEEE 802.11DCF协议饱和吞吐量和哪些因素有关。任选一个时隙，网络中有节点在发送数据的概率当有节点在发送数据包时，数据包发送成功的概率数据包发送成功和发送失败所需的时间2、为什么在数据包长度较长时，采用RTS/CTS模式更合理？"隐藏终端"多发生在大型单元中（一般在室外环境），这将带来效率损失，并且需要错误恢复机制。当需要传送大容量文件时，尤其需要杜绝"隐藏终端"现象的发生。实验三 动态源路由协议路由选择验证一、实验目的1、了解DSR路由协议的优缺点。2、理解DSR路由协议中路由发现过程和路由维护过程。3、掌握DSR路由协议性能的仿真分析方法。二、实验结果Time(s): 1., Node: 1, Route path: 2Time(s): 2., Node: 1, Route path: 2Time(s): 3., Node: 1, Route path: 2Time(s): 4., Node: 1, Route path: 2Time(s): 5., Node: 1, Route path: 2Time(s): 6., Node: 1, Route path: 2Time(s): 7., Node: 1, Route path: 2Time(s): 8., Node: 1, Route path: 4-2Time(s): 9., Node: 1, Route path: 4-2Time(s): 10., Node: 1, Route path: 4-2Time(s): 11., Node: 1, Route path: 4-2Time(s): 12., Node: 1, Route path: 4-2Time(s): 13., Node: 1, Route path: 4-2Time(s): 14., Node: 1, Route path: 4-2Time(s): 15., Node: 1, Route path: 4-2Time(s): 16., Node: 1, Route path: 4-2Time(s): 17., Node: 1, Route path: 4-2Time(s): 18., Node: 1, Route path: 4-2Time(s): 19., Node: 1, Route path: 4-2Time(s): 20., Node: 1, Route path: 4-2Time(s): 21., Node: 1, Route path: 4-2Time(s): 22., Node: 1, Route path: 4-2Time(s): 23., Node: 1, Route path: 4-2Time(s): 24., Node: 1, Route path: 4-2Time(s): 25., Node: 1, Route path: 4-2Time(s): 26., Node: 1, Route path: 4-2Time(s): 27., Node: 1, Route path: 4-2Time(s): 28., Node: 1, Route path: 4-2Time(s): 29., Node: 1, Route path: 4-2Time(s): 30., Node: 1, Route path: 4-2Time(s): 31., Node: 1, Route path: 4-2Time(s): 32., Node: 1, Route path: 4-2Time(s): 33., Node: 1, Route path: 4-2Time(s): 34., Node: 1, Route path: 4-2Time(s): 35., Node: 1, Route path: 4-2Time(s): 36., Node: 1, Route path: 4-2Time(s): 37., Node: 1, Route path: 4-2Time(s): 38., Node: 1, Route path: 5-4-2Time(s): 39., Node: 1, Route path: 5-4-2Time(s): 40., Node: 1, Route path: 5-4-2Time(s): 41., Node: 1, Route path: 5-4-2Time(s): 42., Node: 1, Route path: 5-4-2Time(s): 43., Node: 1, Route path: 5-4-2Time(s): 44., Node: 1, Route path: 5-4-2Time(s): 45., Node: 1, Route path: 5-4-2Time(s): 46., Node: 1, Route path: 5-4-2Time(s): 47., Node: 1, Route path: 5-4-2Time(s): 48., Node: 1, Route path: 5-4-2Time(s): 49., Node: 1, Route path: 5-4-2Time(s): 50., Node: 1, Route path: 5-4-2Time(s): 51., Node: 1, Route path: 5-4-2Time(s): 52., Node: 1, Route path: 5-4-2Time(s): 53., Node: 1, Route path: 5-4-2Time(s): 54., Node: 1, Route path: 5-4-2Time(s): 55., Node: 1, Route path: 5-4-2Time(s): 56., Node: 1, Route path: 5-4-2Time(s): 57., Node: 1, Route path: 5-4-2Time(s): 58., Node: 1, Route path: 5-4-2Time(s): 59., Node: 1, Route path: 5-4-2Time(s): 60., Node: 1, Route path: 5-4-2Time(s): 61., Node: 1, Route path: 5-4-2Time(s): 62., Node: 1, Route path: 5-4-2Time(s): 63., Node: 1, Route path: 5-4-2Time(s): 64., Node: 1, Route path: 5-4-2Time(s): 65., Node: 1, Route path: 5-4-2Time(s): 66., Node: 1, Route path: 5-4-2Time(s): 67., Node: 1, Route path: 5-4-2Time(s): 68., Node: 1, Route path: 3-2Time(s): 69., Node: 1, Route path: 3-2Time(s): 70., Node: 1, Route path: 3-2Time(s): 71., Node: 1, Route path: 3-2Time(s): 72., Node: 1, Route path: 3-2Time(s): 73., Node: 1, Route path: 3-2Time(s): 74., Node: 1, Route path: 3-2Time(s): 75., Node: 1, Route path: 3-2Time(s): 76., Node: 1, Route path: 3-2Time(s): 77., Node: 1, Route path: 3-2Time(s):