静脉-INET兼容性 [英] Veins - INET compatibility

查看:102
本文介绍了静脉-INET兼容性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我目前正在寻找802.11p仿真的可行性,并且除了WAVE/IEE 802.11p之外,我还想测试IPv6. INET将是解决方案,但我怀疑与Veins 4 alpha 2(最新版本)的兼容性.

I’m currently searching for 802.11p simulation feasability and I would like to test IPv6 as well, apart from the WAVE/IEE 802.11p. The INET would be the solution but I’m doubting about the compatibility with the Veins 4 alpha 2 (latest version).

我所知道的是Veins 3.X是基于MiXiM的,但是同时INET和MiXiM可以兼容并一起安装在OmNET中,甚至可以将它们组合在一起,甚至可以与MixNET一起安装.

What I know is that Veins 3.X was based on MiXiM, but at the same time INET and MiXiM can be compatible and installed together in OmNET, combining them or even with MixNET.

我真的很想知道是否有人实现了他们一起工作(OmNET + Veins + INET或MiXiM + INET).

I would really like to know if somebody has achieved them work al together (OmNET + Veins + INET o MiXiM+INET).

谢谢.

推荐答案

答案取决于您运行的静脉版本:

The answer depends on which version of Veins you run:

最新版本的静脉可以与INET 3.4.0一起使用.该过程的详细信息如下: https://stackoverflow.com/a/41833646/4707703

Later versions of Veins can be used together with INET 3.4.0. The process is detailed here: https://stackoverflow.com/a/41833646/4707703

静脉4a2可以与INET框架版本2.3.0中的模块一起使用.为此,您需要运行./configure --with-inet=PATH(如果从命令行构建Veins)或选择相应的"With INET Framework"项目功能(如果从IDE构建Veins). 请注意,静脉中还没有包含一个模块,该模块可以将对网络层进行建模的INET模块连接至对MAC层进行建模的Veins模块.这需要您写. 不过,为了进行快速测试,您可以将INET模块添加到Scenario(您可能需要ChannelControlIPv4NetworkConfigurator)和汽车中(您可能希望Car扩展AdhocHost). 这样一来,您就可以在汽车上实例化INET中的INET应用程序,例如通过配置

Veins 4a2 can be used together with modules from the INET framework version 2.3.0. To allow this, you will need to either run ./configure --with-inet=PATH (if you build Veins from the command line) or select the corresponding "With INET Framework" project feature (if you build Veins from the IDE). Note that there is not (yet) a module included in Veins that can connect the INET module modeling the network layer to a Veins module modeling the MAC layer. This will need to be written by you. Still, for a quick test, you can then add INET modules to your Scenario (you probably want ChannelControl and IPv4NetworkConfigurator) and to your cars (you will probably want your Car to extend AdhocHost). This will let you instantiate INET applications on your cars as common in INET, e.g., by configuring

**.nodeCount = 2

**.constraintAreaMinX = 0m
**.constraintAreaMinY = 0m
**.constraintAreaMinZ = 0m
**.constraintAreaMaxX = 2500m
**.constraintAreaMaxY = 2500m
**.constraintAreaMaxZ = 50m

**.node[*].udpApp[*].sendInterval = uniform(250ms, 750ms)
**.node[*].udpApp[0].startTime = 0ms
**.node[*].wlan[0].**.bitrate = 11Mbps
**.node[*].wlan[0].**.globalARP = true

**.node[*].numUdpApps = 1
**.node[*].udpApp[0].typename = "UDPBasicApp"
**.node[*].udpApp[0].destAddresses = "224.0.0.1"
**.node[*].udpApp[0].localPort = 1
**.node[*].udpApp[0].destPort = 1
**.node[*].udpApp[0].messageLength = 100B
**.node[*].udpApp[0].joinLocalMulticastGroups = true

这篇关于静脉-INET兼容性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆