search

ntop / n2n

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

It is not valid when setting fixed port communication #1083

Open lucktu opened 1 year ago

lucktu commented 1 year ago

edge ... -p xxxx ...

re-open sockets if supernode not responding

Logan007 commented 1 year ago

Hey Lucktu, could you be a bit more specific on this one please? :smile:

lucktu commented 1 year ago

Ok！

On my special network: because of the edge's wan ip change, v1, v2, and v2s are all down, only v3 is still working. And then I add this patch to v2, v2 also works. go on if I add the -p xxx to both v3 and new v2, then they're both down when edge's wan ip changes. when I looked at supernote's management_udp_port, I found that edge's wan ip was still the old (forever?).

Thank you!

Logan007 commented 1 year ago

go on if I add the -p xxx to both v3 and new v2, then they're both down when edge's wan ip changes. when I looked at supernote's management_udp_port, I found that edge's wan ip was still the old (forever?).

So, you mean this re-connect does not work when using -p ... at edge, right?

lucktu commented 1 year ago

Sorry! I know my conclusion may not be right, I just want to drag out the problem smoothly. I've tested 4 different ways. anything with -p is not normal.

lucktu commented 1 year ago

go on if I add the -p xxx to both v3 and new v2, then they're both down when edge's wan ip changes. when I looked at supernote's management_udp_port, I found that edge's wan ip was still the old (forever?).

So, you mean this re-connect does not work when using -p ... at edge, right?

You're right! reboot the edge, might get an error like this:

WARNING: supernode not responding, now trying [118.24..:10090]