Table of Contents
The main component which can be configured into the tracker is the connector that dialogs with every node of the FreeCast network. A
HTTP connector implementation is available (the RMI implementation is obsolete now).
The second component is the connection-assistant, see
the section called
“Connection Assistant Service”.
As soon as the FreeCast tracker is started, nodes can be started.
The information about the FreeCast network managed by the tracker are lost if the tracker reboots. The FreeCast network will experience troubles in this case.
The tracker must be accessible for all the nodes that want to participate to the
FreeCast network. The connector configuration must match the network configuration and the
constraints of the computer where the tracker is hosted. If the tracker on which the
connector is listening requests on the listen address 0.0.0.0:1665 (the default value) and if the nodes are on Internet, any
firewall or router between the tracker host and Internet must be configured to let pass
through or forward connections to the connector
port.
![]() |
Track unreachable |
|---|---|
|
If the FreeCast nodes "behind" a firewall, a router or such equipment encounter connection errors, you should verify the network configuration. |
The connection assistant service provided by the FreeCast tracker assists nodes to connect between them through NATs. Every node connected to the same service can request help to connect to another one. The connection assistant service will notify the other node in realtime that a NAT traversal session is starting.
By default the connection asistant service is started on the TCP port 1666. The default node configuration uses a default service available on freecast.org servers. To use your own service, you must make it reachable from Internet (may be with the required forward) and change the node configuration (see the section called “Connection Assistant”).