• 494 Posts
  • 4.3K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle


  • They do no such thing.

    The first link explains the protocol.

    The second explains WHY one would refer to client and server with regards to Wireguard.

    My point ties both together to explain why people would use client and server with regards to the protocol itself, and a common configuration where this would be necessary for clarification. Ties both of them together, and makes my point from my original comment, which also refers to OP’s comment.

    I’m not digging you, just illustrating a correction so you’re not running around misinformed.

    It wasn’t clear where OP was trying to make a point, just that the same host would be running running Wireguard for some reason, which one would assume means virtualization of some sort, meaning the host machine is the primary hub/server.


  • Honestly, I know a lot of people that do, but delivery address is less of a problem than other personal information.

    I always make fake derivative versions of my names for anywhere I but from so I can tell who is selling my information and not buy from them anymore. The address matters less. I’m not avoiding the government and “hiding out” fo fuck’s sake, I’m just avoiding having my data leaked like this. Any number of fake names that like up on the same address also dilutes these data sets the shady dealers try and ship around. The more names at any single address reduce the confidence of its accuracy, and therefore price.





  • Uhhhh…that is…not how you do that. Especially if you’re describing routing out from a container to an edge device and back into your host machine instead of using bridged network or another virtual router on the host.

    Like if you absolutely had to have a segmented network between hosts a la datacenter/cloud, you’d still create a virtual fabric or SDLAN/WAN to connect them, and that’s like going WAY out of your way.

    Wireguard for this purpose makes even less sense.






  • Nginx, Traefik, Caddy, HAProxy…lots of options.

    Nginx and Traefik are probably the most complex if you’re not familiar with either.

    HAProxy is dead simple if you solely intend to just use it as a reverse proxy.

    Caddy is fairly simple as well, but slightly more complex than HAP.

    If you’re not familiar with routing and VPNs in general, you may want to have a look at Tailscale or ZeroTier which use Wireguard under the hood, but making the routing dead simple, especially if you’re behind a NAT and don’t want to have to mess with ports forwarding.