User's Manual

PRELIMINARY FCC ID: BIB61201001 DESCRIPTION 2-6
PRELIMINARY MCC-6120 SDR Packet Data Radio Network
Customer and system requirements. New device drivers have been developed to provide this
same flexibility to the Ethernet and WIFI ports. For example, a laptop, tablet or palm computer
can be set up to run Xtermw.exe connected through one of the Ethernet ports or WIFI (in ad-hoc
mode) to operate as the maintenance terminal. Another example is that a local host computer
can connect through one of the Ethernet ports and route IP packets through the CMU and WIFI
port (in Infrastructure mode) to an Access Point, and on to a WAN-based Central Host System.
TCP/IP
The TCP/IP stack is a shared library that allows the Ethernet and WIFI ports to operate as
traditional IP Network connections with IP-Forwarding (routing). In the MCC-545C, use of
Ethernet connections was provided only by external terminal-server boxes connected to the RS-
232 serial ports. Only ASCII (TELNET) and MSC or MSC2 protocols could be used for
interfacing with external equipment. The MCC-6120 SDR CMU has the Ethernet and WIFI
built-in, and can be directly interfaced to many Ethernet Devices using the standard “Sockets”
software API.
Each Ethernet and WIFI port can be given its own IP address. The initial version of MCC-6120
SDR software allows each port to have from 1 to 4 application “ports”. These are numbered
from 4000 – 4011.
DHCP Client
Either Ethernet port or the WIFI port can have DHCP-Client enabled to automatically get an IP
address from a DHCP server located on its subnet.
DHCP Server
Either Ethernet port or the WIFI port can have DHCP-Server enabled to automatically supply an
IP address to devices located on its subnet. This is a limited implementation and can only supply
IP addresses, not any other configuration data options.
NAT
The Network Address Translation (NAT) protocol can be configured to separate a private subnet
from the public network. As the private hosts send IP packets to the public network, the NAT
routing function translates the private IP addresses into public IP addresses. As packets come
back from the public network, the translation is reversed and the packet delivered to the correct
private IP address. Options exist for assigning static IP addresses, and defining dynamic IP
addresses to be used for the translation.
NAPT
The Network Address Port Translation (NAPT) protocol is similar to NAT, except a range of
port numbers are defined to be used by the router in the address translation. In this way, a single
private and public IP address can be used on each side of the router. The private processes are