-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OMNeT++ 6.0 compatibility #243
Comments
Hi, I would like to support this initiative, I would be very interested in using Artery in parallel with the soon-to-be-released INET 4.4 version which includes a Time-sensitive Networking implementation for Ethernet networks. |
Unfortunatelly OMNeT++ 6.0 compatibility does not imply INET 4.x -- since I am using INET 3.8.x (which is supported by OMNeT++ 6.0). As far as I understand moving to INET 4.x could mean a bigger effort (altough I have not tried it...). But maybe this could be a second step... |
Yes, Artery shall run with OMNeT++ 6.0 in the foreseeable future. For some changes, I have been waiting for the actual OMNeT++ release because I don't want to "support" pre-releases. |
Hi Raphael, just saw the discussion. FYI: We have ported most parts of Artery and Vanetza to INET 4.4 and OMNeT++ 6.0 as part of the CrowNet project, link to Artery fork is: https://github.com/roVer-HM/artery |
Thanks @wischhof for your hint/reminder! I will have a closer look at the forked repository as soon as I can spend some time for migration to OMNeT++ 6.0. |
I wonder if there is some interest / plans regarding OMNeT++ 6.0 compatibility.
I have some patches for making this happen, but I wonder if there is interest.
If yes, what is the minimal OMNeT++ version artery is expected to support?
The text was updated successfully, but these errors were encountered: