These are necessary conditions to use GCB in your organization. If you found that GCB is not a right system for your situation, please visit Other Solutions and see if we have a better system for you.
Network Setting
- Outbound connections from the network behind a firewall or NAT must be allowed. Note that this condition is true for most private networks and most firewalls are factory-configured this way. In addition, if you cannot assume a strong control over the firewall/NAT machine for administrative or technical reasons, then GCB may be the best software to use.
System Requirements
- So far, GCB has been tested in the platforms listed below. More machines and platforms will be added later.
- Redhat 9 machines.
Restrictions
Though I tried hard to make GCB versatile, GCB does have restrictions and room for improvements.
- No multithread
- Partial support for nested networks
- One well-known service per inagent
Currently GCB is not thread-safe.
To use GCB in a nested network, GCB inagent must be placed outside or on the boundary of the outermost network. Connections from the public network into any inner network would work just fine. However, connections from a inner network into a deeper network must occur through GCB inagent's relay. For better support of nested networks, GCB inagents must be cascaded together.
(Server) sockets inside the private network lease addresses from their GCB inagent. Because one inagent can rent an address to only one socket, only one instance of a well-known service is possible per inagent.