TREP3 Daemonless: understanding RRCP multicast addresses

nicolas.roux · 2018-12-17T10:08:15+00:00

The ADH v3.2 manual seems to be contradictory: * Section 8.2 and 8.5 state that auxiliary transports are send only. * But the configuration example section 8.7 shows this tranports send and receive addresses. * There are further inconsistences between section 8.7 and the specific example in section 8.9. Could you explain…

nicolas.roux

The ADH v3.2 manual seems to be contradictory:

Section 8.2 and 8.5 state that auxiliary transports are send only.
But the configuration example section 8.7 shows this tranports send and receive addresses.
There are further inconsistences between section 8.7 and the specific example in section 8.9.

Could you explain this contradiction? Am I missing something?

Find more posts tagged with

trep

infrastructure

elektron

multicast

rrcp

refinitiv-realtime

Accepted answers

mahesh.bommanayakanahalli

You need to configure both a send and a receive multicast group for these
auxiliary transports to allow for bi-directional protocol messages. TREP 3.3.0 document will be updated to reflect this.

All comments

mahesh.bommanayakanahalli

You need to configure both a send and a receive multicast group for these
auxiliary transports to allow for bi-directional protocol messages. TREP 3.3.0 document will be updated to reflect this.

Quick Links

All Forums
Recent Questions

EXPLORE OUR SITES