https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2935
--- Comment #17 from David Castleford <david.castleford@xxxxxxxxxxxxxxxxxx> 2008-10-16 02:59:12 PDT ---
(In reply to comment #15)
> Committed (with some changes) as SVN #26464.
>
> The changes made included:
>
> - Rework of proto_reg_handoff and the addition of a simulcrypt_init function to
> address comments about tab_ecm_inter usage in Comment #7 above;
> - Rework some of the proto_tree display code a bit;
> - Remove some additional unneeded variables and #includes;
> - Move proto_register... & proto_reg_handoff... to end of source file
> to match Wireshark convention;
> - Various small cleanups.
>
> A development Windows Wireshark build should be available in a few hours in
> http://www.wireshark.org/download/automated/win32/
>
> Please give it a try and let me know if any issues.
>
I'll have a try this afternoon.
> Thanks again for your contribution ....
>
Thanks for your help Bill, glad to see it's been accepted, good to be able to
contribute, great news.
>
> Some questions/comments:
>
> 1. I note that the IANA port assignment document shows tcp port 8600 as being
> assigned to "asterix". Currently Wireshark doesn't have an asterix dissector
> so there's no immediate conflict. Is tcp port 8600 port usage normal for
> simulcrypt ?
>
Oooops, you're absolutely right, that's legacy in my code, there is no IANA
assigned Simulcrypt tcp port, it has to be configured in the servers and
Simulcrypt specification explicitly mentions the ability to have multiple ECMG
servers on the same IP @, hence can't have single TCP port anyhow. Don't ask me
why we're in 8600 range, it could be anything. Not sure what default
non-assigned port is in wireshark...good catch.
> 2. It would be appreciated if you could add a 'protocol reference' page for the
> simulcrypt protocol to the Wireshark wiki. See any of the protocol reference
> pages shown on http://wiki.wireshark.org/ProtocolReference for the format.
>
ok, I'll have a look, but I also have to submit a new Ismacryp dissector, so
that'll be my priority for now! Need to clean it up a bit first ;-)
> Is there a publicly available specification document for the protocol ?
>
>
Yes, see http://www.dvb.org/technology/standards/index.xml
ETSI TS 101 197 V1.2.1 (02/02) "DVB SimulCrypt; Part 1: Head-end architecture
and synchronization"
available from http://pda.etsi.org/pda/queryform.asp
ETSI TS 103 197 V1.4.1 (09/04) "Head-end lmplementation of SimulCrypt"
available from http://pda.etsi.org/pda/queryform.asp
Updated version TS 103 197 V1.5.1 (03/07) is not yet published by ETSI but is
currently available as DVB Bluebook A045r4
http://www.dvb.org/technology/standards/a045r4.tm2117r6.tm-head0034r3.dTS103197.V1.5.1.pdf
ETSI TR 102 035 V1.1.1 (02/04) "Implementation Guidelines of the DVB Simulcrypt
Standard"
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.