Checksum Error might causing routing error

79 views
Skip to first unread message

Konstantinos

unread,
May 6, 2011, 2:05:03 PM5/6/11
to ns-3-...@googlegroups.com
I'm testing different routing protocols for ad-hoc networks.
I have developed my own and while I was testing it, I found with the help of wireshark that all UDP packets have BAD CHECKSUM.
This is not only caused in my protocol but also in OLSR. For data and routing packets.

Header checksum: 0x0000 [incorrect, should be 0x6384] (it is always zero)

Is this something that you have encountered before?


In addition, I'm faced with another problem with my protocol.
In a 5x5 grid network with source and dest. at the two corners of the rectangle, packets are forwarded only until the node in the middle where they are 'jammed' and finally dropped because TTL goes to zero. Could this incorrect checksum cause such a strange behaviour ?

Regards,
Konstantinos

Lalith Suresh

unread,
May 6, 2011, 4:35:28 PM5/6/11
to ns-3-...@googlegroups.com
Hello,

On Fri, May 6, 2011 at 7:05 PM, Konstantinos <dinos.k...@gmail.com> wrote:
I'm testing different routing protocols for ad-hoc networks.
I have developed my own and while I was testing it, I found with the help of wireshark that all UDP packets have BAD CHECKSUM.
This is not only caused in my protocol but also in OLSR. For data and routing packets.

Header checksum: 0x0000 [incorrect, should be 0x6384] (it is always zero)

Is this something that you have encountered before?


Checksum calculations are disabled by default for performance reasons. You may enable it if you really need it by setting g_checksumEnabled = true in your simulation script.
 

In addition, I'm faced with another problem with my protocol.
In a 5x5 grid network with source and dest. at the two corners of the rectangle, packets are forwarded only until the node in the middle where they are 'jammed' and finally dropped because TTL goes to zero. Could this incorrect checksum cause such a strange behaviour ?


The checksum calculation being disabled can't be related to this. Try debugging further. :)
 
Regards,
Konstantinos

--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To post to this group, send email to ns-3-...@googlegroups.com.
To unsubscribe from this group, send email to ns-3-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ns-3-users?hl=en.



--
Lalith Suresh
Department of Computer Science and Engineering
Instituto Superior Técnico
www.lalith.in

Reply all
Reply to author
Forward
0 new messages