I stumbled upon the sequence number having a type of unsigned int. According to this unsigned int is at least 2 byte, whereas the sequence number field is of size 4 bytes. I run my simulation with a packet of size >2^16 and it worked. Maybe this is due to my 64 bit system where an unsigned int is 4 byte. I can't test right now if the simulation still works on a 32 bit system - so I'd like to ask if it still does or if if this has to be corrected. Thanks!
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
Just read one more sentence on the page you linked:
"However, on 32/64 bit systems it is almost exclusively guaranteed to have width of at least 32 bits (see below)."
In practice, an int, signed or unsigned, will be 32 bits wide on (almost) any system OMNeT++ runs on. So this should be among the last things you need to worry/think about.
Attila
2017-08-14 0:04 GMT+02:00 baukran <jensmue...@gmail.com>:
I stumbled upon the sequence number having a type of unsigned int. According to this unsigned int is at least 2 byte, whereas the sequence number field is of size 4 bytes. I run my simulation with a packet of size >2^16 and it worked. Maybe this is due to my 64 bit system where an unsigned int is 4 byte. I can't test right now if the simulation still works on a 32 bit system - so I'd like to ask if it still does or if if this has to be corrected. Thanks!
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.