Problem with Packet::AddAtEnd and PacketTags

28 views
Skip to first unread message

Vikash B

unread,
Dec 16, 2016, 4:55:45 AM12/16/16
to ns-3-users
Release Version: 3.26

I was wondering why Packet::AddAtEnd is adding the ByteTagList, but not the PacketTagList,
is there any reason/rationale behind this.

I was working on porting the mmwave module available for 3.24 (https://github.com/mmezzavilla/ns3-mmwave) to 3.26 and noticed that, Lte tags were being added as Packet tags in the 3.26 release instead of Byte tags and this was causing some problems for me.
Why was this change done?

What is the rationale behind this, is it the intended behaviour, how is it that PacketTagList is retained when using Packet::AddAtEnd?

Thanks,

Biljana Bojovic

unread,
Dec 16, 2016, 8:05:43 AM12/16/16
to ns-3-...@googlegroups.com
Hi Vikash,

this was because of bug 2308. https://www.nsnam.org/bugzilla/show_bug.cgi?id=2308

The bug is still open, and we are still evaluating what are possible pros and cons of each of possible implementations, until the definitive bug solution becomes available in ns-3.

Please, feel free to comment on the bug issue and explain what issues you face with PacketTag solution and how it affects your work.

If this is blocking you from porting mmwave module to ns-3-dev we should consider to revert this patch.

Thanks,

Biljana



--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+unsubscribe@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages