Jero

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by Jero

  1. Hey Guys,

     

    Is it possible to split the linux config file in multiple files?

     

    I want to have a config file per shared folder. I currently manage 10-20 linux servers. The servers are all connected with btsync.

    I have created a system that can push scripts to the servers en executed them. But when i need to change one shared folder on one server i just want to push a new file without to touch the other parameters in the config file.

     

    Kind regards,

  2. Guys,

    The app crashes after x seconds. I am on version 1.1.12 on Linux 3.9.6-200.fc18.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux

    I created the debug.txt file with the FFFF in it, but when the app crashes there is no debug info in the file (only the FFFF).

    So when i start btsync i can open the webpage, but when i want to refresh the app is already crashed.

    I already resynced the whole sync folder, with no luck...

    Edit: just did a resync again (deleted te .sync folder) and everything is working fine.. but for how long.

    Edit2: and now btsync is using 100% cpu...no transfers or indexing in progress

  3. Very useful! This should be in the (unofficial) FAQ

    Is this realy necessary:

    "Unsolicited packets must be able to traverse your firewall from your port 20001 to Peer's port 20002"

    because i only open outgoing port 3000 if i remember correctly. This mean that you need to open outgoing port for every peer his listening port?

  4. 1) i think so yes.

    2) interesting question for restrictive firewalls like mine :) right now i have outbound port 3000 open for all the btsync clients

    3) did you mean you change your listening port to 3000 of all your clients, if so this isn't possible. Every client need his own unique incomming port in the lan, besides you can only port foreward one port to one client. port forewarding is a one to one relation.

    There is one thing wrong with your setup:

    ANY external IP on 42816 can talk to any internal ip on 42816

    has to be:

    ANY external IP on 42816 can talk to your btsync client ip with the listening port on 42816. (firewall rule) AND you need to create a port forewarding rule (look it op if you don't know what portforewarding means)

    You can subtitute "any external IP" by all your known public ip's (like work, ...)

    But like i said before, this port forewarding stuff is only needed when you want to create a direct connection.

  5. i had a btsync running (132) on a Intel® Pentium® CPU P6000 @ 1.87GHz with freebsd (pfsense) and it takes 20-24% CPU when idle, way too much for a firewall :)

    Compared to my NAS Intel® Core2 CPU 4300 @ 1.80GHz also freebsd (freenas) it takes 2 - 6% when idle

    On my windows machines (core i5) it takes 0.4 - 1%

  6. Hello,

    Btsync is causing a "kernel panic" after x seconds syncing.

    My system:

    FreeNAS-8.3.1-RELEASE-x64 (r13452)

    FreeBSD x.y 8.3-RELEASE-p6 FreeBSD 8.3-RELEASE-p6 #0 r248141M: Sun Mar 10 16:35:05 PDT 2013 root@build.ixsystems.com:/home/jpaetzel/8.3.1-RELEASE/os-base/amd64/tank/home/jpaetzel/8.3.1-RELEASE/FreeBSD/src/sys/FREENAS.amd64 amd64

    btsync: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped

    BitTorrent Sync 1.0.130 and tried with 1.0.132

    problem:

    https://dl.dropboxus...72654/crash.jpg

    Do i need to make a bug report or something?

  7. Ok so 10.10.10.116 can communicate with the tracker (54.x.x.x) on 3000. Thats a start. Now you make sure that your home client can do the same.

    Do not create a direct connection just yet, so just ignore the listening port.

    Also make sure that you enabled the (default on) option to use those trackers

  8. FreeNAS-8.3.1-RELEASE-x64 (r13452)

    FreeBSD x.y 8.3-RELEASE-p6 FreeBSD 8.3-RELEASE-p6 #0 r248141M: Sun Mar 10 16:35:05 PDT 2013 root@build.ixsystems.com:/home/jpaetzel/8.3.1-RELEASE/os-base/amd64/tank/home/jpaetzel/8.3.1-RELEASE/FreeBSD/src/sys/FREENAS.amd64 amd64

    btsync: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped

    BitTorrent Sync 1.0.131

    131 is offline atm, i am going to try 132 (132 is working perfect on my pfsens firewall btw, not the most secure thing to do i know but realy cool i CAN do it!, i realy love the sync app)