• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: November 10th, 2023

help-circle

  • No, AllowedIPs should be set to your internal Wireguards IP range to only allow access to your Wireguard peers. You could also add more like your Servers LAN for example (which will need packet forwarding, as I mentioned before)

    Here’s an example of one of my client configs:

    [Interface]
    Address = 10.8.0.2/32
    PrivateKey = 
    
    [Peer]
    PublicKey = 
    PresharedKey = 
    Endpoint = 192.168.0.3:51820
    AllowedIPs = 10.8.0.0/16
    

    Just be careful to not mess up your subnet masks. For example my [Interface] Address ends with /32 because that only leaves 10.8.0.2 In the [Peer] Section i set it to /16 which will allow the client to connect to 10.8.x.x iirc

    Best is to just try it yourself and see if it works, I’m by no means good at networking stuff




  • It’s mostly people on older cards with those problems I guess

    Me for example on my GTX 1080 can’t use G-Sync (monitor blacks out in specific fps ranges). Nvidia “fixed” this like 5 times already. Newer cards work correctly I guess?

    I also get graphical bugs in Wayland after Nvidias final Wayland “fix”. Other people somehow do not experience this so I guess newer cards work correctly (again)

    Imo Nvidia just didn’t bother fixing this on their old cards so there is a minority left with those problems which can be ghosted safely by Nvidia because “those bugs got fixed”

    It’s not uncommon for Nvidia to ignore their normal users since the most money comes from other companies purchasing their GPUs anyway