cd2orb - receive alpha (cd1) packets and copy to an orbserver
cd2orb [-c maxctime]
[-d database]
[-i ip]
[-P cmport[,cd1port]]
[-p pf]
[-S state]
[-vv] [orb]
cd2orb listens for incoming alpha(cd1) connections, and sets up
a receiver when one is found. The incoming packets may be
repackaged into an orb packet and left on an orb. If a versignd(1)
daemon is available with the correct public keys, the packets
may be verified. cd2orb plays the part of both the connection
manager and the ultimate receiver of the data.
-
-c maxctime
Maximum time to allow between connection manager request and subsequent
connection from a remote site. During this period, cd2orb does not allow
other connections. The default is 120 seconds.
-
-d database
If specified, attempt to look up calib, calper and segtype from the calibration
table of this database, to fill into the cd1s packets generated by cd2orb.
-
-i ip
Specify a different ip address for the cd2orb connection manager to provide in the
response to a connection request. This can be useful behind a firewall, where
the local ip address may be different than the externally visible address.
-
-P cmport[,cd1port]
The default port for initiating alpha connections (cmport) is 8000. cd2orb
sets up a connection manager listening at this port.
When a new connection is attempted, a message is returned specifying the
current host (but see the -i option above) and a new port number.
The default for this new port (cd1port) is 9876.
-
-p pf
Specify an alternative parameter file, rather than cd2orb.pf.
-
-S state
save state information in this file, to mark
delayed/out of order packets. The cd1 protocol allows large
numbers of out of order (reverse order) delayed packets, interspersed
with current data. orb2db(1) tends to create many wfdisc records in
this situation. The problem is partly allayed by marking delayed
packets, which are handled differently by orb2db (or can be filtered
out using the match and reject orb parameters).
Delayed packets are marked using standard practice,
with a suffix "/@". If no state file is specified, no marking is done.
-
-v
Be more verbose.
-
-vv
Be extremely verbose.
-
orb
If an output is specified, the incoming cd1 stream is copied to the
orbserver(1).
-
valid_ip_addresses
accept connections only from ip addresses in this list.
-
acceptable_site_codes
accept connections only from sites with connection codes in this array.
An entry of '*' in this array allows all connections.
-
verify_packets
flag indicating if an attempt should be made to verify the packets
-
versign_server
name of server for versign daemon; leave blank to use a local versignd
-
data_packet_signer
user name to use for signature verification;
if not specified, the signer is formed from the cd1 connection code.
-
net_sta_chan
-
net
-
sta
-
chan
These provide a means of remapping the network, station and
channel codes from the incoming connections. Initially, the
network code is taken from the name used to initiate the connection.
The station and channel codes come from the dff headers.
These four lists are each composed of original patterns (regular expressions)
and replacements.
cd2orb first composes a string made of network, station and channel
separated by underscores, and attempts to match this in the net_sta_chan list.
If a match is found, then the result is separated into new network, station and
channel using underscores as delimiters, and these names replace the original.
If no match is found, then network, station and channel are individually
matched with the corresponding list, and any replacement found there is used.
-
status
Some cd1 networks provide some additional information in the header of
a cd1 data packet. This information is placed into a separate string packet.
The default is to name the packet using the site code from connection request,
followed by "/ch".
The status list allows replacing the site code with something arbitrary.
-
verbose
adjust level of verbosity by site code (station); the value may be 0
(the default), 1 or 2 for increasing verbosity. When no value exists for
a site code, the verbosity for that site (thread) is 0.
-
packet_save_directory
raw packets may be saved into subdirectories of this directory
-
save_packets
save raw packets from certain sites, specified in this array.
To replace a channel code of "be" with "BHE", specify the chan list in the
parameter file as:
chan &Tbl{
be BHZ
}
To completely rename "net" (actually site code), sta and chan, use the
net_sta_chan list. You can add a loc code at this point, if you desire.
net_sta_chan &Tbl{
brtt_KONO_bz DQ_KONA_KAFFE_01
}
cd1tran(1)
orb2cd1s(1)
cd1s2cd1(1)
The option to save raw incoming data packets is
for debugging only, and is pretty
crude. All data for a single site and session are saved into
the same file.
Daniel Quinlan
Table of Contents
Antelope Release 4.8 Darwin 8.6.0 2006-06-28
Boulder Real Time Technologies, Inc
For more information, contact support@brtt.com