Bug: Pairing won't work for devices in different networks #130
Comments
|
This should be fixed now. Please try again! |
|
I tried again, but unfortunately I still have the same issue.
…________________________________
De: schlagmichdoch ***@***.***>
Enviado: jueves, 27 de julio de 2023 4:47
Para: schlagmichdoch/PairDrop ***@***.***>
Cc: CHRISTIAN MANUEL RODRIGUEZ CHILET ***@***.***>; Author ***@***.***>
Asunto: Re: [schlagmichdoch/PairDrop] Bug:/Enhancement:/Feature Request: Pairing won't work for devices in different networks (Issue #130)
This should be fixed now. Please try again!
—
Reply to this email directly, view it on GitHub<#130 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A4M735JM5MG6MAD6UNBNNULXSI2MTANCNFSM6AAAAAA2ZLJIPU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
any update on this bug? if no -> @schlagmichdoch tag me when it's fixed....please |
|
Unfortuntately, I'm still having the same issue when I tried to pair my device that uses mobile data to a computer in a different network.
https://github.com/schlagmichdoch/PairDrop/assets/119143925/ae5a3cae-a167-4de1-8351-ea258075e36e
|
|
@Manrochri @marcoportincasa Please try again! I cannot reproduce the bug anymore. |
schlagmichdoch
changed the title
|
The issue was finally solved. At first it didn't worked but after installing the app again on my phone and changing the name of both devices it works as it used to do before I reported the issue. Thank you so much.
…________________________________
De: schlagmichdoch ***@***.***>
Enviado: sábado, 29 de julio de 2023 14:10
Para: schlagmichdoch/PairDrop ***@***.***>
Cc: CHRISTIAN MANUEL RODRIGUEZ CHILET ***@***.***>; Mention ***@***.***>
Asunto: Re: [schlagmichdoch/PairDrop] Bug:/Enhancement:/Feature Request: Pairing won't work for devices in different networks (Issue #130)
@Manrochri<https://github.com/Manrochri> @marcoportincasa<https://github.com/marcoportincasa> Please try again! I cannot reproduce the bug anymore.
—
Reply to this email directly, view it on GitHub<#130 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A4M735JA6AFZWKZRO247GUDXSVNZ7ANCNFSM6AAAAAA2ZLJIPU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Great! Thanks for reporting back! I’ll close this then. |
|
I'm having the same issue when trying to pair devices across VLANs. Running 1.7.6 through a reverse proxy with the container running in one of the VLANs. I tried running both clients in each LAN and everything works, perhaps a firewall allow rule is needed? Or does the pairdrop server need to be run from a different LAN from the clients to route correctly? (also the pairdrop.net server works on both clients) |
|
@s-rog Have you included a TURN server in your setup? |
|
Negative, is that required for pairdrop to work for my setup? |
|
I still seem to be seeing this issue with pairdrop.net |
|
Same, I can reproduce it both self-hosted and paidrop.net |
|
@schlagmichdoch could we re-open this? |
|
@louis-pre By chance, Is your NAT network run by a pfSense box? |
|
my vlans are setup on pfsense |
It is not, I tested directly connected to XFinity's router/modem I can do some more tests this evening if you wish |
|
We need to differentiate between self-hosting and the instance running on pairdrop.net when discussing this issue
Yes, a TURN Server is required to route your traffic if you use devices behind different NATs. See Technical Documentation and Deployment Notes. The instance on pairdrop.net is using the TURN server correctly again. Please try again and give feedback whether we can close this issue @louis-pre |
|
@schlagmichdoch the public instance is working again for me 👍 |
|
Are different subnets considered different NATs? or is a TURN server needed whenever a firewall involved? Edit: I read up more on TURN servers and it is indeed necessary, was hoping I could just poke a hole in my own subnet firewall! |
|
@schlagmichdoch Thanks a lot, pairdrop.net works again for me too in all the uses-cases I have tested prior I have not re-tested the self-hosted version again but I'm sure I can make it work if it works in the hosted version 👍 |
Probably both clients have the same public IP address and are therefor shown to each other by PairDrop. The connection still only works when including a TURN server in the setup. Beware that snapdrop.net will show both devices to each other as well but actually sending sth will fail due to the lack of a TURN server.
Sadly this is not the case. If all devices can use IPv6 it might be possible to host PairDrop on IPv6 only which would eliminate the need of a TURN server but also the auto discovery feature for clients in the same network as every devices has its own IPv6 address. I'll close this for now. Thanks @everyone for testing! |
Describe the bug
When trying to pair an android using mobile data to a computer, the paired devices won't appear and in the list of paired devices all are marked as "undefined". So, it won't let me send text or files between my phone and a computer that are not in the same network.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All paired devices appear as "undefined" and those won't be paired
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Self-Hosted
No
Additional context
I used to pair my phone to a computer (both of them in different networks) and it used to work flawlessly. I didn't use to have problems with that kind of pairing. I use pairing on Pairdrop because I found that to be a practical way to share links from my phone to a computer from a classroom without having to log in into any kind of app or website.
The text was updated successfully, but these errors were encountered: