Attributes to Configure in the Comm-Port Point

Attribute Description
hostname This attribute should contain a name from the /etc/hosts file. The IP address associated with the given host will be used for the IP multicast.
service name This attribute should contain a name from the /etc/services file. The port number associated with the specified name will be used for the IP multicast.
ttl By default, multicast datagrams are sent only to systems on the local network. If the multicast datagram is intended to be sent to distant networks, and if there is a special multicast router on the local network, the application can increase the scope of the multicast by using the IP_MULTICAST_TTL socket option. Any of the values 0 through 255 can be specified. If ttl is zero, the multicast is limited to the local system. If ttl is one, the multicast is limited to the local network. If ttl is two, the multicast can be forwarded through at most one gateway; and so forth.
uni-multi mode This attribute determines whether we run in unicast (zero) or multicast (one) mode.
debug device UNIX

The device file where debug information is to be printed. The full path must be provided; for example "/dev/ptyqf". In addition to a device file, the following key words are recognized: "stdout" and "stderr"; which send debug information to the specified file pointer.

[warning] If a pseudo-terminal device is to be used, specify the master device; otherwise the driver will be hung on the open waiting for the master side of the pseudo-terminal to be opened.

 

[caution] If a pseudo-terminal device is used, the scan task must be started before any process tries to open the slave device; otherwise no debug information will be printed.
Windows

This specifies a "named pipe" that will be created on the server machine. Client applications can then make connections to this "named pipe" to receive debug information. A separate thread is created to handle each client. There is a maximum of six client connections allowed. Additional clients trying to connect will fail.

Since this is a "named pipe", clients can connect from other machines on the network.

See the tesserNet Scan Debug Utilities for freely distributable client applications.

[warning] Depending on the network connection speed, some debug data may be lost. Tests here, show that for a full 10 Mbit/sec connection, no data is lost.