[ndnSIM] MTU, Payload Size and an Assert Message

Alex Afanasyev alexander.afanasyev at ucla.edu
Tue Feb 24 07:25:43 PST 2015

Hi Christian,

This is intended behavior.  If you need to use larger MTU sizes, you simply need to explicitly set MTU parameter on point to point link.  Without such an explicit setting, ns3 in debug mode is "reminding" you that simulation parameters do not match.


> On Feb 24, 2015, at 4:51 AM, Christian Kreuzberger <christian.kreuzberger at itec.aau.at> wrote:
> In line 80 of ndn-net-device-face.cpp, there is an ASSERT MESSAGE checking whether packet->Getsize() <= m_netDevice->GetMtu().
> https://github.com/named-data/ndnSIM/blob/master/model/ndn-net-device-face.cpp#L80
> The line does make sense, as fragmentation is not (yet) implemented (or is it?). However, this ASSERT Message is only triggered if ndnSIM is compiled in debug mode (e.g., not with –d optimized), hence if you run ndnSIM in debug mode, the simulation will stop if the payload+header+tags is to large. Though if you run it without debug mode, the simulation will continue even with payloads that go beyond the MTU.
> I’m wondering if this behaviour is intended, and I am also wondering what happens to too large payloads – I guess it could cause problems and produce inaccurate results in certain cases.
> Hope to help,
> Christian
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20150224/bdcac7d7/attachment.html>

More information about the ndnSIM mailing list