-
Posts
124 -
Joined
-
Last visited
-
Days Won
2
Posts posted by dms2013
-
-
What can we expect in 1.3?
http://syncapp.bittorrent.com/ is blocked in China.
As I mentioned in a previous thread, an admin controlled share with new versions (and possible an archive) would be awesome!
-
staalu,
No, it is not DNS cache poisoning. The poisoning technique implies that someone who has no admin access to the DNS server manages to change some DN-IP relation in DNS server cache. Either your ISP or some global country server has wrong address, most likely intentionally.
dms2013,
How your devices are connected to the DLink router? Wi-fi / LAN? How was RPi connected? I can suggest that DLink might NOT transfer Multicast packets between wi-fi and LAN, especially if they are configured as different subnets. Also, shutting down windows firewall is worth checking to find the root cause.
Looking forward for your RPi test.
I tried using OpenDNS 208.67.222.22 and Google DNS 8.8.8.8. Both show the wrong IP when queried without a VPN. I think GFW is very good at what it's doing.
PC and RPi is connected via ethernet and Androids via WiFi. (all on the same subnet, 192.168.0.0/24)
I was unclear in my previous post. (I started writing, then I had to leave and continued when I got back home.)
The RPi could connect to the Android without having to use a VPN or changing the hosts file.
I didn't manage to share files between 2 androids, stuck at connecting. Now I am trying to scan the QR code from my windows desktop and receive the files in the Android. It's stuck on connecting. I will try the same on the RPi. And then disable windows firewall and try on the PC again.
My router is a D-Link 820L (or cloud 2000 something)
Now I tried the above...
So the Windows 8.1 firewall is the culprit. RPi and Windows with disabled firewall works fine to send files to the android.
But still android to android isn't working.
-
So the sync works in LAN with internet on now. That is great. I haven't changed any network setting since last time.
I added the hosts to my windows pc. And I will do the same for the androids, just to be on the safe side.
-
Hi dms2013,
Actually BTSync identifies other BTSync instances in local network over port 3838 using multicast requests. So devices in local network must be visible one to another even if tracker is inaccessible. Please make sure that the port is not blocked by local firewalls.
All people who can't sync in China over internet, please check that:
1) Your computers can resolve DNS names t.usyncapp.com (tracker server) and r.usyncapp.com (relay server). First would be enough for computers to "see" each other (displayed in devices tab). If they can't be resolved - you can try to put actual IPs in your hosts file, 54.225.92.50, 54.225.196.38, 54.225.100.8
2) if you can actually connect to the tracker server. To accomplish this test you'll need a binary file which represents a legitimate request to the tracker server, send it to tracker server and see if response comes back.
For Linux and Mac systems just get the file, put to some folder and run next command from command line:
"cat udp_req.bin | nc -u t.usyncapp.com 3000"
For Windows you'll need to download net cat utility first and run similar command:
"type udp_req.bin | nc -u t.usyncapp.com 3000"
If you can reach the tracker server, you are going to get response starting with "BSYNC..." like this
If you can't - you'll get just nothing after your command.
For the people who can't sync in local network:
1) Please check your firewall settings, if it you are confident that nothing is blocked -
2) I would appreciate collecting full debug logs from 2 peers that can't connect. Please provide logs for analysis and we'll try to find out what's happening.
Looking forward for your test results.I resolv t.usyncapp.com to 37.61.54.158 and r.usyncapp.com to 67.215.231.242. (while using OpenDNS) it's different from the IPs you posted above. The same with Google DNS. GFW Is replacing the IPs in the DNS Query. However, I can ping all 3 of them (54.225.92.50, 54.225.196.38, 54.225.100.8) so adding the hosts would work.
on my L.A. based VPS I resolve t.usyncapp.com correctly.(obviously)
For my home network. I got a simple D-Link router and I haven't really changed any setting (apart from wifi name/password and ISP credentials)
If I don't set the predefined host on my windows pc to connect to the android (would be nice to see the ip:port in the android app, instead of parsing logs), they don't sync. I don't have BTS on my rPi anymore.
Maybe it never gets executed because the t.usyncapp.com isn't responding. (and maybe it works if it is LAN only, and no internet, will try that out, turning off internet, and try to send files between 2 android phones) (just tried while the internet was on, does not work, it is just stuck at connecting, and the Androids are Nexus 4 with Kitkat and no firewall/virusscanner yadda installed.)
I am running Windows 8.1 on my PC. BTS can use any TCP or UDP port in the firewall rule that was added whem installing BTS. So that shouldn't be the issue.
it feels like it's just a simple bug that someone just overlooked.
So I will get BTS rPi running on my again and add ia share that's only on the phone and see if anything happens.
I will send that log your way later.
-
That sounds better! Thank you for clearing that up.
-
I am surprised to read "consider", since BT Sync is supposed to be the same on all devices. I do hope it will be added, as for the selective sync for windows and linux.
-
That I don't know. You tell us.
But I don't think BT Sync has ipv6 trackers. You will probably need to add the host manually, which shouldn't be a biggie on non android devices.
Let us know how it goes
-
You could open a ssh tunnel and connect to localhost. If you are using Windows, putty is very easy to use.
-
Didn't hear anything about BT Chat since it was announced, apart from the email around New Years, that didn't contain any new news about the project.
I had a look at this project, and it's just some documentation about BitCoin and some other stuff.
It is similar to my project
MassageNet
A way for people to get massage, completely anonymous and encrypted.
Just add my secret: <paste secret here>
And read some files containing the information that's in this post.
Nah.
My back hurts, I think I really need a massage now. Later.
-
this does not make sense to be because in https://github.com/vole/vole which requires btsync it says:
- Grab the read-only ID of the person you want to follow. A directory is in progress at vole.cc. Why not start with Vole Team updates? Our key is RA32XLBBHXMWMECGJAJSJMMPQ3Z2ZGR7K.
- Find the Vole users folder. Unless you changed the defaults, it will be in a directory called Vole/users in your home folder.
- Create a new folder in Vole/users, you should name it after the user that you're about to follow. For example, Vole/users/voleteam.
- In BitTorrent Sync, add this new folder as a shared folder, using the read-only key you grabbed in step 1. Instructions are available on their site and vary a little by operating system.
of course 'their site' refers to http://www.bittorrent.com/sync which says nothing about this.
You don't add /Vole or /Vole/Users in BTSync
only /Vole/Users/user1
/Vole/Users/user2
/Vole/Users/user2
and so on.
-
Also a DNS query can contain text not only an IP address.
So you could put a secret in a text record. Maybe that is easier than inventing a new domain system, and maybe easier to remember.
-
BT Sync servers are blocked in China, so without manual configuration of hosts it doesn't work.
Just to be sure. Are you using the same secret on both machines?
If not that, there is something really wrong with something that is hard to figure out without having access to your computers.
I do hope you'll get it to work.
-
That is right. Not sure if that was the issue in their case (but most likely). They never came back.
-
Do you live in China?
-
What if it's a very large site. And you are not interested in watching everything on it?
-
What is your folder layout like? Current shares and the new share.
-
How can they know how many users and how much data that is transferred?
-
Hi guys!
1.2.87 version contains minor UI changes only for Windows OS.
This build is fully compatible with 1.2.82 version.
Thanks!
I am trying to spot any changes but I can't...
An updated change log would e great!
Also, a tease on upcoming features would be nice too.
-
Hello Devs.
It's been 2+ months since anything was written in the changelog.
What is new/fixed in the 1.2.87 and 89 that some people got.
What are upcoming features?
The wishlist is a mile long, so it's difficult to speculate what will actually come and not.
I'm sure lots of people are wondering
Thanks for a great product!
-
Cool! I will keep looking at the progress! Keep it up
-
I don't think it will work well if you have a backup tool that copies the files at the same time you are running bt sync. Stick with 1 solution. Obviously the files aren't identical.
-
So on server A (src) go to the webui and lookup the read-only secret for your share.
Go to server B with ssh and create a new folder (webui can't do it at the moment)
Go to server B (backup) go to the webui and start a new share, use the read-only secret instead of generating a new one and select the folder you just created.
And it should start sending files across.
But remember, if files are deleted on server A they will be deleted or moved to .SyncArchive on server B, default in linux is 30days history.(on android, delete is default) It is possible to change that to something higher if a month isn't enough. I set mine to 10 years, I have plenty of space and I'm better safe than sorry.
-
Hi Terry. There is no BT Sync client or BT Sync server. Just BT Sync. To backup your shares simply add them on another machine using the same unique secret and it will start syncing within minutes.
-
Maybe a typo, maybe not. I hope to see some new version, it's been more than a month since last update and can't wait to try out some new features
.syncignore Behavior Not As Documented?
in Sync General Discussion
Posted
You are doing the opposite. Add the name/extension of files you DON'T want to sync.