This line is meant to route all outgoing traffic through another tunnel, however, it also has the side effect of making my WireGuard server respond to my external client through another IP (i.e. Im my wg0.conf, I have the following part in my PostUp: iptables -t nat -A POSTROUTING ! -d 10.10.10.0/24 -o pia -j MASQUERADE However I disabled it to make sure it wasn't interfering, and it didn't change anything.Īt this point I don't know what is wrong nor what to search for to help me in figuring this out so any help will be welcomeĮDIT: I kind of figured out where the issue is coming from. I have UFW installed on the server, with the following config: To Action From I've made sure the keys are matching but since the connection works fine when connected to my Wi-Fi, I don't think the config file is to blame. PostDown = iptables -D FORWARD -i %i -j ACCEPT iptables -t nat -D POSTROUTING -d 10.10.10.0/24 -o eth0 -j MASQUERADE iptables -t nat -D POSTROUTING ! -d 10.10.10.0/24 -o pia -j MASQUERADEĪnd the connection file on my phone (running Android 11): ![]() PostUp = iptables -A FORWARD -i %i -j ACCEPT iptables -t nat -A POSTROUTING -d 10.10.10.0/24 -o eth0 -j MASQUERADE iptables -t nat -A POSTROUTING ! -d 10.10.10.0/24 -o pia -j MASQUERADE Since it works fine when I'm connected to my home Wi-Fi, I'm at a loss as to what to look for other that port forwarding, but that works fine as far as I can tell. Peer(.) - Handshake did not complete after 5 seconds, retrying (try 2) ![]() On my phone, I see the following: peer(.) - Sending handshake initiation ![]() Mar 23 17:49:50 wireguard kernel: wireguard: wg0: Keypair 9894 destroyed for peer 16 Mar 23 17:49:50 wireguard kernel: wireguard: wg0: Sending handshake response to peer 16 (:40061) Mar 23 17:49:50 wireguard kernel: wireguard: wg0: Receiving handshake initiation from peer 16 (:40061) Mar 23 17:49:45 wireguard kernel: wireguard: wg0: Keypair 9894 created for peer 16 Mar 23 17:49:45 wireguard kernel: wireguard: wg0: Keypair 9893 destroyed for peer 16 Mar 23 17:49:45 wireguard kernel: wireguard: wg0: Sending handshake response to peer 16 (:40061) Mar 23 17:49:45 wireguard kernel: wireguard: wg0: Receiving handshake initiation from peer 16 (:40061) Here are the logs on my server that appear when I'm trying to connect from my phone (via 4G) Mar 23 17:49:36 wireguard kernel: wireguard: wg0: Keypair 9893 created for peer 16 I've enabled kernel logging for Wireguard to help me troubleshoot this but sadly I haven't been able to find what's wrong with my setup. On my phone, I connect to the VPN using the DNS name (:51820) On my router, I have UDP port 51820 forwarded to my Wireguard server. The problem comes when I disconnect from the Wi-Fi and go on 4G, now my phone is unable to complete the handshake with my server. Utils: Failed to exec 'C:\Program Files (x86)\Pritunl\tuntap\tapctl.I have a Wireguard server on my home network which works fine on all my devices, including my phone when it's connected on Wi-Fi. ▶ utils: Process exec error ◆ arg=string ◆ cmd="C:\\Program Files (x86)\\Pritunl\\tuntap\\tapctl.exe" ◆ output="tap_create_adapter: DiInstallDevice failed\r\nError 0xe0000203\r\nCreating TUN/TAP adapter failed (error 0xe0000203).\r\n" Mat ▶ profile: Connecting ◆ disable_gateway=false ◆ dynamic_firewall=false ◆ mode="ovpn" ◆ profile_id="f27b16c141d176f9" ◆ reconnect=true ◆ sso_auth=false I have installed the generic OpenVPN client and appears to be functioning properly. ![]() Below are the logs from a single convection. I have tried uninstalling and reinstalling the Pritunl client. When I click connect the client asks for my authenticator passcode and after clicking connect I see the status briefly showing “Connecting” followed by “Disconnected” If I look at my network adapters on the system I have noticed that Pritunl creates two new adapters every time I click connect in the client. After installing the latest Windows 11 update I am no longer able to connect to our Pritunl server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |