Robots don't have to be in the same network as the Hub; if that's the case the user must manually tell the Robot what Hub to connect to (NimBUS Manager). If the Robot is in a NAT'ed environment the IP address that the Robot registers to the Hub (22.214.171.124) with may not be an address that the Hub or Consoles can use to communicate with the Robot with (10.1.1.1). Robot A (10.1.1.1) <--------------
Robot A (126.96.36.199) ---------> firewall/router --------------------------> Hub A
If you have a situation like this you have two options; installing a Hub with Robot A and use tunnels (recommended if you have more than one Robot in that network) or configure a Network Alias in Hub A's configuration.
A Network alias is an override mechanism that allows you to map either a range of IP addresses or a single address to another IP address. This mapping is triggered by a NimBUS Name Service lookup; when you try to access any of the probes running on Robot A the registered IP addressed is translated by the Alias mechanism during the lookup process and the address that is usable from Hub A is provided.