|Connectivity Troubleshooting||Table of Content||Conformance Testing|
|Multicast Tunnel Proxy|
For test environment, the multicast tunnel proxy can be used to receive multicast messages through a TCP tunnel.
Multicast tunnel proxy utility is available as part of "ICE iMpact Multicast Price Feed Getting Started" package which can be obtained from by contacting ICE support (firstname.lastname@example.org).
The tunnel proxy establishes a socket connection to the feed server, receives the messages and multicasts them on the local network based on the multicast group mapping rules from TunnelProxy.properties file.
Once the tunnel proxy is launched, multicast client can join the local multicast channels that the tunnel is currently multicasting. This provides a seamless operation from the clients' perspective. The diagram below illustrates the connectivity:
The tunnel TCP server address is 18.104.22.168. But the tunnel port could be different depending on the multicast groups. You can find the port numbers under connection info for API Test env in "ICE iMpact Multicast Feed Technical Specification".
Configuration parameter tunnel.multicast.interface in the TunnelProxy.properties file could be used.
# # In case you want to multicast on a specific interface, or if your local network doesn't support # multicast, you can uncomment the following property. This property sets the multicast interface # to 127.0.0.1 # tunnel.multicast.interface=127.0.0.1
|The value 127.0.0.1 works perfectly in most cases.|