never made it to transfer file in my home LAN

[sangshuduo]

I use one Win10 machine to send file then use another mac to receive but never made it work. Wondering if something I missed.

Win10 side output:

pcp.exe send '.\Downloads\Telegram Desktop\2018-09-01.pdf' Code is:  sweet-curve-gym-rigid On the other machine run:        pcp receive sweet-curve-gym-rigid could not establish enough connections to bootstrap peers        failed to dial QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt: no good addresses        failed to dial QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa: all dials failed  * [/ip6/2604:1380:0:c100::1/tcp/4001] dial tcp6 [2604:1380:0:c100::1]:4001: connectex: A socket operation was attempted to an unreachable network.  * [/ip4/147.75.77.187/tcp/4001] dial tcp4 0.0.0.0:65322->147.75.77.187:4001: i/o timeout        failed to dial QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb: all dials failed  * [/ip4/147.75.83.83/tcp/4001] dial tcp4 0.0.0.0:65322->147.75.83.83:4001: i/o timeout        failed to dial QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN: all dials failed  * [/ip6/2604:1380:1000:6000::1/tcp/4001] dial tcp6 [2604:1380:1000:6000::1]:4001: connectex: A socket operation was attempted to an unreachable network.  * [/ip4/147.75.109.213/tcp/4001] failed to negotiate stream multiplexer: read tcp4 192.168.1.69:65322->147.75.109.213:4001: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.        failed to dial QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ: all dials failed  * [/ip4/104.131.131.82/tcp/4001] failed to negotiate stream multiplexer: read tcp4 192.168.1.69:65322->104.131.131.82:4001: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. this means you will only be able to transfer files in your local network

Mac side output:

Looking for peer sweet-curve-gym-rigid...
could not establish enough connections to bootstrap peers
failed to dial QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb: no good addresses
failed to dial QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt: all dials failed
 * [/ip6/2604:1380:3000:1f00::1/tcp/4001] dial tcp6 [2604:1380:3000:1f00::1]:4001: connect: no route to host
failed to dial QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ: all dials failed
 * [/ip4/104.131.131.82/tcp/4001] dial tcp4 0.0.0.0:59217->104.131.131.82:4001: i/o timeout
failed to dial QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa: all dials failed
 * [/ip6/2604:1380:0:c100::1/tcp/4001] dial tcp6 [2604:1380:0:c100::1]:4001: connect: no route to host
context deadline exceeded
this means you will only be able to transfer files in your local network

[dennis-tra]

Hi @sangshuduo

It seems that the bootstrap peers are unreachable from your network - but this should not interfere with a file transfer in your local network (besides the log output).

I'm suspecting that a firewall on your Windows machine is blocking pcp. Could you try to send a file the other way around (Mac -> Windows)?

On my Mac I'm receiving the following pop-up when running pcp send that I confirm by clicking on Allow:

I can imagine that something similar is happening on Windows but without a user-facing notice.

As noted in the README here, I have only tested transfers between Mac and Linux - so it's great that you're providing some insights here!

EDIT: Another thing I'm noticing: The line breaks seem wrong on windows. It looks like just one long string.

[sangshuduo]

@dennis-tra mac->windows works.

[dennis-tra]

That's good to hear. I had the opportunity to test on a windows PC today as well and could not transfer a file from windows -> mac. I have added it to the project plan and need to look into that 😕

Thanks for reporting!

[sangshuduo]

OK. wish Windows get working soon.

[sergeevabc]

Tried to send a file to myself. Took 3 minutes and 1 second just to locate a peer. Unacceptable, sorry.

[dennis-tra]

Hi @sergeevabc,

as stated in the readme:

If you're on different networks the lookup can take quite long (~ 2-3 minutes).

So it's not really surprising to me. However, if your nodes are on the same network the peer discovery shouldn't take longer than a couple of seconds - >3 minutes would surprise me in this case.