josh4trunks
-
Posts
11 -
Joined
-
Last visited
-
Days Won
1
Posts posted by josh4trunks
-
-
@PacketMan @RomanZ
btsync is in the official FreeBSD ports tree, and I made the request to update the port to v2.0.105, but it hasn't been committed yet.
-
I the new download scheme a permanent change?
https://download-cdn.getsyncapp.com/2.0.105/FreeBSD-x64/BitTorrent-Sync_freebsd_x64.tar.gz
I was to see if I should change it in the FreeBSD port.
Thanks
-
@koloman
yeah, download the version 1.4 PBI from download.freenas.org and never click update on the plugin's entry on the Plugin > Installed tab.
-
I'm waiting on this to be fixed to update the FreeBSD port and FreeNAS plugin.
Thanks
-
@RomanZ
yup I knew about that one, just forgot to mention it. OK I may try updating the freenas plugin then
-
Has anything changed when compared to the advanced settings documented here?
http://sync-help.bittorrent.com/customer/portal/articles/1590260-preferences-explained
-
600
thanks
-
@RomanZ what is the default value of config_save_interval? I am the maintainer of the FreeBSD port and FreeNAS plugin and want to make sure we set it correctly by default.
Thanks
-
I have installed btsync 100's of times while developing my btsync plugin for FreeNAS. I noticed a bug where the WebUI doesn't always show on a fresh install. The below are in the log when the WebUI isn't showing.
UPnP: Could not map UPnP Port on this pass, retrying.UPnP: Unable to map port 192.168.2.30:13104 with UPnP.
Once the below shows up in the log the WebUI starts working.
NAT-PMP: Mapped TCP port 28721 -> 192.168.2.30:28721NAT-PMP: Mapped UDP port 28721 -> 192.168.2.30:28721NAT-PMP: Got external IP: XXX.XXX.XXX.XXX
My router/firewall is PfSense and I can see from its "UPnP & NAT-PMP Status" that the ports are mapped in all cases so I don't believe the router is the issue.
-
I am getting the below errors in the log when starting btsync on FreeBSD and FreeNAS. I wrote a btsync plugin for FreeNAS and just noticed this when testing advanced options. It doesn't seem to effect functionality though I presume send and receive buffer sizes aren't being changed accordingly.
[20140112 16:00:45.738] UDP setsockopt(SO_RCVBUF, 2097152) failed: 55[20140112 16:00:45.738] UDP setsockopt(SO_SNDBUF, 2097152) failed: 55
To rule out permissions, virtual environments, and maximum system values, I did the following test.
I ran btsync as root on a host FreeBSD system (not in a jail). FreeBSD 9.2's default kern.ipc.maxsockbuf is 2097152. In the config I set 1MB send and receive buffers..
"recv_buf_size" : 1,"send_buf_size" : 1,
A always get the above errors whether or not I..
- set the send/receive buffers low, high, or don't set them
- run as root or as an unprivileged user
- run in a jail or on a host system
Latest 2.0 Desktop Build - 2.0.105
in Sync General Discussion
Posted
joshruehlig@gmail.com is me. I think we have different definitions of port. By official port, I meant it's the the FreeBSD Ports Tree, but you mean port in the more general sense, as in a package maintained by the BitTorrent team.