The RUDP unistim uses is proprietary to Nortel it doesn't match what was
already there. It's strictly a 4 byte sequence number and a 1 byte
(ACK/NAK/Payload) descriptor. While I'm not familiar with the existing
RUDP, if I decode my packets as RUDP they are completely wrong (it
actually looks like a tcp-lite).
My thought process was: Since Nortel's RUDP has no relevance outside the
context of unistim it was best not to confuse the issue with Cisco's
RUDP.
Don Newton
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
Sent: Wednesday, June 20, 2007 1:40 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] [Patch] Unistim dissector plugin [Sample
captures attached]
Hi,
I see that this dissector uses RUDP. We already have an RUDP dissector
in the plugin tree. Does it work the same RUDP flavour as in UNISTIM?
Could we make de RUDP plugin work with a sub dissector table, like UDP?
Thanx,
Jaap
Newton, Don wrote:
> No problem I will either do this evening or tomorrow.
>
> Don Newton
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
> Sent: Tuesday, June 19, 2007 5:01 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] [Patch] Unistim dissector plugin
>
> Hi,
>
> The plugin looks good, now we need some sample captures for a
testdrive
> (fuzztest). Can you whip up a Wiki protocol page and add the sample
> captures?
>
> Thanx,
> Jaap
>
> Newton, Don wrote:
>> I have corrected all deficits that were noted. I also have changed
so
>
>> rudp sequence id shows in info column. Please let me know if there
is
>
>> anything else I am missing.
>>
>> Don Newton
>>
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev