Gigabyte Express 7 for Mac OS X and Linux provides the highest performance file transfer solution when you need to move large files by way of Internet Protocol (IP) backbones.
Two transport types are supported, TCP and RELIA.
RELIA™ technology (Patent Nos. US 6,445,717, US 6,895,019) Enhances TCP (Transmission Control Protocol) to handle packet loss (also called congestion) and long delay (also called ping time or latency) - your information gets through under harsh network conditions. Niwot's RELIA Technology is an extension to TCP which adds redundant information that enables the receiver to reconstruct lost information without requiring the time delay of retransmission. RELIA™ Technology also adds support of 32 bit window size.
The first application to support RELIA was Niwot's Gigabyte Express for Windows 5.0. RELIA Technology uses Large Window and Packet Recovery™ techniques to optimize throughput over the congested international and satellite Internet or intranets. With 4 percent packet loss, RELIA Technology is 2.9 times as fast as naked TCP on the national Internet, 8.8 times as fast on the international Internet, and 15.8 times as fast on the satellite Internet.
Gigabyte Express 7 also includes the File Pipeline - Improves multi-file transfers by filling the data pipe, 5 times as fast for large numbers of small files when compared to a protocol such as FTP which requires the first file transfer be complete before the second file transfer is begun.
1) Mac OS X / Linux
2) 20 Megabytes of disk storage.
3) A minimum of 256 Megabytes of RAM, 512 Megabytes or greater is preferred.
4) Gigabyte Express 7 uses up to 5 megabytes of RAM per session, and can run up to 16 simultaneous answer sessions and 8 simultaneous dial sessions.
RELIA(tm) Technology is an extension to TCP that uses redundant UDP packets to allow the receiving side to recover from lost packets without requiring the sender to retransmit them. The more redundant packets which are sent, the more severe the congestion can be without degrading performance. The DEMO provides redundancy levels to recover from packets being lost 1 or 2 packets at a time (RED1, RED2 redundancies).
RELIA(tm) Technology also supports a 32 bit window size, allowing full throughput even when faced with the typical 300 millisecond international Internet and 600 millisecond satellite Internet delays.
RED1 is default, can recover without retransmission from single lost packets. Use this for optimum throughput on satellite and international IP connections experiencing low congestion. (the sending side is reporting less than 1 chunk resent per 1000 chunks sent).
RED2 can recover without retransmission from pairs of lost packets. This is a robust level, capable of recovering from most cases of satellite and international congestion.
GBXWin.log entries made by a session using RELIA Technology:
Common information:
Date > Time > Session ID RELIA
Dial Session Connection start:
REDx Connecting on 206.124.12.218 to 185.135.4.151:168
x is 1,2,4, or 8
Connecting on Source IP address to
Destination IP address:Destination port
Answer session Connection start:
Answering on 185.135.4.151:168 from 206.124.12.218
Answering on Destination IP address:Destination port from
Source IP address.
Dial or answer session Connection finish:
REDx: TargetRate=1600 Kbps
x is 1,2,4, or 8
TargetRate= the kilobits/sec link rate requested by PhoneBook entry on the Dialing side
chunks rcvd=40, rercvd=0, sent=2362, chunks resent=4
chunks rcvd=xx, the total number of chunks(multi-packet blocks) received.
rerecvd =xx, the number of extra chunks received(retransmitted by other side)
chunks resent= xx, the number of chunks retransmitted by this station
outgoing lost =305 sent = 16683 rcvd =16378
outgoing lost = xxx is the difference between the number of packets this station sent(given in sent=) and the number of packets the far side received(given in rcvd=).
incoming lost =0 sent= 3745 rcvd =3745
incoming lost=xxx is the difference between the number of packets this station received(given in rcvd=) and the number of packets the far side sent(given in sent=).
Gigabyte Express for Mac OS X and Linux is distributed as a gzipped tar file like "gbxmac7119.tar.gz" or "gbxlin7119.tar.gz".
a) Open a Terminal window and login as the user that you wish to run Gigabyte Express. You may choose to run as root, in all of our examples we will have the username niwot.
b) Download/move the gzipped tar file to where you would like to install the application. We strongly suggest installing in the "/Applications" directory for Mac OS X, and in the "/" root directory for Linux. Running gunzip and then extracting the tar file will create the directory "GBXMac" or "GBXLin":
root# gunzip gbxmac7119.tar.gz
root# tar -xf gbxmac7119.tar
c) Change to the "GBXMac" (or "GBXLin") directory and examine the installed files:
root# cd GBXMac
root# ls -al
-rwxr-xr-x
1 niwot wheel 431271
Jul 14 17:21 gbx
(Gigabyte Express)
-rw-r--r--
1 niwot wheel 109747
Jul 14 16:35 gbx7man.htm
(this user manual)
-rw-r--r--
1 niwot wheel 1259
Jul 19 11:13 GBXMAC.INI
(configuration file) or GBXLIN.INI
-rw-r--r--
1 niwot wheel 565
Jul 14 17:31 GBXPHONEBOOK.INI
(configuration file)
-rw-r--r--
1 niwot wheel 8435
Jul 14 16:17 license.txt
(the license file)
-rw-r--r--
1 niwot wheel 167
Jul 14 17:24 NiwotAutoSendList.txt
(Auto Send List file)
drwxr-xr-x
2 niwot wheel 4096
Jul 19 11:51 Niwot_inBasket
(default incoming directory)
drwxr-xr-x
2 niwot wheel 4096
Jul 19 11:14 Niwot_out2Basket
(test directory)
drwxr-xr-x
2 niwot wheel 4096
Jul 19 11:15 Niwot_out3Basket
(test directory)
drwxr-xr-x
2 niwot wheel 4096
Jul 19 11:15 Niwot_out4Basket
(test directory)
drwxr-xr-x
2 niwot wheel 4096
Jul 19 11:14 Niwot_outBasket
(default outgoing directory)
At this time you may wish to change the permissions on the files in this directory if you wanted everything to be owned by a different user or belonging to a different group. You may need to become the root user to do this (use the su (switch user) command), and you would need to execute the following commands:
root# chown -R john * (everything in this directory and all subdirectories is now owned by the user named john)
root# chgrp -R admin * (everything in this directory and all subdirectories is now belongs to the group named admin)
d) You may start Gigabyte Express immediately with the following command:
root# ./gbx (running as root)
Please click here for more information on starting and stopping the program.
TCP incoming connections start on port 167
RELIA incoming connections start with a TCP and a UDP connection into port 168.
Thereafter the incoming data ports (with ANSWSECOND=32780 in GBX*.INI) are:
answer 1= 32780 (TCP and UDP for RELIA)
answer 2= 32781 (TCP and UDP for RELIA)
answer 3= 32782 (TCP and UDP for RELIA)
............
answer n= (32779 +n) (TCP and UDP for RELIA)
There is no set procedure when uninstalling Gigabyte Express for Mac OS X and Linux. You may simply delete all contents of the installation directory, though you may wish to save the INI files for later testing.
When Gigabyte Express starts running, the initial process begins with root user privileges and then all spawned child processes may take on a different user ID of your choice. You can use the su (switch user) command to become the root user, or you can use the sudo (superuser do) command to run the program as a non-root user. Note that it is not recommended that you run Gigabyte Express solely as the root user, though this is allowed if you desire to do so. You may start Gigabyte Express within the installation directory from a Terminal window as follows:
root# ./gbx (running as root)
or
niwot$ sudo ./gbx (running as non-root user)
You may edit the GBXMAC.INI / GBXLIN.INI file to select which user you wish to run spawned child processes:
If you do start up Gigabyte Express as the root user, you will receive the following warning as a reminder:
Warning, this program running with ROOT user privileges!
If you defined a username in the GBXMAC.INI / GBXLIN.INI file which could not be identified, you will receive the following message:
Aborting, unable to identify user "username"
You may use the tail command to view the program's log files while the program is running. Open up another Terminal window, navigate to the "GBXMac" or "GBXLin" directory and execute the following:
root# tail -f gbxmac.log (or gbxlin.log for Linux)
The data that is written to the log file will now be shown in the Terminal window as the program runs.
To stop tail, press CTRL-C (hold down the Control key and press the C key).
You may choose to have less Answer/Dial sessions than the maximum number permitted. In regards to the lines above, you could choose to have only 1 Dial session, 2 TCP Answer sessions, and no RELIA Answer sessions (or no TCP Answer sessions, and 2 RELIA Answer sessions).
When Gigabyte Express is running, there is one central process running like a "traffic cop", who starts up each Dial session process, and also starts up Answer session "listener" processes. The Answer session "listener" processes will accept incoming Gigabyte Express connections and spawn new Answer session processes to handle the incoming data. If the number of incoming connection requests exceed the allowed maximum number of Answer sessions, they are refused until an existing Answer session process is completed and goes away.
As there is no GUI for Gigabyte Express for MAC OS X and Linux, configuration is done by editing the GBXMAC.INI / GBXLIN.INI and GBXPHONEBOOK.INI files.
A Minimal Example GBXMAC.INI / GBXLIN.INI file
[PREFERENCES]
; Global settings for both Dial and Answer sessions
DEFAULTCHILDPROCESSOWNER=niwot
DISPENNAME=0
LOGFILE=1
LOGACCT=1
LOGACCTFOLDER=
MACHINENAME=
MACSUPPORT=0
PENNAME=lindemo
SERIALNUM=niwotdemo1
SORTTYPE=1
WATCHDOG=3
; BothMaster/BothSessionSpecific
ANSWSECOND=32780
; Global settings for Dial sessions
AUTOEXAMTICK=10
AUTOSENDTICK=10
LRCVERIFY=0
; Global settings for Answer sessions
ALLOWASPATHING=0
ANSWERENCRYPTION=1
AUTOGETSENTHANDLING=USESENT
AUTOGETLEAVEFOLDERS=0
AUTOGETMOVESELECTEDPATH=
INBASKET=/GBXLin/Niwot_inBasket
OUTBASKET=/GBXLin/Niwot_outBasket
; Number of Dial sessions
; (Serial number may enable more or less)
SESSIONSDIAL=1
; Dial session specific settings
AUTOLIST1=NiwotAutoSendList.txt
SENTHANDLING1=USESENT
LEAVEFOLDERS1=0
AUTOSENDMOVESELECTEDPATH1=
; AnswMasterOnly
; Number of Answer sessions that the server can serve at once
; (Serial number may enable more or less)
SESSIONSANSWERTCP=1
SESSIONSANSWERRELIA=1
; AnswMaster/AnswSession Specific settings
; TCP LISTENS ON DEFAULT PORT 167
ANSADDRA=0.0.0.0
TRANSPORTA=TCP
ANSPORTA=167
;
; RELIA LISTENS ON DEFAULT PORT 168
ANSADDRB=0.0.0.0
TRANSPORTB=RELIA
ANSPORTB=168
5.1 Global Answer session settings in GBXMAC.INI / GBXLIN.INI:
5.5 The Gigabyte Express PhoneBook file GBXPHONEBOOK.INI
The Gigabyte Express PhoneBook file GBXPHONEBOOK.INI contains the PhoneBook entries used by the program. These are the entries that outgoing Dial sessions use to connect to remote hosts. A typical entry in the PhoneBook file might look something like this:
Also contained in the PhoneBook file are usernames and encrypted passwords in the [USERS] section, which define the users that are allowed incoming encrypted connections.
5.5.1 Sections within the PhoneBook file
There are 3 sections within the PhoneBook file:
[PREFERENCES]
Contains the [PREFERENCES] PHONELIST and the [PREFERENCES] USERLIST
[PHONEBOOK]
Contains the actual PHONEBOOK entries
[USERS]
Contains any User entries and their encrypted passwords, defined for incoming encrypted connections
• The [PREFERENCES] PHONELIST:
This is a list of the names of all PHONEBOOK entries. In a one-to-one relationship with the PHONEBOOK section entries, i.e. if there are two PHONEBOOK entries named LondonTCP and ParisRELIA, then the PHONELIST would look like:
PHONELIST=LondonTCP;ParisRELIA; (entries are separated by semicolons)
• The [PREFERENCES] USERLIST:
This is a list of the names of all USERS entries (used only for incoming encrypted connections). In a one-to-one relationship with the USERS section entries, i.e. if there are three USERS entries named niwotdemo, Gerald, and Samantha, then the USERLIST would look like:
USERLIST=niwotdemo;Gerald;Samantha; (entries are separated by semicolons)
• The PHONEBOOK section:
These are the actual PHONEBOOK entries. Using the examples above of LondonTCP and ParisRELIA, the PHONEBOOK entries might look like:
• The USERS section:
These are the actual USERS entries, used only with encryption. These entries define the USERS that are allowed incoming encrypted connections. Using the examples above of niwotdemo, Gerald, and Samantha, the USERS entries might look like:
niwotdemo=[niwotdemo]
Gerald=[ENC!29CCDFC711B16DD8] (Click here for an explanation of these encrypted passwords)
Samantha=[ENC!33AD619C72914B4D]
Note that the User "niwotdemo" has the password displayed "in the clear", as this User should be used for encryption demonstration purposes only.
5.5.2 Format of PHONEBOOK entries
Using the example PhoneBook entry of LondonTCP, we will define all fields:
After the "Name=" field at the start of the entry, there are 4 positional parameters (these are ALWAYS in the same order):
Field #1
Dial string
[]
Leave this field blank
Field #2
Transport type
[TCP/IP] or [RELIA RED1] or [RELIA RED2]
The transport type to use (Note the space character between RELIA and RED1/RED2)
Field #3
Remote Hostname/IP Address
[www.yourname.com] or [188.164.16.122]
The Hostname/IP Address of the Remote machine
Field #4
Local IP Address
[0.0.0.0]
The IP Address of the Local machine
Regarding the Remote Hostname/IP Address: This field specifies the Hostname/IP address of the remote workstation with which a Dial session will communicate. This can be entered as a host name (e.g., win.gigabytex.com) or as a "dotted" IP address (e.g., 64.32.164.216).
Regarding the Local IP Address: This field specifies the local IP address used during communication. A local address of 0.0.0.0 is recommended if you are on a machine where your IP address changes, this may happen if you are using DHCP or a dial-up connection. You may enter 127.0.0.1 in both the local and remote IP addresses to test on a single machine. In this case the answer session should be set to answer on 0.0.0.0.
The remaining parameters that you may use in a PhoneBook entry are non-positional parameters (they may be in any order, and they may or may not even exist).
[NoPenName]
Do not use Penname
[NoComp]
Do not use Compression
[Port=167]
Define the Port to use, normally 167 for TCP/IP, 168 for RELIA
[TargetRate=0]
The kilobits/sec link rate, 0 means unlimited (full bandwidth of link). If a non-zero number is specified then the connection will be throttled or governed to not exceed the specified number of kilobits per second. This link rate governor feature allows you to put an upper limit on the amount of bandwidth Gigabyte Express consumes.
If you wish to use Encryption for outgoing connections, then add the following parameters:
(Click here for an explanation of the above encrypted password)
5.5.3 A Minimal Example PhoneBook file
Contents of an example GBXPHONEBOOK.INI:
[PREFERENCES]
PHONELIST=niwothqWin;niwothqWincrypt;niwothqRED1;
USERLIST=niwotdemo;tester;
[PHONEBOOK]
niwothqWin=[][TCP/IP][win.gigabytex.com][0.0.0.0][NoPenName][TargetRate=0][Port=167][Encryption=0]
niwothqWincrypt=[][TCP/IP][win.gigabytex.com][0.0.0.0][NoPenName][TargetRate=0][Port=167][Encryption=1] [Username=niwotdemo][Password=niwotdemo]
niwothqRED1=[][RELIA RED1][win.gigabytex.com][0.0.0.0][NoPenName][TargetRate=0][Port=168]
[USERS]
niwotdemo=[niwotdemo]
tester=[ENC!90DE78102AA39FFC] (Click here for an explanation of this encrypted password)
The example file above defines three PhoneBook entries named "niwothqWin", "niwothqWincrypt", and "niwothqRED1", and also defines two user/password entries named "niwotdemo" and "tester".
5.5.4 Adding entries to the PhoneBook file
• When adding a new PhoneBook entry to the GBXPHONEBOOK.INI file, be sure to edit both of the [PREFERENCES] PHONELIST and [PHONEBOOK] sections. For example, a new PhoneBook entry named "SeattleTCP" would require changes like the following:
Likewise, when removing a PhoneBook entry from the GBXPHONEBOOK.INI file, be sure to remove the entry from both the [PREFERENCES] PHONELIST and [PHONEBOOK] sections.
• When adding a new user/password entry to the GBXPHONEBOOK.INI file, be sure to edit both of the [PREFERENCES] USERLIST and [USERS] sections. For example, a new User named "Tom" would require changes like the following:
[PREFERENCES]
USERLIST=niwotdemo;tester;Tom;
[USERS] Tom=[ENC!2AA39FFC90DE7810] (Click here for an explanation of this encrypted password)
Likewise, when removing a user/password entry from the GBXPHONEBOOK.INI file, be sure to remove the entry from both the [PREFERENCES] USERLIST and [USERS] sections.
Gigabyte Express encryption uses a Diffie-Hellman key exchange, encryption is 128 bit Rijndael. Each new session/connection establishes a different encryption key than the last session/connection.
In order for a local Gigabyte Express machine to communicate in encrypted fashion with a remote Gigabyte Express machine, the following parameters must be in order:
1. The local Gigabyte Express machine must Support/Use or Require Encryption in its configuration of the Dialer's PhoneBook entry in GBXPHONEBOOK.INI.
The Encryption passwords for Gigabyte Express have the following format:
ENC!2AA39FFC90DE7810
Where the first 4 characters ENC! indicate that this is an encrypted password string.
To have Gigabyte Express generate an encrypted password string, use the "-p password" option like so:
root# ./gbx -p password (running as root)
or
niwot$ sudo ./gbx -p password (running as non-root user)
Note that the string password is case-sensitive!
Gigabyte Express will not start up the full application when you use this option, it will only generate an encrypted password string and then the program will return to the command line immediately. Typical output might look like so:
=*=*=*=> PASSWORD [ENC!792ABC9D918C35EB]
Now simply copy and paste the above string into the appropriate place in your configuration file. See example immediately below.
IMPORTANT NOTE: It is strongly recommended that you execute the "history -c" and "clear" commands immediately after copying your encrypted password string, so that no record of your original password exists within this Terminal window.
Let us suppose that we wished to have an encrypted connection, Dialing from the local machine, Answering on the remote machine, with the username of "Joe" and the password of "word4you".
• On the local machine we would run Gigabyte Express with the "-p password" option like so:
Note that the same password "word4you" created different encrypted password strings on the local and remote machines. This is done by design, so that each encrypted password string is unique to the machine where it was created.
This new PhoneBook entry JoesEncryptedTCP can now be used in a NiwotAutoSendList file with an description like:
"Niwot_outBasket" "Niwot_inBasket" JoesEncryptedTCP (Please see Autosend immediately below)
Autosend is a Gigabyte Express feature which supports ongoing, unattended transmission of files from one or more Dial sessions. The sources and destinations for file transfer are supplied by text-based Autosend List files in the Gigabyte Express folder. Filenames for the list files begin with "NiwotAutoSendList". Every file whose first seventeen letters are "NiwotAutoSendList" and which resides in the same directory from which Gigabyte Express was started is available for use. These list files can contain multiple lines, each of which defines the source folder, destination folder, and Phonebook name used during connection.
Autosend supports a [NoFolder] option, which prevents Autosend from expanding or sending any folders within the source folder. To ignore folders within the source folder put [NoFolder] after the Phonebook name.
The frequency that Autosend polls folders is defined with AUTOEXAMTICK. The frequency that Autosend examines files is defined with AUTOSENDTICK.
SENTHANDLINGXXX options allow you to specify what action to take after files and folders are sucessfully transferred, either USESENT, DELETE, or MOVESELECTED. The default USESENT is to create a "source folder"_sent at the same level as the "source" folder, and to move files and folders into it. With DELETE, sent files can simply be deleted. With MOVESELECTED, sent files will be moved to the path specified in AUTOSENDMOVESELECTEDPATHXXX, like "AUTOSENDMOVESELECTEDPATH1=/Test/autosent". The LEAVEFOLDERSXXX option allows folder structures to remain in place after these various file moves or deletions.
The default USESENT will move files to an _sent folder. If you select this option, Gigabyte Express will, after successfully transferring files from the folder specified in the NiwotAutoSendList ("Niwot_outBasket" in our example), move those files to another folder on the sending computer. That folder will be at the same level as the source folder, and the name will be generated by appending "_sent" to the source folder name. PenName folders may be created within that folder, depending on whether Disable PenName was requested by the sender. These folders are created if necessary.
For example, you use Autosend to transfer a file from "Niwot_outBasket" to a remote computer, your PenName is "faststuff", and Disable PenName was not selected. After successful transfer of the file, Gigabyte Express will move the file on your computer from "Niwot_outBasket" to a folder named "faststuff1" within the "Niwot_outBasket_sent" folder.
The source folders and destination folders are enclosed in double-quotes. These can supply a full drive and path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder. Full paths can be entered as:
/directory1/directory2 (and for Windows destinations: drive-letter:\path\folder \\computer\share\path\folder \\server\volume\path\folder)
Source folders must exist to the folder level (\folder in the examples). Wildcards are supported. The question mark (?) wildcard can be used to represent any single character, and the asterisk (*) wildcard can be used to represent any character or group of characters that might match that position in other filenames.
Destination folders must exist to the path level (\path in the examples). The specified folder, and possibly a Penname folder within it, will be created if necessary at the destination side. The destination string is limited to 60 characters.
Autosend now has a WAIT/WHEN feature for the NiwotAutoSendList
script.These features are used to schedule the starting of a
NiwotAutoSendList script file (the WAIT command) or the
sending of files in a specific "hot-folder" (the WHEN
command). Both commands have the same format, but each is
used in a different way. WAIT is placed at the top of the
NiwotAutoSendFile (the first line of script), and is used to
schedule when Autosend can access the "hot-folder" script
lines below. The WHEN command is used at the beginning of a
"hot-folder" script line,and is used to schedule when files
in the specified "hot-folder" can be sent.
Format:
This is StartTime
This is either Duration or EndTime
WAIT hh:mmx yhh:mmx
hh - is hours (24hr time if no x)
mm - is minutes
x - is 'A'(am), 'P'(pm), or not used
Note: If x is not used, hh becomes 24hr time.
y - is either 'd' or 'D'(duration), or not used
Note: If y is not used, the hh:mmx that follows is then considered an EndTime.
Examples:
WAIT 2:00a 6:00p
WHEN 2:01a d0:45 "toCustomerOne" "fromNiwot" "PhoneBookEntry1"
WHEN 3:00 13:45 "toCustomerTwo" "fromNiwot" "PhoneBookEntry2"
WHEN 14:00 d2:00 "toCustomerThree" "fromNiwot" "PhoneBookEntry3"
Explanation of examples:
Line 1 - WAIT until 2:00am to start Autosend and stop at 6:00pm.
Line 2 - WHEN it is 2:01am, send all items in the "toCustomerOne"
hot-folder to the phonebook entry "PhoneBookEntry1",
and place these items into a folder at the destination
called "fromNiwot".
Stop sending newly placed items from "toCustomerOne"
hot-folder after 45 minutes.
Line 3 - WHEN it is 3:00 (24hr time), send all items in the
"toCustomerTwo" hot-folder to the phonebook entry
"PhoneBookEntry2", and place these items into a
folder at the destination called "fromNiwot".
Stop sending newly placed items from "toCustomerTwo"
hot-folder at 13:45 (24hr time).
Line 4 - WHEN it is 14:00 (24hr time), send all items in the
"toCustomerThree" hot-folder to the phonebook entry
"PhoneBookEntry3", and place these items into a folder
at the destination called "fromNiwot".
Stop sending newly placed items from "toCustomerThree"
hot-folder after 2 hours.
NOTE: WHEN commands will not execute if the AutoSendList is
disabled by a WAIT command.
The Autoget feature includes support of an optional "GET" in each line of the AutoSendList and Answer session control of the Handling of files that have been retrieved using Autoget. Each line in the NiwotAutoSendList may have GET after the whenspec(if it exists) and the before the source folder specification. If GET is used, the source folder spec is as it appears to the remote end's Gigabyte Express answer session, and destination folder spec is as it appears to the local Gigabyte Express.
Each line in the NiwotAutoSendList may have the [NoFolder] option after the Phonebook name. Folders within the source folder will be ignored with this option. See above example. Only files will be sent, not folders.
The source folder is enclosed in double-quotes. The contents can be a full path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder. Full paths can be entered as:
/directory1/directory2
Wildcards are supported such as:
/directory1/directory2/*.ZIP
The total number of characters should not exceed 55.
The destination folder is enclosed in double-quotes. The contents can be a full drive and path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder. Full paths can be entered as:
These can supply a full drive and path specification, or a simple folder name. If a full path is not specified, the folders are treated as relative to the Gigabyte Express folder.
Destination folders must exist to the path level (\path in the examples). The specified folder, and possibly a Penname folder within it, will be created if necessary at the destination side. The destination string is limited to 55 characters.
The Gigabyte Express phonebook name is used for the selection of transport, IP address, and such as controlled by the Gigabyte Express phonebook file GBXPHONEBOOK.INI.
The first line will cause all files and folders in the folder "Niwot_outBasket" to be sent using the phone book entry with the name "niwothqWin". The files will be placed in a pen name folder in the folder "from7demo" in the GBXWin folder at the destination.
The second line will cause all files and folders in the folder "Niwot_out2Basket" to be sent using the phone book entry "selfTCP".
The third line will cause all files and folders in the folder "Niwot_out3Basket" to be sent to "niwothqRED1 using RELIA.
The fourth line will cause all files and folders in the folder "Niwot_out4Basket" to be sent to the same machine using RELIA.
7. Configuration Setting Definitions
Global Answer session settings
• ALLOWASPATHING -- Allow Autosend Pathing (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI applies to all Answer sessions. The default is ALLOWASPATHING=0, to not allow Autosend Pathing.
If this setting is ALLOWASPATHING=1, and a remote sender is running Autosend with destination folders specified, files and folders are placed into the specifed destination if it can be found. If it cannot be found the actual destination is reported in the gbxmac / gbxlin.log Log File.
• ANSWERENCRYPTION -- Encryption setting (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI applies to all Answer sessions. The default of ANSWERENCRYPTION=1 is to support encryption. If this setting is ANSWERENCRYPTION=0, meaning "Disable Encryption", then Dial sessions requiring encryption will not be able to connect to this Gigabyte Express machine.
If this setting is ANSWERENCRYPTION=1, meaning, "Support Encryption", Dial sessions requiring or using encryption will be able to connect to this Gigabyte Express machine (assuming their username and password match an authorized username and password) and use encryption. Dial sessions with encryption disabled or dial sessions from versions of Gigabyte Express not supporting encryption will still be able to connect.
If this setting is ANSWERENCRYPTION=2, meaning "Require Encryption", Dial sessions requiring encryption will be able to connect to this Gigabyte Express machine. Dial sessions using encryption will connect (assuming their username and password match an authorized username and password) and use encryption. Dial sessions with encryption disabled or dial sessions from versions of Gigabyte Express not supporting encryption will not be able to connect.
• AUTOGETSENTHANDLING -- Handling of Files After Autoget (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the manner in which files sent via incoming Autoget are handled for all Answer sessions. Currently the options for this setting are:
USESENT
Move files to an "_sent" folder after incoming Autoget (default behavior)
DELETE
Delete files after incoming Autoget
MOVESELECTED
Move files to AUTOGETMOVESELECTEDPATH (see below) after incoming Autoget
• AUTOGETLEAVEFOLDERS -- Leave Folder Structure in Place (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows folder structures to remain in place after files sent via incoming Autoget have been moved or deleted, for all Answer sessions:
0
Delete folder structure after sending files (default behavior)
1
Do not delete folder structure
• AUTOGETMOVESELECTEDPATH -- Files Moved Here After Autoget (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to choose the folder into which files are transferred after incoming Autoget, if AUTOGETSENTHANDLING=MOVESELECTED (see above). Example: "AUTOGETMOVESELECTEDPATH=/SentFiles/autoget" ... for all Answer sessions, this would move all files sent via incoming Autoget to "/SentFiles/autoget".
• INBASKET -- The InBasket (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to choose the folder into which files are transferred from a remote user. The default InBasket for all sessions is "Niwot_inBasket" in the same folder as Gigabyte Express. All Answer windows share a common InBasket. Example: INBASKET=/MyGBXInBasket
• OUTBASKET -- The OutBasket (Answer session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to choose what folder a remote user can access to get files. The OutBasket does not need to be in the Gigabyte Express folder. Some users have their OutBasket on their server. The default OutBasket is "Niwot_outBasket" in the same folder as Gigabyte Express. The remote user will also be able to get files/folders from an OutBasket which matches their PenName. PenName OutBaskets must be in the same folder as Gigabyte Express. Example: OUTBASKET=/MyGBXOutBasket
Specific Answer session settings
• SESSIONSANSWERTCP -- Number of TCP Answer sessions (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the number of TCP Answer sessions. Your serial number may enable more or less TCP Answer sessions. Example: SESSIONSANSWERTCP=1
• ANSADDRA -- TCP Answer IP Address (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the TCP Answer session IP Address. The default TCP Answer IP Address setting is ANSADDR=0.0.0.0
• TRANSPORTA -- TCP Transport Type (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the TCP Transport type. The default setting is TRANSPORTA=TCP
• ANSPORTA -- TCP Answer Port (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the TCP Answer Port. The default setting is ANSPORTA=167
• SESSIONSANSWERRELIA -- Number of RELIA Answer sessions (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the number of RELIA Answer sessions. Your serial number may enable more or less RELIA Answer sessions. Example: SESSIONSANSWERRELIA=1
• ANSADDRB -- RELIA Answer IP Address (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the RELIA Answer session IP Address. The default RELIA Answer IP Address setting is ANSADDRB=0.0.0.0
• TRANSPORTB -- RELIA Transport Type (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the RELIA Transport type. The default setting is TRANSPORTB=RELIA
• ANSPORTB -- RELIA Answer Port (Answer session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the RELIA Answer Port. The default setting is ANSPORTB=168
Global Dial session settings
• AUTOEXAMTICK -- Poll Folders Every xxx Seconds (Dial session Global) Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. The Autosend function will continue to check the specified folders, moving from line to line at the interval specified in seconds. If there are files in the folders, they will be transferred to the destination corresponding to the IP address. The default setting is AUTOEXAMTICK=30 (seconds). Minimum is 1 second.
• AUTOSENDTICK -- Examine Files Every yyy Seconds (Dial session Global) Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. Specifies how long Autosend will wait between successive file examinations. The default is AUTOSENDTICK=30 (seconds). Minimum is 1 second.
• LRCVERIFY -- Read After Write Integrity Check (Dial session Global)
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. Enabling this with LRCVERIFY=1 adds an extra read after write longitudinal redundancy file integrity check at the destination. The default setting LRCVERIFY=0 will not perform the check.
Specific Dial session settings
• SESSIONSDIAL -- Number of Dial sessions (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the number of Dial sessions. Your serial number may enable more or less Dial sessions. Example: SESSIONSDIAL=1
• AUTOLISTXXX -- The Autosend List file (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the Autosend List file for a specific numbered Dial session. Filenames for the list files begin with "NiwotAutoSendList". For example, with Dial session #1 you could define AUTOLIST1=NiwotAutoSendList1.txt and with Dial session #2 you could define AUTOLIST2=NiwotAutoSendList2.txt
• SENTHANDLINGXXX -- Handling of Files After Autosend (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the manner in which Sent Files are handled for a specific numbered Dial session. Currently the options for this setting are:
USESENT
Move files to an "_sent" folder after send (default behavior)
DELETE
Delete files after send
MOVESELECTED
Move files to AUTOSENDMOVESELECTEDPATHXXX (see below) after send
For example, with Dial session #1 you could define SENTHANDLING1=USESENT and with Dial session #2 you could define SENTHANDLING2=DELETE Click here for examples of Sent File Handling in the larger context of Autosend.
• LEAVEFOLDERSXXX -- Leave Folder Structure in Place (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows folder structures to remain in place after the Sent files have been moved or deleted, for a specific numbered Dial session:
0
Delete folder structure after sending files (default behavior)
1
Do not delete folder structure
For example, with Dial session #1 you could define LEAVEFOLDERS1=0 and with Dial session #2 you could define LEAVEFOLDERS2=1
• AUTOSENDMOVESELECTEDPATHXXX -- Files Moved Here After Autosend (Dial session Specific) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to choose the folder into which files are transferred after Autosend, if SENTHANDLINGXXX=MOVESELECTED (see above). Example: "AUTOSENDMOVESELECTEDPATH1=/SentFiles/autosend" ... for Dial session #1 only, this would move all files sent via Autosend to "/SentFiles/autosend".
Global settings for both Answer and Dial sessions
• ANSWSECOND -- The Answer session Data Transfer Port (Answer session Specific)
Defined in GBXMAC.INI / GBXLIN.INI, the default Answer session Data Transfer Port setting is ANSWSECOND=32780, so Answer session #1 will use port 32780, Answer session #2 will use 32781, and so on. User may specify the secondary port numbers by modifying this value. A value of 0 or deleting this parameter will cause the ephemeral ports to be used.
• DEFAULTCHILDPROCESSOWNER -- The Username that will own all child processes (Answer/Dial session Global) Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI allows you to define the Username that will own all child processes of Gigabyte Express. When Gigabyte Express runs, it spawns off child processes to handle all Answer and Dial sessions. The default setting is DEFAULTCHILDPROCESSOWNER=root, it is recommended that you change this to a Username of your choice. Click here to see an explanation of Gigabyte Express in the context of starting all child processes. • DISPENNAME -- Allow PenName Disabling (Answer session Global) Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. The default setting is DISPENNAME=0 to not allow PenName disabling. Set this value to DISPENNAME=1 to allow PenName disabling. If you select this option, and if the sender has chosen to disable the PenName, files and folders will be placed directly in your InBasket without a PenName. Both the sender and receiver must request the no pen name in their respective ways for this to occur. CAUTION: With this option, over-writing of a duplicate file can occur. If the Sender does not disable the PenName, or if the Receiver does not choose the "Allow PenName Disabling" option, all incoming files will be put into correct PenName folders.
• LOGACCT -- The gbxacct.log Accounting Log File Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. The default is LOGACCT=0 to not write the gbxacct.log Accounting Log File. This file maintains a record of the files transferred for accounting purposes. Enable the writing of this file by using LOGACCT=1 for this setting. When you choose to generate a gbxacct.log, it contains one line for every file successfully transferred. The file is organized to allow importing by spreadsheet programs to capture file transfer information for billing purposes. When the file is approximately 5 megabytes, it is copied to gbxacct1.log (after gbxacct1.log is copied to gbxacct2.log). Also see the LOGACCTFOLDER setting immediately below.
Each line of the gbxacct.Accounting Log File has the format:
Date>StartTime>FinishTime>Session ID>FileName>Size>OtherSide ID
The Session ID gives the session number and the direction of the transfer. A Dial session may receive "R"(Get) or send "S". An Answer session may receive "R" or send "S"(in response to a Get))
The OtherSide for an Answer Session has the format "PenName: xxxx" where xxxx is the Other side's PenName. For a Dial session, the OtherSide has the format "PhoneBook: xxxx" where xxxx is the name of the PhoneBook entry.
• LOGACCTFOLDER -- Folder to write Accounting Log File Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. The default is to leave this field blank. If the setting LOGACCT=1 is defined, the gbxacct.log Accounting Log File will be written to the folder where Gigabyte Express is installed. If the LOGACCTFOLDER setting is also defined it will be used, i.e. LOGACCTFOLDER=/Test then the Accounting Log File will be written to /Test/gbxacct.log
• LOGFILE -- The gbxmac.log/gbxlin.log Log File Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. The default setting of LOGFILE=1 is recommended so that a record is kept of the operation of the program, start-up, sending/receiving files, etc. This file will always be written to the folder where Gigabyte Express is installed. Gigabyte Express operations from ALL sessions will be logged here. When the file is approximately 5 megabytes, it is copied to gbxmac1.log/gbxlin1.log (after gbxmac1.log/gbxlin1.log is copied to gbxmac2.log/gbxlin2.log). If desired you may disable writing of the Log File with LOGFILE=0
• MACSUPPORT -- Macintosh file support for LINUX ONLY Back to Table of Contents
Gigabyte Express for Linux may gracefully send and receive Macintosh files when communicating with Gigabyte Express for Mac OS X or Gigabyte Express for Windows (if MACSUPPORT is also enabled on the Windows machine). Users desiring this functionality should set MACSUPPORT=1 in the GBXLIN.INI file. This option should be disabled with MACSUPPORT=0 for non Macintosh-only file operation as it slows down the cataloging of files to be sent. • PENNAME -- The PenName Back to Table of Contents
This setting is defined in the GBXMAC.INI / GBXLIN.INI file. The PenName is used to name the folder on the receiving computer which will contain the files and folders you have sent. For example, let's use the setting PENNAME=Jack ... The first batch of files/folders you send will be placed in the folder "Jack1". The second batch of files/folders you send will be placed in the folder "Jack2", and so forth. The PenName number will increment unless you delete a pen name folder, then it will replace the deleted folder so the numbers remain consecutive.
• SERIALNUM -- The Serial Number Back to Table of Contents
This setting in GBXMAC.INI / GBXLIN.INI is where you may view or change your serial number. Gigabyte Express will not execute without a valid serial number. Demo serial numbers are: SERIALNUM=niwotdemo1 or SERIALNUM=niwotdemo2 or SERIALNUM=niwotdemo3
• SORTTYPE -- The File Sorting algorithm used (Answer/Dial session Global)
If SORTTYPE=1 or if SORTTYPE is not found in the GBXMAC.INI / GBXLIN.INI file then oldest files will be sent first. If SORTTYPE=0 then files will be sent in the order they are found.
• WATCHDOG -- The Watchdog Timeout, in minutes Back to Table of Contents
The WatchDog timer is used to monitor file transfer action between connected computers. If there is no file transfer action within the set WatchDog time, the link between computers will be terminated. The default WatchDog time setting is WATCHDOG=3 (minutes). Edit the GBXMAC.INI / GBXLIN.INI file to define the WatchDog time you would like in minutes. WATCHDOG=0 (zero) indicates unlimited time. With WATCHDOG=0, the link may stay up indefinitely creating high long distance bills.
