:::: Self check ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] WireGuard is running
:: [OK] WireGuard is enabled
(it will automatically start on reboot)
:: [OK] WireGuard is listening on port 51820/udp
:::: Having trouble connecting? Take a look at the FAQ:
:::: FAQ - docs.pivpn.io
:::: WARNING: This script should have automatically masked sensitive ::::
:::: information, however, still make sure that PrivateKey, PublicKey ::::
:::: and PresharedKey are masked before reporting an issue. An example key ::::
:::: that you should NOT see in this log looks like this: ::::
:::: YIAoJVsdIeyvXfGGDDadHh6AxsMRymZTnnzZoAb9cxRe ::::
There should be no need to reinstall VPN while changing ISP
Probably the external lan network is using same IP address range as your local network. At least it seems to be an issue of that lan network if other connections working fine.
Do you use the same device for testing on all networks?
IPv6 is not needed. On client app you should see if it connects or not. As well you should see if your client app is retrieving correct IP address for your DDNS. Next check the log within client app.
When I connect to my phone as the hotspot, and turn on the wireguard client on my laptop, I can connect to my network and I am able to access the devices.
If i switch to an external wifi connection, it does not let me connect! zero traffic.
I checked the ip address it’s correct since I am able to connect using a cellular data connection.
I don’t understand why it does not work with LAN.
Do you think it has something to do with the VLANs setup on the new ISP router?
Your mobile phone should also have an IPv6 address when using the mobile internet. Isn’t it?
According to your log, an attempt is being made to establish the connection via IPv4. But for some reason the connection from the affected LAN is not possible. Perhaps something is being blocked. Either in the network itself or at the corresponding ISP.
2024-08-06 03:50:59.695861: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: network is unreachable
2024-08-06 03:50:59.697019: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: network is unreachable
2024-08-06 03:50:59.698615: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: network is unreachable
2024-08-06 03:50:59.713287: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: network is unreachable
2024-08-06 03:51:02.350157: [NET] peer(zj8L…AHTg) - Sending handshake initiation
2024-08-06 03:51:02.351026: [NET] peer(zj8L…AHTg) - Failed to send handshake initiation: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: no route to host
2024-08-06 03:51:02.810763: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: no route to host
2024-08-06 03:51:02.812628: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: no route to host
2024-08-06 03:51:02.813974: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: no route to host
2024-08-06 03:51:02.815353: [NET] peer(zj8L…AHTg) - Failed to send data packet: write udp4 0.0.0.0:49465->119.xx.xx.xx:51820: sendto: no route to host
2024-08-06 03:51:03.695743: [APP] startDeactivation: Tunnel: mba15m3
2024-08-06 03:51:03.699475: [APP] Tunnel 'mba15m3' connection status changed to 'disconnecting'
I understand that. I have used it before when i only had ipv4 on my wireguard server as well.
All i am saying is another person who also only has ipv4 is able to connect but a connection with ipv4 and ipv6 for some reason tries to squeeze into the ipv6 connection and I dont see anything in the docs to disable or force ipv4.
Is there a way in dietpi or wireguard to force it ?
I do not know why you are running around the IPv6 topic. In the logs there is no indication of an attempt to establish an IPv6 connection. All attempts have been made using the same IPv4 address 119.xx.xx.xx. There is one attempt in the log where the connection could not be established and the error message is quite clear as described above.
119.xx.xx.xx:51820: sendto: network is unreachable
119.xx.xx.xx:51820: sendto: no route to host
Perhaps the LAN does not support IPv4? I don’t know.
Anyway, I can’t add anything else here. Maybe @trendy has another idea.
I tried to connect to a SSH port directly in my 5gbps network fro ma 1gbps network and it says there is no path to the host! what the hell ? does that mean these public ip addresses are not able to talk to each other???