[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-users
Subject: Re: [Wireshark-users] LUA dissector - combine data from 2 UDP packets, display issue
From: Michael Poroger <bezenchu () gmail ! com>
Date: 2020-07-31 16:01:54
Message-ID: CACo=suSGYumO89MrRRtpD-a=wQvDoKAQwTR=KxxAgLaxp_OLPQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Something I build by myself. The idea is similar to this
<https://osqa-ask.wireshark.org/questions/55621/lua-udp-reassembly>
implementation (in the answer) - just storing the data between packet X-1
to packet X.
Not sure about the actual implementation (as already on weekend), but I
think that this is not persistent storage, as if the data in the packet is
complete, the storage is set to an empty one. In any case, if packet X-1
does not contain complete data, this data is available for packet X.
-----------------------------
Michael Poroger
"Science is not only knowledge, science is also to be dare"
Shimon Peres
On Fri, Jul 31, 2020 at 5:27 PM Jeff Morriss <jeff.morriss.ws@gmail.com>
wrote:
>
>
> On Fri, Jul 31, 2020 at 8:58 AM Michael Poroger <bezenchu@gmail.com>
> wrote:
>
>> Hello users :)
>>
>> I've successfully created a dissector which combines data from 2 UDP
>> packets. Every time I select this kind of packet, I'm getting an error on
>> the packet details on the custom protocol section.
>>
>> Only when I select the previous packet and then the current packet, I can
>> see the dissection as I expect and without any error.
>>
>> How to solve the issue?
>>
> Probably a question better for the -dev list but...
>
> Are you using epan's reassembly routines or something you built yourself?
> If it's something you built yourself, are you storing the reassembled data
> in persistent storage which is available when (re)dissecting the 2nd frame
> (where the reassembled data is used)?
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@wireshark.org
> ?subject=unsubscribe
[Attachment #5 (text/html)]
<div dir="ltr"><div>Something I build by myself. The idea is similar to <a \
href="https://osqa-ask.wireshark.org/questions/55621/lua-udp-reassembly">this</a> \
implementation (in the answer) - just storing the data between packet X-1 to packet \
X.<br></div><div><br></div><div>Not sure about the actual implementation (as already \
on weekend), but I think that this is not persistent storage, as if the data in the \
packet is complete, the storage is set to an empty one. In any case, if packet X-1 \
does not contain complete data, this data is available for packet \
X.</div><div><br></div><div><div><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div \
dir="ltr">-----------------------------<br>Michael Poroger<br><br><font \
color="000000"><font color="00CCFF"><span lang="en"><font \
color="3366FF"><span>"Science is not only knowledge, science is also to be \
dare</span><span>"<br>Shimon \
Peres</span></font></span></font></font><br><br></div></div></div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 31, 2020 at 5:27 PM \
Jeff Morriss <<a href="mailto:jeff.morriss.ws@gmail.com">jeff.morriss.ws@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On \
Fri, Jul 31, 2020 at 8:58 AM Michael Poroger <<a href="mailto:bezenchu@gmail.com" \
target="_blank">bezenchu@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"> <p>Hello users \
:)<br></p><p>I've successfully created a dissector which combines data from 2 UDP \
packets. Every time I select this kind of packet, I'm getting an error on the \
packet details on the custom protocol section.</p> <p>Only when I select the previous \
packet and then the current packet, I can see the dissection as I expect and without \
any error.</p> <p>How to solve the issue?</p></div></blockquote><div>Probably a \
question better for the -dev list but...</div><div><br></div><div>Are you using \
epan's reassembly routines or something you built yourself? If it's \
something you built yourself, are you storing the reassembled data in persistent \
storage which is available when (re)dissecting the 2nd frame (where the reassembled \
data is used)?<br></div></div></div> \
___________________________________________________________________________<br> Sent \
via: Wireshark-users mailing list <<a \
href="mailto:wireshark-users@wireshark.org" \
target="_blank">wireshark-users@wireshark.org</a>><br>
Archives: <a href="https://www.wireshark.org/lists/wireshark-users" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-users</a><br>
Unsubscribe: <a href="https://www.wireshark.org/mailman/options/wireshark-users" \
rel="noreferrer" target="_blank">https://www.wireshark.org/mailman/options/wireshark-users</a><br>
mailto:<a href="mailto:wireshark-users-request@wireshark.org" \
target="_blank">wireshark-users-request@wireshark.org</a>?subject=unsubscribe</blockquote></div>
[Attachment #6 (text/plain)]
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic