sylar

Agree with this ! Llama can't indeed kill the app depending on a predefined condition ...

Just tried the app today, while I'm using the desktop (mac) client for months now. Like everyone here, the heavy battery usage makes the app useless for now. I would like to use it exactly like I'm using Dropbox to sync my photo folder : without thinking at the synchronization at all. For that, the Dropbox client is permently running on the phone, without any battery drain issue, so I guess this will also be possible for btsync in the future. btsync for android is not so old and I will follow the forthcoming developments with attention !

BTsync support send me a 1.1.15_1 version yesterday. With this new version, the problem seems solved. So this bug should be fixed in the next official update I guess.

100% CPU again on my imac. I'm sending you the process sample right now.

I have/had the same problem, see http://forum.bittorrent.com/topic/20610-100-cpu-usage-since-last-update-mac/ So far, "my" BTsycn is running and the 100% CPU bug is gone without any clue on what was the problem ...

While I had already reboot before posting this thread, it seems that this morning all is OK. I have just started the iMac and launched BTsync, exactly like I did on Friday, and this time, no 100% CPU bug. Very strange ...

No, nothing else in the log file. I will send you the process sample on Monday. In the meantime, you can download here the crash file created when the 1.1.12 version crashed.

Sync just crashed. I have a crash file if it can help. EDIT : just tried with 1.1.15 version. Same problem.

Hi, I have just updated to the last available version on my iMac@work, and as soon as sync is launched, it uses 100% of my CPU. The new indexing process is finished, nothing seems to happens, but I get in the log file over and over: [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1: [20130514 15:35:24.378] ping 192.168.1.2:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1: [20130514 15:35:24.378] ping other_mac_ip:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2: [20130514 15:35:24.378] ping 192.168.1.2:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2: [20130514 15:35:24.378] ping other_mac_ip:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3: [20130514 15:35:24.378] ping 192.168.1.2:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3: [20130514 15:35:24.378] ping other_mac_ip:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4: [20130514 15:35:24.378] ping 192.168.1.2:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4: [20130514 15:35:24.378] ping other_mac_ip:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5: [20130514 15:35:24.378] ping 192.168.1.2:1234 directly [20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5: [20130514 15:35:24.378] ping other_mac_ip:1234 directly [20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1: [20130514 15:35:25.382] ping 192.168.1.2:1234 directly [20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1: [20130514 15:35:25.382] ping other_mac_ip:1234 directly [20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2: [20130514 15:35:25.382] ping 192.168.1.2:1234 directly [20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2: [20130514 15:35:25.382] ping other_mac_ip:1234 directly [20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3: [20130514 15:35:25.382] ping 192.168.1.2:1234 directly [20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3: [20130514 15:35:25.382] ping other_mac_ip:1234 directly [20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4: [20130514 15:35:25.383] ping 192.168.1.2:1234 directly [20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4: [20130514 15:35:25.383] ping other_mac_ip:1234 directly [20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5: [20130514 15:35:25.383] ping 192.168.1.2:1234 directly [20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5: So many many "ping" at the same time. Both local machine (192.168.XXX) and other mac (other_mac_ip) are not accessible (BTsync is stopped on these machines, and the local machine is only accessible with a VPN which is not active). On the other mac, no problem, no 100% CPU bug. And the two mac seem to sync well even with this 100% CPU bug. Any idea? Tell me if I can do something else to help to debug!

Yep, my DS213+ can't hibernate anymore.

Works also fine on a Synology DS213+ with DSM 4.2.

It's working now ! In order to avoid the initial upload from the mac to my NAS, I have copied the folder I want to sync with BTsync from the unison "repository" to a new location on the NAS. In this case, it seems I have a problem with some files with non-standard characters in their name. But if I start a new fresh sync, with an empty folder on the NAS at the beginning, then all is OK and the two folders are correcly synced. So I guess I will have to upload all the data from the mac to the NAS to have a correct synchronization between them ...

Thanks for your help rdebath. I will try all your suggestions as soon as possible. And by the way, you are right concerning the NTPd running on port 123 on my NAS. I will shut it down first and try again in the first place.

So, after setting the encoding to UTF8 on both the mac and the NAS, I still get : [20130422 17:55:02] LoadTorrent: requesting to load file A LIRE/Cours/Géométrie Diff.pdf which is modified on disk (cur:1268735002 stored:1268757807) - rejecting until file info is updated [20130422 17:55:02] LoadTorrent: requesting to load file Biblio/10 IROS/Danès.pdf which is modified on disk (cur:1306159750 stored:1306239614) - rejecting until file info is updated This time, only 2 files seem to be problematic. So, I'm not sure if the problem is related to the encoding. BUT, I have just noticed that I have some problem with time settings: the mac and the NAS do not have exactly the same hour. I have sync the NAS with a NTP server, but the mac can't right now do the same (NTP standard port is blocked at work). Can this explain the problem? And if yes, why only 2 files are concerned?

I'm quite surprised since I am using unison right now to perform the synchronization between my NAS and two apple laptops, and I don't have any problem with locales. BTW, I am juste adding the UTF8 support to my NAS to check if all is OK now.

Yep, you're right. I have just checked, and yes, these files are the only one I have with accented characters. I hope this does not mean that I will not be able to sync file with such characters ! (I'm French ...) So, how to cope with that?

Hi, I have a problem with a fresh new sync folder. The sync seems to work correctly, but I have in the log : [20130422 13:55:15] LoadTorrent: requesting to load file A LIRE/Cours/Géométrie Diff.pdf which is modified on disk (cur:1268735002 stored:1268757807) - rejecting until file info is updated [20130422 13:55:15] LoadTorrent: requesting to load file A LIRE/Thèses/Busson.pdf which is modified on disk (cur:1262540501 stored:1268757665) - rejecting until file info is updated [20130422 13:55:15] LoadTorrent: requesting to load file A LIRE/Thèses/MasterThesis.pdf which is modified on disk (cur:1262540454 stored:1268757665) - rejecting until file info is updated [20130422 13:55:15] LoadTorrent: requesting to load file A LIRE/Thèses/Valin.pdf which is modified on disk (cur:1262540457 stored:1268757665) - rejecting until file info is updated [20130422 13:55:15] LoadTorrent: requesting to load file Biblio/10 IROS/Danès.pdf which is modified on disk (cur:1306159750 stored:1306239614) - rejecting until file info is updated So the 2 clients (one on a mac, the other on a NAS) seems to be stuck (they both indicate that there is an ongoing transfer), but nothing is actually happening and the message above is repeating again and again. Any idea on the problem?

Here is my openvpn configuration (very standard one): dev tun tls-client remote MY_NAS_IP 1194 pull proto udp script-security 2 ca ca.crt comp-lzo reneg-sec 0 auth-user-pass So yes, it's using UDP. And I'm able to use this VPN connection. And BTsync *on the same UDP port* (1194) does not work. Can a firewall detect and block a specific kind of data traffic (I mean, here, bittorrent)? You're probably true ... And if I ask them to open a port for a sync based on a bittorrent protocl, they will probably: 1/ never answer; 2/ tell me to go to hell

And here are are the log files. 1st case: mac@work and nas@home, with the mac connected to the work network. In this case, nothing happens, the NAS in not seen by my Mac (firewall problem, probably). On the mac: [20130417 17:29:20] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:20] Got 2 relay ips [20130417 17:29:20] Server ip 67.215.231.242:3000 [20130417 17:29:20] Server ip 67.215.229.106:3000 [20130417 17:29:20] Got 3 tracker ips [20130417 17:29:20] Tracker ip 54.225.100.8:3000 [20130417 17:29:20] Tracker ip 54.225.196.38:3000 [20130417 17:29:20] Tracker ip 54.225.92.50:3000 [20130417 17:29:21] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:21] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:21] ping MY_NAS_IP:1234 directly [20130417 17:29:21] Requesting peers from server [20130417 17:29:22] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:22] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:22] ping MY_NAS_IP:1234 directly [20130417 17:29:23] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:23] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:23] ping MY_NAS_IP:1234 directly [20130417 17:29:24] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:24] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:31] Requesting peers from server [20130417 17:29:31] NAT-PMP: Unable to map port with NAT-PMP. ... etc. On the NAS: [20130417 17:29:50] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:50] Got 2 relay ips [20130417 17:29:50] Server ip 67.215.231.242:3000 [20130417 17:29:50] Server ip 67.215.229.106:3000 [20130417 17:29:50] Got 3 tracker ips [20130417 17:29:50] Tracker ip 54.225.100.8:3000 [20130417 17:29:50] Tracker ip 54.225.196.38:3000 [20130417 17:29:50] Tracker ip 54.225.92.50:3000 [20130417 17:29:50] Adding DHT peer MY_MAC_IP:1234 for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:51] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:51] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:51] ping MY_MAC_IP:1234 directly [20130417 17:29:51] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:51] ping MY_MAC_IP:1234 directly [20130417 17:29:51] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:51] ping MY_MAC_IP:1234 directly [20130417 17:29:51] Requesting peers from server [20130417 17:29:51] Got list of 1 peers from 54.225.196.38:3000 [20130417 17:29:52] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:29:52] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:52] ping MY_NAS_IP:1234 directly [20130417 17:29:52] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:52] ping MY_MAC_IP:1234 directly [20130417 17:29:52] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:29:52] ping MY_MAC_IP:1234 directly ... etc. 2nd case: mac@work and NAS@home, but with the mac beeing connected through my phone In this case, sync works great. 92.90.21.4 is the IP I got from my phone On the mac: [20130417 17:36:42] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:42] Got 3 tracker ips [20130417 17:36:42] Tracker ip 54.225.100.8:3000 [20130417 17:36:42] Tracker ip 54.225.196.38:3000 [20130417 17:36:42] Tracker ip 54.225.92.50:3000 [20130417 17:36:42] Got 2 relay ips [20130417 17:36:42] Server ip 67.215.229.106:3000 [20130417 17:36:42] Server ip 67.215.231.242:3000 [20130417 17:36:43] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:43] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:36:43] ping MY_NAS_IP:1234 directly [20130417 17:36:43] Requesting peers from server [20130417 17:36:44] Incoming connection from MY_NAS_IP:1234 [20130417 17:36:44] Got ping (broadcast: 0) from peer MY_NAS_IP:1234 (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:44] Found peer for folder /Users/sylar/Documents/Administration/Enseignement/Master/M1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX MY_NAS_IP:1234 direct:1 [20130417 17:36:44] Lost peer for folder /Users/sylar/Documents/Administration/Enseignement/Master/M1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:44] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:44] Got id message from peer synok (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) 1.0.134 [20130417 17:36:44] Got state sync request from peer XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:44] Merge: processing get_root message, my hash: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:44] Merge: processing get_availability message, my hash: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, prev hash: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:36:44] State sync finished for folder /Users/sylar/Documents/Administration/Enseignement/Master/M1 And on the NAS: [20130417 17:37:15] ping MY_MAC_IP:1234 directly [20130417 17:37:16] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:37:16] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:16] ping MY_NAS_IP:1234 directly [20130417 17:37:16] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:16] ping MY_MAC_IP:1234 directly [20130417 17:37:16] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:16] ping MY_MAC_IP:1234 directly [20130417 17:37:16] Got ping (broadcast: 0) from peer 92.90.21.4:11931 (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:37:16] Found peer for folder /volume1/homes/sylar/M1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 92.90.21.4:11931 direct:1 [20130417 17:37:17] Going to sync state with peer 92.90.21.4:11931 (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) [20130417 17:37:17] Merge: generating intial request with root XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:37:17] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130417 17:37:17] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:17] ping MY_NAS_IP:1234 directly [20130417 17:37:17] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:17] ping MY_MAC_IP:1234 directly [20130417 17:37:17] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:17] ping MY_MAC_IP:1234 directly [20130417 17:37:17] Send ping to peer (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130417 17:37:17] ping 92.90.21.4:11931 directly Notice the port 11931. Where does it come from? Thanks for you help.

I have just made some tests and have the log files from the NAS and my mac@work. I will provide them ASAP. I'm not an expert in traceroute, but whatever the options on the command line, whatever the port, I just get ... nothing: > traceroute -e -P UDP -p 1234 MY_NAS_IP traceroute to myhome.toto (MY_NAS_IP), 64 hops max, 52 byte packets 1 * * * 2 * * * I have tried with TCP, on other classical ports (80, 443), but ... nothing. But maybe I am making a mistake in how to use traceroute? Actually, I have a public IP (134.15*.*****)! So I'm not really on a LAN... I have shutted down all the softwares during a few hours. No change ...

Hi, I have just ran some tests, and I must confess I don't understand what is happening. But I don't know the filtering rules on my company's firewall, and this might explain the following ... And I'm definitely not an expert in networks! 1/ I have made some nmap tests to check if UDP port 1234 was open for connections from work to home (1234 is the port number bor BTsync on my NAS) : ~% sudo nmap -sU MY_NAS_IP -p1234 Starting Nmap 6.25 ( http://nmap.org ) at 2013-05-16 09:36 CEST Nmap scan report for MY_NAS_IP (XX.XX.XX.XX) Host is up (0.024s latency). rDNS record for XX.XX.XX.XX: myadslbox.titi.toto.net PORT STATE SERVICE 1234/udp open|filtered search-agent Nmap done: 1 IP address (1 host up) scanned in 0.37 seconds So port 1234 is filtered. But this is not so informative ... 2/ I have made the same scan on UDP port 1194 (openVPN port), since I can can connect trough VPN to my NAS. So this should indicate that UDP 1194 is allowed four outbound connections. sudo nmap -sU MY_NAS_IP -p1194 Starting Nmap 6.25 ( http://nmap.org ) at 2013-05-16 09:36 CEST Nmap scan report for MY_NAS_IP (XX.XX.XX.XX) Host is up (0.024s latency). rDNS record for XX.XX.XX.XX: myadslbox.titi.toto.net PORT STATE SERVICE 1194/udp open|filtered openvpn Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds Still indicated as filtered ... but again, VPN connections from work to home are OK. 3/ Just to be sure, I have made a last scan on TCP port 99, on which is running my SSH server. sudo nmap MY_NAS_IP -p 99 Starting Nmap 6.25 ( http://nmap.org ) at 2013-05-16 09:36 CEST Nmap scan report for MY_NAS_IP (XX.XX.XX.XX) Host is up (0.024s latency). rDNS record for XX.XX.XX.XX: myadslbox.titi.toto.net PORT STATE SERVICE 99/tcp open metagram Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds Port open 4/ Since it seems that UDP port 1194 was allowed for VPN, I stopped the VPN server on my NAS, and have run BTsync on port 1194. But still no success, the NAS is not seen by the client. Log are similar: [20130416 09:49:16] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130416 09:49:16] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130416 09:49:16] ping MY_NAS_IP:1194 directly [20130416 09:49:16] Requesting peers from server [20130416 09:49:17] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130416 09:49:17] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130416 09:49:17] ping MY_NAS_IP:1194 directly [20130416 09:49:18] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130416 09:49:18] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130416 09:49:18] ping MY_NAS_IP:1194 directly So, as a conclusion, do I have any chance to make BTsync working at work? Thank you again for your help.

Thank you very much or your response. I wiil try a UDP traceroute tomorrow from work. BTW, I have already tried port 123 on my NAS: - if I'm right, the NAS was still not visible. But I will try again; - I don't know why, but the btsync process is running with 100% CPU on my NAS when using this port (and some other ones I have tested). So I am using port 1234 right now on the Synolgy, and no problem so far. May be a bug? I have also tested through a VPN connection, and it works great. But before envisaging such a solution, I just want to be sure that any other solutions don't work.

BTW, I wonder if the settings "Delete files to Sync trash" actually works on OSX: if I don't active synctrash, files are deleted without going in the OSX trash ...

Yep. But work and home do still not manage to see each other ... I guess this is what appears in the log: [20130414 11:43:31] Got 2 relay ips [20130414 11:43:31] Server ip 67.215.229.106:3000 [20130414 11:43:31] Server ip 67.215.231.242:3000 But what happens if UDP port 3000 is blocked on my company's firewall?

Hi, I'm just discovering btsync, and it is definitely the missing sync software I was looking for for the past two years! So thank you for your work. Now, here is my problem. I have a configuration with 3 machines : 2 mac (at work) + 1 NAS from Synology (at home). I would like to sync multiple folders between them. - The 2 mac sync, since they are on the same local LAN (at work); - If I bring my laptop at home, my NAS sync with it; - but no success in syncing the NAS with the 2 computers at work. Actually, it seems that my company's firewall is blocking the connection between the NAS and the 2 computers. - if I connect my laptop to the web by sharing my phone connection, sync works greats, so the configuration on the NAS (and my personnal router) is OK. So, is there any way to connect my computers to my NAS? Tracker and DHT network are activated in the sharing properties, NAT UPnP is not activated (not working), but it still does not work. Here is a part of the (anonymized) log file on the mac side : [20130414 11:43:31] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:43:31] Got 3 tracker ips [20130414 11:43:31] Tracker ip 54.225.100.8:3000 [20130414 11:43:31] Tracker ip 54.225.196.38:3000 [20130414 11:43:31] Tracker ip 54.225.92.50:3000 [20130414 11:43:31] Got 2 relay ips [20130414 11:43:31] Server ip 67.215.229.106:3000 [20130414 11:43:31] Server ip 67.215.231.242:3000 [20130414 11:43:32] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:43:32] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130414 11:43:32] ping NAS_IP:port directly [20130414 11:43:32] Requesting peers from server [20130414 11:43:33] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:43:33] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130414 11:43:33] ping NAS_IP:port directly ... [20130414 11:43:42] Requesting peers from server [20130414 11:43:42] NAT-PMP: Unable to map port with NAT-PMP. ... [20130414 11:44:31] ping NAS_IP:port directly [20130414 11:44:31] Got 3 tracker ips [20130414 11:44:31] Tracker ip 54.225.92.50:3000 [20130414 11:44:31] Tracker ip 54.225.100.8:3000 [20130414 11:44:31] Tracker ip 54.225.196.38:3000 [20130414 11:44:31] Got 2 relay ips [20130414 11:44:31] Server ip 67.215.231.242:3000 [20130414 11:44:31] Server ip 67.215.229.106:3000 [20130414 11:44:32] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:44:32] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130414 11:44:32] ping NAS_IP:port directly [20130414 11:44:32] Requesting peers from server [20130414 11:44:33] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:44:33] Send ping to peer () for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: [20130414 11:44:33] ping NAS_IP:port directly [20130414 11:44:34] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:44:35] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:44:36] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:44:37] Sending broadcast ping for share XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [20130414 11:44:52] Shutdown. Saving config sync.dat Thanks for your help !