It certainly works that way...
Anyway, an user might want to be able to use different sscop
encapsulaed protocols (UNI, QAAL2, ILMI, SSCF-NNI, etc ) on different
USER_DLTs without having to change the preferences each time...
packet-k12.c has (IMHO ugly) code for that (e.g. "sscop:ssf-nni"), it
might be worth moving it into packet-sscop.[ch] and use that for
USER_DLTs as well.
\Lego
On Fri, Aug 29, 2008 at 5:46 PM, Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> wrote:
>
>
> David Bryant wrote:
>> In Wireshark release 99.5, under the Edit/Preferences menu, within the
>> Protocols/"DLT User A" window, the user has the capability to select
>> SSCOP as a special encapsulation and MTP3 as the payload type. In
>> release 99.7 and 1.0.2, the Protocols/DLT_User window is set up
>> differently. MTP3 can be entered as the payload type within the DLT
>> user encapsulation table, however, the SSCOP special encapsulation
>> cannot. I attempted entering SSCOP as a trailer protocol, as well as
>> other combinations of SSCOP and MTP3 for payload, header and trailer,
>> and I could not get Wireshark 99.7 or 1.0.2 to bust out the protocols
>> the same as 99.5. The later versions produce a much larger number of
>> decode errors and unknowns on the same capture files with my (erroneous)
>> DLT user table settings. What is the correlary to the MTP3 with SSCOP
>> Special Encapsulation setting in the later versions of Wireshark?
>
> Does it work to set SSCOP as the "protocol" in DLT_User and then, in the
> SSCOP preferences, choose its payload type as SSCF-NNI(MTP3-b)?
> _______________________________________________
> Wireshark-users mailing list
> Wireshark-users@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-users
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
