search

ntop / n2n

Peer-to-peer VPN
GNU General Public License v3.0
6.07k stars 927 forks source link

Failed to ping android or oculus devices to my other edge nodes #1081

Open shenrique38 opened 1 year ago

shenrique38 commented 1 year ago

Hello,

I have tried to setup a connection between two window's pcs and two android devices (a phone and oculus quest 2). I have set my supernode hosted in an aws ec2 instance. I am able to connect all the edges to the supernode without issues, since I receive the ok message at the end in the console for the edge.exe and for the .apk provided by hin2n. I can ping just fine using the address that I set, both my windows edges computers. But I cannot do the same with the android devices.

I am bit lost on what to test next to identify the problem. In case someone could give me a hand, it would be highly appreciated! Thanks!

hamishcoleman commented 1 year ago

I dont know what changes the hin2n people have made to their binaries - have you tried asking them for assistance?

If this was the regular n2n, I would start with useing the command line n2n-ctl tool to check the n2n status at both the edge and the supernode. You should also be able to see if the remote nodes are showing up in the ARP table of your local node after trying a ping

shenrique38 commented 1 year ago

Thanks @hamishcoleman for your reply. I am not sure how to contact the hin2n developers. Should I write a question in another repository ?

I have used the n2n from your repository which is n2n_v3_windows_x64_v3.1. In the folder I have, it contains a group of applications such as the edge.exe, edge_upx.exe, supernode.exe and so on. To use the command you suggested, which aplication should I execute first ? Perhaps n2n-route.exe ? Thanks!

hamishcoleman commented 1 year ago

I just did a quick google and would assume https://github.com/switch-iot/hin2n is the hin2n people.

I'm not sure what the n2n_v3_windows_x64_v3.1 is, as I dont recognise that filename. Especially since it sounds like it has UPX files, which we dont release.

The n2n-ctl is a python script that is included with the source code - it might need you to install some other bits to be able to run this from a windows system

shenrique38 commented 1 year ago

Hi @hamishcoleman,

I appreciate the link you sent me from hin2n group, and will give it a shot.

Regarding the origin of the files I described, I have took them from here https://github.com/lucktu/n2n/tree/master/Windows. I found this repo link in the readme file in the part "Collection of pre-built binaries for Windows: lucktu". Are those pre-built files not from your main n2n project ? If not, in case you know of another place where I could have access to some already built applications, please let me know :)

hamishcoleman commented 1 year ago

Oh, yes, lucktu collects binaries compiled by other people from the internet.

We do have a github action that creates windows binaries, but dont actually have a stable release published with any windows binaries at this time.

However, the script that you can use to debug n2n is in the source code, possibly not included in lucktu's archive. If you are not comfortable with running python scripts (or using tools like netcat) then you might not be interested in using this script to debug your setup

shenrique38 commented 1 year ago

Oh Thanks for the prompty reply. I undertand now those binaries might not be from the same n2n version, or communicate well across platforms. I will try to understand a bit more how to compile the code, and from that point see if I can understand why the android apk is not working. Thanks for your help!