106
General Discussion / Re: DNS over TLS setup and test final
« on: September 25, 2023, 05:18:24 pm »
Don't ever trust free VPNs, how do you think they make money to provide the service? You are the 'product' !
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Install AGH on your OPNsense? Or instead of a port forward just give clients the address of the Pi as their DNS server via DHCP.I know, but I wanted to make things a bit more complicated and learn some networking


[Interface]
# Bouncing = 10
# NetShield = 2
# Moderate NAT = off
# NAT-PMP (Port Forwarding) = off
# VPN Accelerator = on
PrivateKey = ******
Address = 10.2.0.3/32
DNS = 10.2.0.1
[Peer]
# UK#53
PublicKey = ******
AllowedIPs = 0.0.0.0/0
Endpoint = 146.70.83.66:51820
Have you tried all of this?Yep, and with 1 tunnel it works flawlessly, most likely ProtonVPN 'mess up' things with more than 1 connection.
Who is your VPN Provider? If both tunnels use the same ip config, which I see often with WG, you can not have more than one tunnel to that provider.ProtonVPN
The monitor IP must be routed through the tunnel, the endpoint IP mustn't. The tunnel can't be routed through itself.According to the OPNsense guide, as for the IP monitor -> "Insert the endpoint VPN tunnel IP (NOT the public IP) of your VPN provider - see note below" BUT for me it doesn't work, the tunnel shows offline, even if leave it blank, why ??