• 3 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: July 12th, 2023

help-circle

  • tapdattl@lemmy.worldtoOpen Source@lemmy.mlParadox of tolerance license
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    2 months ago

    How about instead of restricting use of the software, adding in a clause that states "Use of this software is a formal acknowledgement and agreement by the user that race and gender are a social construct, gender identity and sexual orientation is a spectrum, humans can not be illegal,… " etc.

    Thus use of the software is not restricted and is still open source, but forces groups, organizations, and people who disagree with the above to acknowledge something counter to their system of power.










  • Thanks for your response! I’m completely self-taught, so I’ll go ahead and acknowledge knowledge gaps on my end, but how would putting all the nodes in a network cause routing problems or ARP poisoning?

    I recognize that what I’m trying to accomplish is a bit overkill for the average home network, and a lot of my reasoning behind my design is purely for learning. My reasoning for putting everything on a mesh network is 2-fold:

    • Providing encrypted, secure, and mutually identified networking between all nodes
    • Creating a centralized source of truth and control – NetBird runs its own DNS system behind the scenes, which allows all nodes to be addressed by name regardless of location, which interests me because it creates a single point of administration for ACLs, routing, etc. I’m also able to access any node I want across the mesh network as long as I’m connected to it.

    I have successfully run this setup previously with the NetBird management console hosted in a VPS, however the issue I ran into was that if internet went down at home, I could no longer access my locally hosted services through the mesh network. I could still access them via IP, since I was on the same LAN, but that defeats my goal of centralized control, mDNS, and a central source of truth that I got via the mesh network.

    I have also successfully ran this setup completely local, however I am unable to access it from outside my homelab. For my use case, I think having all components of the mesh network hosted within my homelab is the best design. However now I have to figure out the best way to allow external connections to my management interface. Thus my original question should I use a cloudflare tunnel to my management interface, set up a wireguard tunnel from an externally accessible VPS service pointed to my management interface, or something different?