prosciutboy

Members
  • Content Count

    9
  • Joined

  • Last visited

Everything posted by prosciutboy

  1. Hi RomanZ, your advice is good but I don't really know to check how the DNS resolver works... and I wonder if there is any easy way to modify the way it works. Anyway, I manage to bypass this issue and I can now sync with peers outside my network ! As already stated, the problem is due to the DNS Poisoning performed by the Chinese Great Firewall (the famously terrible GFW). To prevent this alteration, I compiled and configured DNSCrypt on my RPi and the IP of t.usyncapp.com is now resolved perfectly. That might be useful for others so I will write a tutorial in the next days. Thanks aga
  2. In fact the root DNS in China redirect to wrong IPs for "non harmonized" servers (such as btsync trackers it seems). My hosts is as follows cat /etc/hosts::1 raspbmc localhost6.localdomain6 localhost6127.0.1.1 raspbmc127.0.0.1 localhost::1 localhost ip6-localhost ip6-loopbackfe00::0 ip6-localnetff00::0 ip6-mcastprefixff02::1 ip6-allnodesff02::2 ip6-allrouters# btsync tracker and relay IP54.225.92.50 t.usyncapp.com54.225.196.38 t.usyncapp.com54.225.100.8 t.usyncapp.com54.225.196.38 t.usyncapp.com67.215.231.242 r.usyncapp.com6
  3. I edited resolv.conf to use google DNS (8.8.8.8 and 8.8.4.4), the tracker IP is now sometimes 37.61.54.158 sometimes 59.24.3.173. Moreover this is what I get with nslookup. pi@raspbmc:~$ nslookup t.usyncapp.comServer: 8.8.8.8Address: 8.8.8.8#53Non-authoritative answer:Name: t.usyncapp.comAddress: 59.24.3.173pi@raspbmc:~$ nslookup t.usyncapp.comServer: 8.8.8.8Address: 8.8.8.8#53Non-authoritative answer:Name: t.usyncapp.comAddress: 37.61.54.158
  4. After updating btsync to 1.2.92 and an apt-get upgrade of the RPi, I see some improvements: I get access to your share (hello file contents the world) and I even see a peer connected to the same shared directory. But tracker IP in the log is always the wrong address 59.24.3.173. Really weird...
  5. Your are right, the IP does not seem to be a tracker, moreover I cannot ping it. My /etc/hosts forces the following IPs: $ cat /etc/hosts# btsync tracker and relay IP54.225.92.50 t.usyncapp.com54.225.196.38 t.usyncapp.com54.225.100.8 t.usyncapp.com54.225.196.38 t.usyncapp.com67.215.231.242 r.usyncapp.com67.215.229.106 r.usyncapp.comA ping to t.usyncapp.com lead to a working IP $ ping t.usyncapp.comPING t.usyncapp.com (54.225.92.50) 56(84) bytes of data.64 bytes from t.usyncapp.com (54.225.92.50): icmp_req=1 ttl=35 time=298 ms64 bytes from t.usyncapp.com (54.225.92.50): icmp_req=2 ttl=35 time=2
  6. I think you are right a part of the problem comes from my firewall on the raspberry pi. I flushed the iptables rules and the logs looks better: ...Got 2 relay ips[20140321 22:59:58.171] ip 67.215.231.242:3000[20140321 22:59:58.171] ip 67.215.229.106:3000[20140321 22:59:58.197] Got 1 tracker ips[20140321 22:59:58.197] ip 59.24.3.173:3000[20140321 22:59:58.197] Got 1 tracker ips[20140321 22:59:58.197] ip 59.24.3.173:3000[20140321 22:59:58.222] Got 1 tracker ips[20140321 22:59:58.223] ip 59.24.3.173:3000[20140321 22:59:58.248] Got 1 tracker ips[20140321 22:59:58.248] ip 59.24.3.173:3000[20140321
  7. I disabled the firewall and activated UPnP. I can see that the port 8082 is opened in the UPnP status webpage of the router ID App Description External Port Protocol Internal Port IP Address Status2 BitTorrent Sync (TCP) 8082 TCP 8082 192.168.1.110 Enabled3 BitTorrent Sync (UDP) 8082 UDP 8082 192.168.1.110 EnabledI activated the logs with debug.txt and get the error message "Failed to get tracker ips". ...Found peer for folder /btsync/testmg 0___8 192.168.1.105:8086 direct:1Got ping (broadcast: 1) from peer 192.168.1.105:8086 (0___8) for share 5___EFound peer for folder /btsync/testbts 0___8 1
  8. Hi dms2013, UPnP is not enabled on the router. The device with which I am syncing is provided by vrypan (https://github.com/vrypan/btsync-keys) and I am synching btsync-keys directory. I noticed connection sometimes drop so I will add some IPs in the hosts. Nevertheless my PC get the sync very quickly (not even 1 min after btsync starts) whereas my Raspberry Pi have been on for 3 days already and still nothing (I can also see it from the log where I get the "Unable to map port with NAT-PMP" error message). Any ideas?
  9. Hello I am facing a strange issue, I have BTSync running on a PC and and on a Raspberry Pi and I am behind a router with firewall activated: #1 PC running linux 3.13.6-1-ARCH with BitTorrent Sync 1.2.92 Connected via Wifi to router Listening port is set to 8086, this port is forwarded on my router (TCP/UDP) As I am in China I force tracker and relay IPs in /etc/hosts $ cat /etc/hosts...54.225.92.50 t.usyncapp.com67.215.231.242 r.usyncapp.com...BTSync is running as --nodaemon /usr/bin/btsync --config /home/prosciutboy/.config/btsync/btsync.conf --nodaemon Results -> LAN access is work