Search:

Type: Posts; User: TheFu; Keyword(s):

Search: Search took 0.23 seconds.

  1. [SOLVED] Re: When connecting to server Wireguard VPN, handshake detected, but no internet

    There is absolutely ZERO need to redact private IPs or private DNS IPs.
    Glad my hint about port forwarding was helpful.
  2. [SOLVED] Re: When connecting to server Wireguard VPN, handshake detected, but no internet

    You need to solve this part or it will never work.
  3. [SOLVED] Re: When connecting to server Wireguard VPN, handshake detected, but no internet

    To my knowledge, UFW doesn't have the ability needed to control port forwards. I could be wrong.

    Linux containers and running a VPN server are a terrible idea, even if it works. Don't do it.
  4. [SOLVED] Re: When connecting to server Wireguard VPN, handshake detected, but no internet

    What about the iptables/nftables forwarding rules?

    And I wouldn't assume that it is ok to have duplicate stanza headers.

    I keep the VPN server configured to use a different subnet than where...
Results 1 to 4 of 4