yottabit

Sync 2.0.120 Nat Issue

Recommended Posts

I had sync'd 750 GB of files from my home NAS (FreeBSD) to a Linux VM on Google Cloud Platform (GCP), using EROS from NAS -> GCP.

 

I was doing it to test a difficulty I had sync'ing to my friend's FreeBSD NAS with the same EROS where it would just stall at a high number of files remaining and never continue, no matter what we did (check UPnP rules on routers, create static port mappings, restart btsync, delete and re-add secret, etc.). Finally he deleted the EROS share and all data, and added it back at the same time I added the EROS to my GCP. Three-way sync started immediately and completed without issue. (Actually there were three files on my NAS that wouldn't sync until I ran "touch" on them, but that's not relevant to this issue.)

 

Now that the sync is complete, I wanted to switch to ROS instead of EROS on my GCP. The data is already there as I had it sync'd before and didn't delete it while I was doing the EROS test.

 

Unfortunately the GCP instance just sits there without transferring any files at all from my NAS or my friend's NAS. After a day it still says 55,024 files remain.

 

Looking into the logs on both sides, it seems like my NAS instance is trying to connect to the private 10.x.x.x IP of the GCP rather than its ephemeral public IP. This is a static mapping done by Google's firewall rules and I haven't changed anything. Other services are continuing to work just fine.

 

Any ideas what to try to get my and my friend's NASes to connect to the ephemeral public IP of GCP rather than the private 10.x.x.x IP of the VM host running the btsync instance?

 

netstat on the GCP instance shows an established connection, yet in the logs I see attempted hits on that private IP.

 

GCP:

$ netstat -a | grep 4242tcp        0      0 *:4242                  *:*                     LISTEN     tcp        0      0 nas2-150127a.c.al:41967 pool-173-71-51-47.:4242 ESTABLISHEDudp        0      0 *:4242                  *:*

FreeNAS:

# netstat -a | grep 4242tcp4       0      0 nas1.4242              250.51.154.104.b.41967 ESTABLISHEDtcp4       0      0 *.4242                 *.*                    LISTENudp4       0      0 *.4242                 *.*

GCP log:

$ grep 173.71.51.47 sync.log$ grep 172.16.42.25 sync.log

FreeNAS log:

# grep 10.240.140.165 sync.log [20150606 11:09:50.423] SD[EDC6]: Peer 2: local IP 10.240.140.165:4242# grep 104.154.51.250 sync.log[20150606 11:08:20.588] SF[EDC6] [12B9]: Going to send state notify to peer 104.154.51.250:41967 - root:D0B769EF3F6A6734970A3CC4412BD87E9490B7C8 pieces:4FB9897D0C1C0F182B46CBF77FF02911A1F4E8D6[20150606 11:09:50.423] SD[EDC6]: Peer 2: 104.154.51.250:4242 10E9410CB526E9C5364A6B921C622BC9C82512B9[20150606 11:10:00.443] SF[EDC6] [12B9]: Going to send state notify to peer 104.154.51.250:41967 - root:D0B769EF3F6A6734970A3CC4412BD87E9490B7C8 pieces:4FB9897D0C1C0F182B46CBF77FF02911A1F4E8D6[20150606 11:10:00.780] Incoming connection from 104.154.51.250:41967

I'm perplexed.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.