search

eventure / hide.client.linux

Hide.me CLI VPN client for Linux
https://hide.me
GNU General Public License v2.0
92 stars 35 forks source link

Conn: DPD started but no connection #40

Open morturio opened 1 month ago

morturio commented 1 month ago

Hi,

when I connect to hide.me e.g. via this command:

sudo ./hide.me -4 -d 208.67.222.222:53 connect free-unlimited.hideservers.net

theres no internet connection although it seems the connection is established (there is a vpn-connected-symbol in the linux task tray). log:

Link: Generated a new wireguard private key Link: Wireguard interface vpn activated Link: Wireguard device vpn configured Link: DHCP bypass throw route 255.255.255.255/32 mtu 0 table 55555 added Link: Loopback route 0.0.0.0/0 dev lo mtu 0 table 55555 added Link: IPv4 RPDB rule added Init: Done Conn: Connecting in 0s Link: DNS server throw route 208.67.222.222/32 mtu 0 table 55555 added Name: Resolved free-unlimited.hideservers.net to 45.144.196.98 Link: VPN server throw route 45.144.196.98/32 mtu 0 table 55555 added Conn: Connecting to 45.144.196.98 Pins: Hide.Me Server CA #1 pin OK Pins: Hide.Me Root CA pin OK Rest: Remote UDP endpoint is 45.144.196.98:432 Rest: Keepalive is 20 seconds Rest: Assigned IPs are 10.141.205.197, fd00:6968:6564:6e6::a8d:cdc5 Rest: Gateway IPs are 10.141.204.1, fd00:6968:6564:6e6::1 Rest: DNS servers are 10.141.204.1, fd00:6968:6564:6e6::1 Link: Interface vpn MTU set to 1392 Link: Peer 45.144.196.98:432 added Link: Address 10.141.205.197 added to interface vpn Link: Gateway route 10.141.204.1/32 dev vpn mtu 1392 table 55555 added Link: Route 0.0.0.0/1 via 10.141.204.1 dev vpn mtu 1392 table 55555 added Link: Route 128.0.0.0/1 via 10.141.204.1 dev vpn mtu 1392 table 55555 added Link: /etc/resolv.conf updated Link: Up Conn: DPD started

i tried it with and without -4 -6 -d options and with firewall switched off (-6 does not work at all). without -d the vpn connection symbol in the task tray stays at "connecting"

How to fix/verbose logging? Im on Linux Mint 21.1 xfce, kernel 6.8.0-39.

best regards

tcohar commented 1 month ago

Sounds like a typical censoring scenario. If you need to specify "-d" then you, obviously, can't access our public DNS servers. Without "-d" the client will try to resolve "free-unlimited.hideservers.net", will eventually time out, the kill-switch will kick in to protect you against connection drops and you're left with "connecting" in the tray.

When you connected, using "-d", you successfully resolved our server address, exchanged keys with us ( over HTTPS ), we sent you configuration details for your wireguard kernel module and your client set wireguard up. That's what our client does, such setups. Once the setup is done, wireguard takes over. If wireguard cannot communicate your connection will hang. Since you cannot do DNS UDP, i'm rather sure you cannot do wireguard UDP. Wireguard cannot communicate. If you wait long enough (about 2 minutes) the client will notice and will try to reconnect.

Where are you connecting from ? Is it a firewalled/censored network ?

morturio commented 1 month ago

Where are you connecting from ?

germany

Is it a firewalled/censored network ?

nope. but maybe my ISP is censoring/blocking something?