Good stuff.
Please see the CMIP (which uses ROS) FTAM and MMS which are all
implemented ontop of ACSE and which shows how some data is passed from
the PRES layer to the dissector using the SESSION structure.
Since this structure is already used for these things, this is i think
where you would add your extra variable.
As for ROS, CMIP implements it by hand in the conformance file since
we dont have a ROS dissector yet.
Cutnpaste from that file would probably do the trick until we have ROS
in ethereal.
Please also note that ACSE was replaced wholesale with an asn2eth
generated dissector a few weeks ago which also replaced the way you
register a subdissector for use with ACSE.
I dont think i have seen a real SET yet in a real packet, so if you
can donate a capture file and the corresponding ASN1 definition
maybe Tomas can see whatever needs to be added to asn2eth and I can
add the support to packet-ber.c
On 7/11/05, Graeme Lunt <graeme.lunt@xxxxxxxxx> wrote:
> Hi,
>
> I've justed started looking at ethereal with a view to supporting
> X.400 message transfer. This requires support for RTSE, ROS and X.411
> - and then X.420.
>
> I have a basic RTSE dissector which can be called from ACSE using the
> application context (MTSE in this case). As far as I can tell, the
> application context which was used to determine the dissector is not
> passed to the dissector itself. So in this case, the RTSE dissector
> cannot determine how to dispatch the connection data or transfer data.
> A global variable would work but is not very elegant.
> Has this sort of problem been encountered before?
>
> For the time being I plan to "upgrade" my RTSE dissector to a MTSE
> dissector to solve this problem and incorporate those bits of ROS I
> require (Bind/Unbind). Ultimately it would be nice have separate RTSE
> and ROS dissectors (further down the line I would like to add P7
> (X.413) - which can be run over either ROS or RTSE).
> Is anyone else looking at RTSE/ROS support?
>
> I noticed a couple of problems with the asn.1 support:
> a) packet-ber.c doesn't have a "dissect_ber_set" function though
> asn2eth.py generates these calls
> b) asn2eth.py has a "typo" for T61String support.
>
> I have fixes for both problems which I will pass on when they have
> been more thoroughly tested.
>
> Finally, you come across lots of indefinite length encodings in the
> X.400 world. Is there any update on the support for indefinite length
> encoding?
>
> Graeme
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
