Pihole, unbound, no internet when wireguard gets activated

Hi there,

I have not changed my setup but since yesterday I can no longer use internet when wireguard is active, neither when in my home plan nor when outside using my mobile internet.

systemctl status wg-quick@wg0.servic doesn’t show errors and is active yet the wireguard app on my phone is looping at the handshake initialisation stage as soon as I activate it.

The only thing I can think is pihole as I did update it couple of days ago. But no settings were changes, permit all origins is still active.

Ddns is set up correctly and works. I can access my pi via ddns when outside of my home network when wireguard is not active.

As soon as I activate, wireguard on my phone, I don’t have internet anymore.

Any ideas how to tackle this? I am out of ideas what to check.

Best,
T

you would need to check if a handshake is done between server and client. On client side, you should have a log within Wireguard App and on server side you can use wg command.

Usually these kind of issues are related to incorrect DDNS settings or wrong port forwarding on router.

I did all of that but seems it was down to not receiving an externally reachable ipv4 address.

No settings changes but all working again.

You can close here.

Best
T

Usually external IP address is assigned to your router and not to a DietPi device. Or what do you mean?

My router no longer receives a public ipv4 address (CG bat). I must have been lucky in the past, but not anymore.

That would mean you don’t have internet access? Or just DDNS not working? Theoretically DietPi is able to update your DDNS as well.

I do have internet access and ddns does work as well as per dietpi-ddns.

But as soon as I activate wireguard, I don’t have internet connection anymore.

Maybe my conclusion is wrong but my router’s IP starts with 100. now which indicates CG nat, or?

I believe (not sure) that before I had a 85. or 95. ip address and my setup and all settings that come with it was working without issues even with wireguard active.

Honestly I don’t know. Maybe @trendy could answer this. Or you can check with your ISP?

I checked with my iso

‘no external ipv4 (guarantee) for private customers as per our terms and conditions, you were just lucky in the past’ (which was for the last 4+ years, but well…now I am unlucky going forward)

  1. IPs are behind cgnat :neutral_face:

:frowning:

Just to finish this…I ended up using tailscale, 10min setup and all working again without specific port forwarding.

probably best in the scenario you are running now

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.