Search the Community

Showing results for tags 'nat'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 7 results

  1. Product Resilio Sync Pro 2.6.3 (1340) Pro - as in 5 user license/subscription. Platform(s) : Ubuntu 19.10, Ubuntu 18.04, FreeNAS 11.2 (but also a Win10 laptop at work - happy to leave this out of the equation). Okay - I've done various searches but unable to find more specific information I'm looking for. Everything was working "tickety-boo" in 2018, till my employer started blocking a "vast" range of anything to anywhere TCP/UDP ports... I'm on good terms with one of the Network administrators, and he gave me a list of TCP ports open to "anywhere", e.g. armed with this information I can now ssh to my Raspberry Pi from my desk at work, with a NAT rule on my router. Currently I've implemented a "kludge" - I keep my main home computer (Dell Laptop running 19.10) connected/sync'd via my employer's VPN (horrible Checkpoint SSL product), and I've got "Predefined Hosts" pointing to the IP address of my work Laptop running 19.10, using port 60870. This works. Another even "kludgier" workaround I was using was to insert a 256 GB thumb drive into a BananaPi (M1, running Armbian), running on a LiPo battery, sync everything to there from "home", plonk it on my desk (got a dumb Gbit switch on my desk) and get it sync'd, but the Pi ethernet NIC is a bit "dodgy", had to keep rebooting it (pulling power and pressing power button) - i.e. take it into work, and home again, everyday... So - given this information : Work will let me SOURCE DESTINATION TCP PORT office anywhere 30400 office anywhere 31400 office anywhere 32400 office anywhere 4020 office anywhere 4022 office anywhere 4023 office anywhere 5671 office anywhere 5672 i.e. no UDP it seems, and not "ranges of ports" unless e.g. 5671-5672... Also - I'm using one of these for my SSH NAT rule to my RPi. Here's my "Predefined Hosts" settings for one of my shares, from the Ubuntu machine @home that I keep VPN'd to the office : "tenrji-wk" is an /etc/hosts file entry, pointing to the DCHP leased IP address of my work Ubuntu laptop... I have to edit /etc/hosts if my work computer gets a new DHCP lease. Armed with this information, could I perhaps : Setup (at least one) of my work Resilio Clients to send out on TCP port 30400 to my NoIP dynamic hostname, with my broadband router having a NAT rule to send this traffic to some "port" (e.g. 60870) on one of my home computers. e.g. : SOURCE TCP-Port -> DESTINATION:PORT -> NAT-DEST:NAT-Port desktop 30400 -> -> home-PC:60870
  2. Hallo, as I haven't found an answer to this question I'll just try it here. My assumption is that the "Sync with..." status of peers is chaining such that peers appear as synced (and online) even though this information is only available through one of the peers. Can somebody confirm that? Let me explain my setup. I am using BitTorrent Sync without tracker and relay server. Those are disabled for every folder on every machine and instead predefined hosts are used to talk to the other peers. I am using two 24/7 linux servers behind a NAT-router without upnp where only one of the servers has the BitTorrent Sync port forwarded through the router firewall. Currently me and my MacBook are in a totally different city. I resolve the mentioned NAT router through DynDns and only added the forwarded port to the predefined host list of the MacBook client. Interestingly I can see 2 relays synced (and online) even though my MacBook should only be able to talk with 1. I'd love to see this chaining feature confirmed. Or is there something I am missing? -- ankoh
  3. Hello btsync have wrong implementation of upnp. It works only on networks without routers between network segments. In our case we have follow network organization: Whole network is: This network is divided to subnetworks with 64 host in each other. Now we have 3 subnetworks subnetworks and join to with routers. In we have gateway( to global network. On that gateway work nat, nd upnp server, and btsync client placed in subnetwork When btsync starts it send multicast SSDP discovery(we see this throw wireshark): M-SEARCH * HTTP/1.1 HOST: ST:upnp:rootdevice MAN:"ssdp:discover" MX:3 and gateway response to it: HTTP/1.1 200 OK CACHE-CONTROL: max-age=120 ST: upnp:rootdevice USN: uuid:75802409-bccb-40e7-8e6c-60a44c67052b::upnp:rootdevice EXT: SERVER: RT-N56U/ UPnP/1.1 MiniUPnPd/1.8 LOCATION: OPT: ""; ns=01 01-NLS: 1 BOOTID.UPNP.ORG: 1 CONFIGID.UPNP.ORG: 1337 But btsync just ignore this, and doesn't discovers service list:, which have <deviceType>urn:schemas-upnp-org:device:InternetGatewayDevice:1</deviceType> As a result no any port are opened.
  4. Hi. I would like to sync my raspberry pi with my ubuntu Laptop. For this task i would want to create a ssh tunnel from the ubuntu laptop to the pi. How could i do that, my bittorrent sync traffic would go through this tunnel and start finding my pi as a device? I could also use a vpn, but i would appreciate to use the ssh method. Thanks
  5. My setup is for folders only synced by predefined hosts. Every time I choose a new folder, it has relay servers, tracker servers, and LAN searching on. Instead, I want any folder I create to have my predefined hosts and all these options turned off. Hell, at this point I'd be happy to create a folder that had NONE of these settings activated. Is there something I can adjust to alter what are considered the "default" properties for added sync folders? Thanks for the help.
  6. OK folks - "seasoned network administrator" here. I've been hoping to use BTSync to share some business-related files & directories from my employer's systems, to let their clients more easily access some data, etc. But I've run into an 'Unexpected behavior!' I set up the 'server' - Windows 2008 R2 with BTSync, and share the folder. I've also set a custom 'listen port' and performed a MANUAL NAT / port forward. When the client (who is behind NAT and is *not* supporting uPNP) connects, they get a low, low speed of around 50kilobytes/second, even though the client's download pipe is many, many times that, and the server's upload pipe is many times that as well. When reviewing the open connections on each end, I could see that the 'client' was in fact NOT connecting directly to the 'server.' Is there a reason that the 'relay' servers were being used, even though there was the ability for at least a one-way direct connection? (Yes, I've tested the direct connection, by telnetting to the remote system on the custom port, and I was able to establish a connection). The configuration is fairly normal. Both systems are behind NAT firewalls. The "server" has the custom BTSync port forwarded to it. The expected behavior - direct connection from 'client' to 'server' did not happen. Why? I'm confused. Also, in the logs, I saw the following unexpected entries. Note that port "34780" is *not* the port I used - I in fact specified port 61223 - the 'lan port' it's trying to connect to is the right one, but the port it's trying to connect on the actual WAN interface is very wrong! [2014-02-13 12:59:01.296] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:01.296] ping yyLAN.IPyy.63.13:61223 peer local address[2014-02-13 12:59:02.296] Sending broadcast ping for share 5678obfuscatedshare500[2014-02-13 12:59:02.296] Sending broadcast ping for share 0123ObfucsatedShare012300071[2014-02-13 12:59:02.296] Send ping to peer (01234567obfuscatedpeer000C99) for share 0123ObfucsatedShare012300071:[2014-02-13 12:59:02.296] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:02.296] ping yyLAN.IPyy.63.13:61223 peer local address[2014-02-13 12:59:03.296] Sending broadcast ping for share 5678obfuscatedshare500[2014-02-13 12:59:03.296] Sending broadcast ping for share 0123ObfucsatedShare012300071[2014-02-13 12:59:03.296] Send ping to peer (01234567obfuscatedpeer000C99) for share 0123ObfucsatedShare012300071:[2014-02-13 12:59:03.296] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:03.296] ping yyLAN.IPyy.63.13:61223 peer local address[2014-02-13 12:59:04.297] Sending broadcast ping for share 5678obfuscatedshare500[2014-02-13 12:59:04.297] Sending broadcast ping for share 0123ObfucsatedShare012300071[2014-02-13 12:59:04.297] Send ping to peer (01234567obfuscatedpeer000C99) for share 0123ObfucsatedShare012300071:[2014-02-13 12:59:04.297] ping xxWAN.IPxx.253.205:34780 directly[2014-02-13 12:59:04.297] ping xxWAN.IPxx.253.205:34780 via relay[2014-02-13 12:59:04.297] ping yyLAN.IPyy.63.13:61223 peer local address
  7. I've been able to setup BitTorrent Sync locally, but I'm having trouble getting my router to work with it. In my logs I see "Requesting peers from tracker via UDP" but it says it "Got 3 tracker ips" along with 2 relay IPs. [2013-12-27 20:28:36.527] Got 2 relay ips[2013-12-27 20:28:36.527] ip[2013-12-27 20:28:36.527] ip[2013-12-27 20:28:36.527] Got 3 tracker ips[2013-12-27 20:28:36.527] ip[2013-12-27 20:28:36.527] ip[2013-12-27 20:28:36.527] ip Any idea why it is not using one of the three tracker IPs for the requesting peers? I'm not sure if this is my problem, but I can post the full log file if needed. I am using Sophos UTM as a firewall / router. I've allowed any UDP 3000 traffic, and port forwarded the listening port to the system running BitTorrent Sync. Thanks for any help.