• 400 Posts
  • 3.02K 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.



  • 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.