Home → Problems →

RPC over a WAN acts strangely

• Edit

Mike

25 Sep, 2013 09:07 PM

When running rpcd in a separate network from the rpc client, the client is unable to route to the rpcd after the initial connection setup in a standard configuration. The rpcd binds to the eth0 ip address (or 0.0.0.0) just fine by doing rpcd --address 0.0.0.0 --port 7331. I am able to initiate the rpc connection over the public internet just fine and can see the connection when following the server stdout. However, the next step is for the rpc client to initiate a new connection back to the rpcd and it tries to connect to the bound IP of the rpcd which is 0.0.0.0 in this example. I end up getting a [-] Connection closed [Errno::ETIMEDOUT] on the client side.

I am able to work around this issue by setting the hosts file on the rpcd server to map 0.0.0.0 to a FQDN and then map the external IP address of the rpcd server to the same FQDN on the client side. Then I run rpcd --address my.fqdn.com --port 7331 on the server which listens on 0.0.0.0 and also tells the client to connect to my.fqdn.com which it will resolve to the external IP.

Obviously this is not ideal ... Hopefully my explanation was not too confusing.

Thanks,

1. Support Staff 1 Posted by Tasos Laskos on 25 Sep, 2013 09:14 PM

   

   Is there a reason why you don't want to provide your WAN IP address as the Dispatcher's --address option?

   • Edit

2. 2 Posted by Mike on 25 Sep, 2013 09:39 PM

   

   eth0 only knows of its internal network and it cannot bind to the WAN IP... It's running NAT'd behind some Amazon magic.

   Attached is the trace when I tried it anyway (replaced real WAN IP with 5.5.5.5)

   • wan_stacktrace.txt 17.1 KB
   • Edit

3. Support Staff 3 Posted by Tasos Laskos on 25 Sep, 2013 09:47 PM

   

   That's a good point, but since the Dispatchers need to know of their external IP address I'll have to add a separate option for that.

   I'll let you know when I have this ready.

   Cheers

   • Edit

4. Support Staff 4 Posted by Tasos Laskos on 25 Sep, 2013 11:16 PM

   

   I've finished it, now running some tests and will be in tomorrow's nightlies for you to check out. Will update this ticket when the nightlies are up.

   Cheers

   • Edit

5. Support Staff 5 Posted by Tasos Laskos on 26 Sep, 2013 09:26 AM

   

   Ok, the update is in the nightlies, you can use the --external-address option to specify the address the Dispatcher should advertise to its clients.

   Let me know how it works.

   Cheers

   • Edit

6. 6 Posted by Mike on 27 Sep, 2013 02:46 PM

   

   Confirmed that it works now.

   Thanks!

   • Edit

7. Support Staff 7 Posted by Tasos Laskos on 27 Sep, 2013 02:47 PM

   

   No worries man, glad it's working. :)

   • Edit

8. Tasos Laskos closed this discussion on 27 Sep, 2013 02:47 PM.