This is a draft. It should eventually be folded into the manual. -GCB, or Generic Connection Brokering, allows Condor installations behind firewalls and NATs to communicate with machines on the other side. Two sets of machines behind different firewalls can even communicate. +GCB, or Generic Connection Brokering, allows HTCondor installations behind firewalls and NATs to communicate with machines on the other side. Two sets of machines behind different firewalls can even communicate. (It is possible to put large holes in your firewall or NAT to allow incoming and outgoing connections instead of using GCB.) @@ -8,7 +8,7 @@ 192.168.0.101, 192.168.0.102, and 192.168.0.103. *:*TODO* Document standing up the GCB brokers -*:The following goes in your Condor configuration file. These setting must be visible to all Condor machines that need to use the GCB broker. If a daemon communicates with machines outside of your firewall or NAT for any reason, it will need GCB configured. +*:The following goes in your HTCondor configuration file. These setting must be visible to all HTCondor machines that need to use the GCB broker. If a daemon communicates with machines outside of your firewall or NAT for any reason, it will need GCB configured. {code} # Turn on GCB # Note: this automatically turns on BIND_ALL_INTERFACES.