LBI-38962
10
USING NON-NETWORK LAYER RDTs
If there are any Radio Data Terminals (RDTs) that do not have the EDACS Network Driver installed, EDACS
addresses become important to the user. Specifically, a Host LID needs to be mapped to each of the IP hosts.
For this example, it is assumed that LID 1 has been assigned to Host A and LID 2 has been assigned to Host B.
Host A
CAP
Host B
Host Network
Internal EDG Network
TSI
EDACS Network
EDG
1.0.15.12
1.0.15.13
1.0.0.0
199.0.0.0
128.1.0.0
Radio/RDI/RDT
128.1.0.64
128.1.64.2
Radio/RDI/RDT
128.1.0.65
128.1.64.1
Radio/RDI/RDT
128.1.0.66
128.1.64.1
1.0.15.14
LID 1
LID 2
The IP host always references IP addresses whether any network layer RDTs are being used or not. The EDG
will convert the IP address of the destination radio to an EDACS address (i.e. LID or GID). Conversely, an RDT
without an EDACS
Network Layer always references an EDACS address. The EDG will convert the EDACS
address of the IP host to an IP address.
will be receiving data calls from a non-Network Layer RDT.
NOTE
An EDACS Host ID must be assigned to any IP host that
Systems may contain a mixture of Network Layer and Non-Network Layer RDTs. The major benefits to using
Network Layer RDTs are that radio-to-radio data communications becomes possible, message sizes greater than
512 bytes may be sent, and the capability to use non-proprietary host computer protocols such as TCP and UDP.
In a more complex configuration, there could be multiple gateways between the EDG and the Hosts. Regardless
of the configuration, the EDG CAP Board's external IP Address must be a valid address on the network that it is
connected to. Routing table entries would be used to allow the EDG and Hosts to communicate.