Minicom Advanced Systems CMG-DCM manual Static routes

Page 47

Operator's guide

net.eth.0.broadcast : The broadcast IP address used by the interface. This can often be derived from the IP address by replacing numbers at the end with 255.

net.eth.0.gateway : The IP address of the gateway machine (router) on your network.

net.eth.0.netmask : The network mask to use for the IP interface. A DCM with an IP address in the domain 192.168.1.x would normally use a netmask of 255.255.255.0.

net.eth.0.netaddress : The network address of the DCM. A DCM with an IP address in the domain 192.168.1.x would normally use a network address of 192.168.1.0.

Static routes

In addition to the standard IP routing mechanisms, you can define up to 4 additional static routes from the DCM to other parts of the network. These routes are specified as arguments to the standard Unix route command. For example, if you wanted the DCM to route traffic to and from IP addresses beginning 192.168.0. over the eth0 interface, you would include the line

add -net 192.168.0.0 netmask 255.255.255.0 dev eth0

in the list.

For more information on the route command, please see its Linux manual page.

December 2005

47

Image 47

Contents CMG-DCM Table of Contents December Inside the DCM Introduction CMG-DCM Inside the DCM Network services Serial port servicesSee .4, Connecting to a local network for full details Overview Installing the CMG-DCMPower supply Connecting over a serial link Connecting to a single computer192.168.0.x Connecting over EthernetConnecting over USB Using an internal modemConnecting to a local network Gcfgdbset option-namenew-value Connecting to the Internet Wi-FiSetting up the CMG-DCM Connecting digitizers and external hardwareWeb setup Setting up digitizers Using Scream DCM as a data store UsageGeneral notes Gnblocks port-number Page CMG-DCM DCM as a GCF data source Accessing the DCM command line through gcfout Sensor arrays DCM as a network data hub Communicating with digitizers Configuring digitizers Data storage and retrieval Using miniSEED format Real-time data transmission CD1.0 and CD1.1 Troubleshooting DCM installations Cannot Gcfping the DCMs Scream! server Cannot see the DCMs Web site over Http or HttpsCannot connect to the DCMs Scream! server DCM is not receiving any data streams Can Gcfping the DCMs Scream! server, but no data appearsDCM is receiving streams, but they do not contain any data Use the Serial port configuration → port name Web page, or143032 up 34 min, load average 1.24, 1.32 General Configuration optionsDisk CMG-DCM Serial port configuration CMG-DCM Page Ethernet port Network configurationStatic routes DNS setup Incoming mail setup Outgoing mail setup Remote access Administrators PPP Mgetty Scream Data transferAutoDRM Scream! ClientCD1.0 Http serverHttp client CD1.1 CD1.1 subframe configuration DSS Server configuration Seed Page CMG-DCM Data Viewer ActionsStream list Icon barDigitizer Setup General digitizer settings Digitizer output control CMG-DCM Trigger criteria CMG-DCM Tap # Rate Bandwidth Samples/s Auxiliary Mux channels Sensor mass control Flush flash Disk toolsPartition, and format disk Check disk filesystemRecent Log Entries Disk filesCamera Summary Network configurationData Out Port, Serial Port A, Serial Port B DNS configurationDisk Status Flash StatusTamper lines Software Versions Inside the DCM File systems CMG-DCM Command line tools Configuration Digitizer console access Data flow MonitoringDigitizer status Tamper lines Removing support packages Updating the DCMOver the Internet From the hard diskFirmware Libgconfigdb Data OUT port Appendix a Connector pinoutsAppendix A.1 Modular DCM units Port a and BNetwork connector USB connectorDM/AM module output Appendix A.2 Integrated DCM unitsAppendix B.1 Sensor response codes Appendix B Sensor and digitizer typesDigitizer Appendix B.2 Digitizer type codes