search

vi / natram

UDP hole puncher for restrictive-ish NAT
MIT License
5 stars 0 forks source link

ovpn help #1

Open freecode505 opened 2 weeks ago

freecode505 commented 2 weeks ago

C:\Users\Administrator\Downloads>natram.exe --client 216.189.154.18:19929 --bind 127.0.0.1:2323 --sendto 216.189.154.18:1194 --name mcjorsh Dropping foreign message to client port Dropping foreign message to client port

Hello bro, how can I make a connection with ovpn?

With this I am doing the following but it does not work without success

vi commented 2 weeks ago

Are you running a natram --server at 216.189.154.18:19929?

freecode505 commented 2 weeks ago

If my IP is my vps server

freecode505 commented 2 weeks ago

natram.exe --client 216.189.154.18:19929 --bind 127.0.0.1:2323 --sendto 216.189.154.18:1194 --name mcjorsh

Screenshot 2024-06-23 083818

vi commented 2 weeks ago

--bind 127.0.0.1:2323 --sendto 216.189.154.18:1194

This combination of options seems to be strange.

That would expect the following UDP stream between natram and OpenVPN client:

127.0.0.1:2323 <->  216.189.154.18:1194

But 127.0.0.1 typically can only communicate within localhost, not with 216.189.154.18.

Also 216.189.154.18:1194 assumes that you want a VPN between your host and server. I'm not sure why do you need natram in this case - why not just point OpenVPN client to 216.189.154.18:1194 directly?

natram (or similar tool) may be relevant if you want create OpenVPN connection between two clients, both behind NATs, using 216.189.154.18 only for connection establishment, not for the OpenVPN traffic itself. In this mode you would probably omit --sendto entirely on one of the endpoints and listen OpenVPN at 127.0.0.1 on the other endpoint.

Dropping foreign message to client port may be caused by attempts to connect to 127.0.0.1:2323 not from 216.189.154.18:1194, but from some other address.