Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't send data [Help wanted] #174

Open
bigbangvn opened this issue Nov 23, 2017 · 6 comments
Open

Can't send data [Help wanted] #174

bigbangvn opened this issue Nov 23, 2017 · 6 comments

Comments

@bigbangvn
Copy link

I tried this on my Mac
Receiver: wdt -directory ~/Download -start_port 22356
Sender: wdt -directory ~/Download -destination 127.0.0.1

And always get error:

connect did not succeed on 127.0.0.1 22356 : Connection refused
W1124 02:04:21.625430 225271808 ClientSocket.cpp:144] wdt> connect did not succeed on 127.0.0.1 22363 : Connection refused
W1124 02:04:21.625440 223662080 ClientSocket.cpp:144] wdt> connect did not succeed on 127.0.0.1 22360 : Connection refused
W1124 02:04:21.625444 222052352 ClientSocket.cpp:144] wdt> connect did not succeed on 127.0.0.1 22357 : Connection refused

Plz help, what's wrong with the command?

@ldemailly
Copy link
Contributor

you need to pass the connection url from the receiver to the sender:
https://github.com/facebook/wdt/wiki/Getting-Started-with-the-WDT-command-line

or disable encryption

@bigbangvn
Copy link
Author

Hi, thanks so much!
I can transfer data when disable encryption:

wdt -directory ~/Downloads/Received --transfer_id=none --encryption_type=none -start_port 22356

But without disabling encryption (wdt -directory ~/Downloads/Received -start_port 22356). When start sender I got this error:

wdt -directory ~/Pictures -connection_url "wdt://bangnguyen:22356?Enc=2:...11635868495635604744...&dir=%2fUsers%2fnguyentb%2fDownloads%2fReceived&id=335681769&iv_change_int=34359738368&num_ports=8&recpv=30"
I1124 23:41:41.783552 2841084736 EncryptionUtils.cpp:84] wdt> Openssl library initialized
I1124 23:41:41.784875 2841084736 WdtResourceController.cpp:29] wdt> Updated max number of senders for root controller to 0
I1124 23:41:41.784901 2841084736 WdtResourceController.cpp:22] wdt> Updated max number of receivers for root controller to 0
I1124 23:41:41.784911 2841084736 Throttler.cpp:67] wdt> No average rate specified
I1124 23:41:41.784919 2841084736 Throttler.cpp:73] wdt> No peak rate specified
I1124 23:41:41.784930 2841084736 Wdt.cpp:24] wdt> One time initialization of WDT for wdt
I1124 23:41:41.784965 2841084736 Throttler.cpp:90] wdt> Updating the rates avgRatePerSec : -1048576.00 bucketRatePerSec : 0.00 tokenBucketLimit : 0.00
E1124 23:41:41.786592 2841084736 EncryptionUtils.cpp:194] wdt> Not hex found 46 in 2:...11635868495635604744...
E1124 23:41:41.786620 2841084736 WdtTransferRequest.cpp:312] wdt> Unable to parse encryption data from "2:...11635868495635604744..." ERROR
E1124 23:41:41.786645 2841084736 wdtCmdLine.cpp:282] wdt> Invalid url "wdt://bangnguyen:22356?Enc=2:...11635868495635604744...&dir=%2fUsers%2fnguyentb%2fDownloads%2fReceived&id=335681769&iv_change_int=34359738368&num_ports=8&recpv=30" : ERROR
I1124 23:41:41.786669 2841084736 WdtResourceController.cpp:294] wdt> Shutting down the controller (0 senders 0 receivers)

@ldemailly
Copy link
Contributor

the connection URL has to be exactly what the receiver outputs on stdout

it seems you copied the logged URL which obfuscate the secret by design, you need to copy the url printed out (or capture it via | like linked above)

@bigbangvn
Copy link
Author

Oh yea, thanks 👍 it's obfuscated url. I can send now with parsed url from stdout!
But I notice that sending with encryption is much slower than no encryption (~700Mbytes/s vs ~60Mbytes/s). Is it expected? Because I thought that AES 128 encryption just increase CPU usage a bit, not expand the data. Could you tell me the reason?

@ldemailly
Copy link
Contributor

not sure, maybe your CPU doesn't have hardware acceleration for encryption, is it old ?

@bigbangvn
Copy link
Author

bigbangvn commented Nov 25, 2017

it's Intel core i5 2.9 Ghz. The terminal show that:
nguyentb$ sysctl -n machdep.cpu.brand_string
Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz

I also see that the CPU is full load 200% when sending. So does the encryption needs lots of power?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants