Master DIS Gateway File This file is meant to document all features of the DIS Gateway file. There are three main sections to the DIS gateway file: [general] [interfaces] [waveform] The [general] effects all DIS traffic on the box and allows for setting the DIS version. This version is placed in the DIS header of the packet. Typical versions are 4, 5, and 6, default is 4. The command is: [general] version = 6 The DIS timestamp has an option for relative (based on sim time) or absolute (based on UTC). The default timestamp is relative but can be switched to absolute with the following: timestamp = absolute The exercise_edgemap setting is rarely used and can be ignored in most cases. This feature adds the ability to support multiple DIS exercises with the same exercise enumeration, but on different UDP ports.  This feature can be enabled in the DIS gateway thru the command shown below where N is the DIS exercise enumeration that is required on the DIS network. Output Note: Everything maps to exercise N. Input Note: The incoming exercise is ignored as it is assumed that all PDUs on that port are of the required exercise enumeration. exercise_edgemap = N The exercises is rarely used and should be ignored. This parameter specifies that the DIS gateway should process PDUs received on all exercises. If this parameter is not set, then only received PDUs for exercises being used on the local Target will be processed. (This is normally only used for monitoring purposes such as anmon, or when a Telestra must act on all exercises, such as a dedicated SATCOM Server). exercises = all The [interfaces] section sets the DIS networking configuration including port, interface, and IP scheme. The [interfaces] section also allows for flexible control of DIS networking on a per DIS exercise ID basis. Below is a typical example, which sets the DIS version, ethernet interface, UDP Port, and broadcast address for all DIS traffic. [interfaces] main_bcast = 10.2.255.255 port = 53124 if = eth0 Here is an enhanced example, where each PDU type is put their own multicast address: [interfaces] signal_mcast = 224.11.11.11 receiver_mcast = 224.12.13.14 main_mcast = 224.10.10.10 entity_mcast = 224.10.10.220 port = 53124 if = eth0 Separate ports may also be used for transmit and receive. If none are specified the default is 53000: [interfaces] main_bcast = 10.2.255.255 port = 53124 tx_port = 53001 if = eth0 The [interfaces] section may be enhanced to apply different rules on a per DIS exercise basis. The example below applies special rules for the range of exercise IDs from 23 to 35, using a different interface, port, and multicast address. [interfaces:23] end_exercise_range = 35 main_mcast = 224.1.1.31 port = 3334 if = eth2 Each exercise can be given its own set of DIS network configs by using multiple [interfaces:] sections. Multicast groups can also be created based on adding the exercise ID to the last octet. A simple mcast by exercise example: Will use 224.1.1.1 thru .30 [interfaces:1] end_exercise_range = 30 main_xmcast = 224.1.1.0 port = 3334 if = eth0 Will use 224.1.1.31 thru .255 [interfaces:31] end_exercise_range = 255 main_xmcast = 224.1.1.0 port = 3334 if = eth2 Waveform Mappings [waveform:] This section is where you specify the mapping of the comm plan waveform to DIS modulation parameters. You insert one section for each mapping that you want to specify. For example, if your comm plan contained a Waveform file named waveform and in it was a particular waveform named VHF-AM, then you could add the following section to the DIS gateway file: [waveform:waveform.VHF-AM] system=1 spreadspectrum=0 major=1 detail=2   This two-way mapping specifies that any local radios that are configured to use waveform.VHF-AM in their comm plan will generate Transmitter and Receiver PDUs with the above specified DIS modulation parameters. It also says that any remote radios that contain exactly that combination of parameters will be given the mode specified in waveform.VHF-AM (this will usually be AM). Wildcards You can also leave off attributes and the DIS gateway will wildcard the corresponding attribute in the PDU-to-ANPS mapping. For example: [waveform:waveform.VHF-AM-DEFAULT] system=1 spreadspectrum=0 major=1   The detail field is missing and so any PDU that matches this last mapping but does not match a more specific mapping will use this mapping for the conversion to ANPS. The only problem with this mapping is that on an ANPS-to-PDU mapping, there is not a detail field specified and so a value of zero is inserted. PDU-to-ANPS Wildcard and ANPS-to-PDU Specified However, you can specify a wildcard for the PDU-to-ANPS mapping while also specifying a particular value to use on the ANPS-to-PDU mapping. For example: [waveform:waveform.VHF-AM] system=1 spreadspectrum=0 major=1 detail= -2   The negative number used for the detail attribute says that when creating a PDU, set the detail field to 2. However, when mapping from a PDU to an ANPS, the detail field is a wildcard and does not require the value to be 2. This one mapping then does the job of both waveform.VHF-AM and waveform.VHD-AM-DEFAULT. Each waveform also allows the setting of the DIS fields located in the Entity Type Record as well as the Input Source. Most of the fields are a single byte, with the exception of country which is two bytes long. Subcategory is equivalent to the "Nomenclature Version" Specific is equivalent to the upper byte of "Nomenclature Field" Extra is equivalent to the lower byte of "Nomenclature Field" entitykind = 1 domain = 2 country = 3 category = 4 subcategory = 5 specific = 6 extra = 7 inputsource = 8