aboutsummaryrefslogtreecommitdiffstats
path: root/epan/wslua
diff options
context:
space:
mode:
authorjake <jake@f5534014-38df-0310-8fa8-9805f1628bb7>2009-10-24 11:19:23 +0000
committerjake <jake@f5534014-38df-0310-8fa8-9805f1628bb7>2009-10-24 11:19:23 +0000
commit1af704de9a42e6e2a81dcc15f89cb0c150871f18 (patch)
treebe527b8d8ab6347a89229a0cb5ed0a43e16a283c /epan/wslua
parentc3c11493bd46b249625bc22ada8aba45cfc2794e (diff)
From Mithun Roy:
The primary header in bundle protocol contains some offset values(destination scheme offset, destination ssp offset, source scheme offset, source ssp offset, etc). These are the offsets within the dictionary if the length of the dictionary length is greater than 0. But if the dictionary length is 0, then these offset refer to node number and service number respectively(according to compressed bundle header encoding). For example if destination scheme offset is 2 and the destination ssp offset is 1, then the destination EID(<node_number>.<service_number>) is 2.1. Currently the dtn dissector will consider these offsets to be actual offsets in the dictionary even if the dictionary length is 0. So the values for the EID's(destination, source, report, custodian) and their schemes are junk values. For example if the destination scheme offset is 2 and the destination ssp offset is 1 and the dictionary length is 0(which means the dictionary is empty), then the destination scheme is 2 bytes after the beginning of the metadata block(field after dictionary) and destination is 1 byte after the beginning of the metadata block. git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@30682 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'epan/wslua')
0 files changed, 0 insertions, 0 deletions