this post was submitted on 07 Mar 2024
297 points (93.0% liked)

linuxmemes

21192 readers
596 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    297
    thx, duck duck joey (lemmy.ml)
    submitted 8 months ago by Samsy@lemmy.ml to c/linuxmemes@lemmy.world
    36 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] solidgrue@lemmy.world 7 points 8 months ago (1 children)

    Not unless your endpoint is configured to act as a gateway (IP forwarding, maybe also with masquerade) and allows other clients to access the IP address ranges you use in your home LAN (AllowedIP).

    [–] ozymandias117@lemmy.world 5 points 8 months ago* (last edited 8 months ago) (1 children)

    That was my assumption, but the way it was stated, I wanted to clarify there wasn’t something special about WireGuard in the way people tend to mean peer to peer

    [–] solidgrue@lemmy.world 5 points 8 months ago* (last edited 8 months ago) (1 children)

    Its peer-tp-peer in that it can be configured in multiple modes on a peer by peer, interface by interface basis. You can make point to point, hub & spoke, or full mesh topologies. If you configure one of the peers for IP forwarding, it can gateway to external networks. If you configure two peers with IP forwarding and establish some routing you can build site to site topologoes, or add more peers for site to multisite and full mesh site topologies. Add IP masquerade (source NAT or PAT) to any of those topologies and it can provide remote access VPN.

    Its very flexible. Most config guides walk you through a basic remote access VPN scenario that lets remote peers access local LAN services at the one end, but not the other, and/or additionally access Internet resources via IP masquerade. The other topologies require more work, but are (edit: not) much more difficult than the remote access use case.

    [–] ozymandias117@lemmy.world 4 points 8 months ago

    Thanks for the in depth explanation.

    When I’m using it from my work laptop to work’s server to access internal sites, it feels very client -> server.

    When they said peer to peer, I was worried I was somehow also exposing my personal devices to work’s network

    I didn’t realize there were so many other ways to set it up