• 0 Posts
  • 215 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












  • I’m sorry, I forgot to mention that you have to press the PS button once after plugging it in. Did you do that?

    If that doesn’t work try restarting Steam and look into your controller settings if it works there, if it does you’re good to go

    Keep in mind that many games don’t natively support Playstation controllers. You can work arround this by emulating an Xbox controller instead (enabling your PS4 controller in Steam should do just that for Steam games). Or alternatively do this regedit edit in your games Wineprefix to achieve the same in any launcher of your choice

    If all else fails it might be worth trying out ds4drv

    Good luck my guy and (hopefully) have fun gaming! :)