AnsweredAssumed Answered

Setting up a HUB environment with NAT

Question asked by Baltasar_Infante Employee on Nov 12, 2015
Latest reply on Oct 9, 2018 by mark.de.boer

I'm trying to setup the following environment:

 

- Primary Hub with public IP Address: 130.119.150.170

 

- Remote Hub with private address 10.0.3.15 NATed to 141.202.201.38

 

I've tried to run this setup as follows:

 

 

1) Install the Remote Hub by using the Hub installer and selecting Custom and choosing "robot", "hub" and "libraries". The install was successful.

 

2) After that, I went to the primary Hub and added a Network Alias of 10.0.3.15->141.202.201.38.

 

3) After that, I added a Static Route pointing to 141.202.201.38 and I got the error message: Could not connect to Hub: 141.202.201.38! Reason: communication error. The same error is seen if I point to 10.0.3.15.

 

4) After some research, all I got was that "static routes are not a good option, better go with Tunnels".

 

5) I've just created a Tunnel, following the Wiki, but still, I just get to see my Primary Hub on my IM.

 

6) Checking the primary Hub's log, I can see the following errors:

 

Nov 11 16:11:33:244 [3536] hub: ssl_connect - connect to '10.0.3.15:48003' failed (10060)

Nov 11 16:11:33:244 [3536] hub: TSESS could not connect to tunnel 10.0.3.15:48003 (-2)

Nov 11 16:11:33:244 [3536] hub: CTRL could not connect to server 10.0.3.15/48003

Nov 11 16:11:33:244 [3536] hub: CTRL could not connect to 10.0.3.15/48003; 1

 

My first question would be, when you want to connect to Hubs that are in different Networks but there's no firewall in between, shouldn't I go with the "Static Hub Route"?

 

Also, the way I understand tunnels is that you use them when there's a firewall involved or when you want to add security (VPN). Would we use tunnels "just" to connect two Hubs that are in different networks?

 

Finally, any idea on why I can't get my Hubs connected with the configurations I've already tried?

 

Thanks a lot!

 

Balta.

Outcomes