Configure the route table, Routing in a vipersat network, Configure the route table -7 – Comtech EF Data CDD-56X Series Vipersat User Manual
Page 29: Routing in a vipersat network -7, Figure 2-6 ethernet interface screen
Chapter
2 -
Quick Start Configuration
2-7
MN/22137, rev 1
Initial Configuration
Figure 2-6 Ethernet Interface screen
3. Save the settings to flash by entering S at the command prompt.
Configure the Route Table
Routing in a Vipersat Network
CDD-56X Demodulator Routers operating in Vipersat mode do not use the
small or large network described in the CDD-564L Installation and Operation
Manual. There is no HDLC address in a Vipersat network; instead, the
CDD-56X role designation — Hub or Remote, Expansion unit or not — deter-
mines routing rules that prevent multicast loops. This simplifies the configura-
tion of a Vipersat network.
Because satellite networks are often used as extensions for access to services
such as the Internet or the PSTN, they lend themselves quite readily to private
addressing. For example, to provide Internet access to the satellite network, only
the Hub requires a public IP address in order for the entire satellite network that
is controlled by the Hub to have access to the Internet backbone. Utilizing
Network Address Translation (NAT), the administrator can effectively address
the network using a minimum number of static route statements.
Example:
The IP address 172.16.0.0 is the private address network number for class B
networks. If there is a router at the Hub with a connection to the Internet, the
operator can define the local network as a class B. If the operator splits the Class
B in half and points the upper half toward the satellite there will be over 16000
usable addresses at the Hub as well as at the Remotes. For details on IP address-