Hacker News new | ask | show | jobs
by NathanKP 4468 days ago
This is really amazing! I had a bit of trouble on my first attempt because I was connected to a VPN, so ShareDrop was considering me to be in the 10.* range (my local IP address on the VPN) while my coworker on the same router showed up in the 192.* range. I was able to send him a file, but he obviously couldn't send me one back because he wasn't connected to the same VPN.

Once I disconnected from the VPN then ShareDrop starting using my local 192.* IP address instead of my remote VPN address and it worked both ways.
2 comments
conductor 4468 days ago
Does this mean that any JavaScript code can determine the client's local IP addresses? Then it can be used for identification, I think browsers should let the users white-list the sites which are allowed to use WebRTC.
link
szimek 4468 days ago
It seems so. I was a bit surprised myself, but this data is taken from the info that browsers send to each other to determine the best path for P2P connection. The actual code for determining local IP is taken from http://net.ipcalf.com.
link
nashashmi 4468 days ago
I believe it is the public IP address and not the local IP address that brings everyone to the same page.
link
jonalmeida 4467 days ago
I don't think that's true. I'm connected to a VPN using the built-in VPN client but none of my traffic is going through it (i.e. Send all traffic over VPN connection is unchecked) and my public IP is still the one that my phone has.

EDIT: It seems that the displayed IP is only incorrect, but the service still works over your local IP.

link