Skip to content
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

Open
sk13 opened this issue Apr 26, 2022 · 5 comments
Open

OMNeT++ 6.0 compatibility #243

sk13 opened this issue Apr 26, 2022 · 5 comments

Comments

@sk13
Copy link
Contributor

sk13 commented Apr 26, 2022

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?

@MadeInPierre
Copy link

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.
Thanks!

@sk13
Copy link
Contributor Author

sk13 commented Apr 29, 2022

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...

@riebl
Copy link
Owner

riebl commented May 15, 2022

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.
The trouble is just that I have to do these things in my spare time; that's also the reason for my delayed response, sorry.

@wischhof
Copy link

wischhof commented Jun 3, 2022

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
I think, you discussed a previous version with @stefanSchuhbaeck at the last OMNeT++ summit. Since then, we have ported more parts but we only test those parts of Artery which we use within CrowNet. So it is not finished but might be used as a basis. If it is useful for you, I'll send a pull request - did not do it until now, since it is only roughly tested and incomplete.

@riebl
Copy link
Owner

riebl commented Jun 26, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants