There have been some questions coming in about this, so I want to address it in its own thread and also give our fine beta users a place to offer feedback, ask questions, or raise any issues.
The odrive gateway listens on port 8888 on all available network interfaces for incoming connections from odrive clients.
To ensure that remote clients can access the odrive gateway, you can route incoming connections on port 8888 to the local IP of the odrive gateway. Depending on your network infrastructure, the exact steps to achieve this can vary. I'll go through a simple example here, based on my home odrive gateway setup.
I'm running an old eeepc netbook (1005ha), fronting a 4TB Drobo-FS NAS. I'm currently running Windows 8 on it, but I will most likely switch it out for Linux soon
. I have left everything to auto-configure on the odrive gateway.
In my case, allowing remote access took less than 5 minutes to setup:
1) Install the odrive gateway and invite a remote user.
2) Set a static IP on the eeepc (192.168.100.165). Alternatively, I could've set a static lease, to ensure the IP address assigned by the router would not change.
3) Set a port fowarding rule on the router from port 8888 (TCP) to port 8888 at 192.168.100.165*Depending on your router, this screen may look different*
Depending on your configuration and needs, you may have a couple more steps. Let me know if you need any assistance and I'll do my best to help you through it.