wg-meshconf
wgsd
wg-meshconf | wgsd | |
---|---|---|
6 | 8 | |
882 | 765 | |
- | - | |
0.0 | 2.8 | |
21 days ago | 4 months ago | |
Python | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wg-meshconf
- Wireguard mesh between 4 pc similar to Tailscale
-
Updated MinIO NVMe Benchmarks: 2.6Tpbs on Get and 1.6 on Put
my experience, i dont know if this is comparable, but from my memory (i have not made any notes on that), i've tried min.io in december and switched to seaweed a weeks ago, because my usecase was transition from local file storage to DFS + also enable our developers to transition from local filesystem to s3. Since my resources are limited (vsphere VM) with 3 hosts + different disks, i tried to set up a 3 vm cluster with minio first, after i did some research on different systems (ceph, longhorn.io, ..) i wanted to have an easy setup-able system, which supports s3. I relied a lot on what people measured and chose min.io first because it supported mount via s3. Then i tried to copy over about 34 million files (mostly few bytes, but can also be 1Gbyte), with a mass of about 4.2TB. I tried different methods, rsync, cp, cp with parallelism,.. and i took me about 3 days to copy over 300GB of data at best. Then i also found out that it was impossible to list files. We have one single folder with over 300k projects (guid) beneath (growing). After that i gave seaweed a shot. Why i did not used it firsthand was documentation was a bit confusing and it did not gave me all the answers i needed as fast as minio did.
Now, my seaweed setup is a 3 vm cluster with 3 disks per vm (1TB) each. I configured a wireguard mesh (https://github.com/k4yt3x/wg-meshconf) between the VMs and configured master and volumes server to talk to each other via wireguard IPs securely. I also configured ufw to only allow communication between http/gRPC ports. I also configured a filer (using leveldb3) to use wireguard IPs (master and volumes) and let it communicate with some specific servers on the outside (ufw).
After that i mounted the filer via weed.mount on that specific server and tried to copy over the same files/folders. after 2 days i copied over about 1.5 TB of the data via rsync. There was also no problem with file listing and accessing the filer from different machines while uploading stuff. But there is a overhead when reading and creating lots of small files. File listing is even faster than local btrfs file listing.
chris is also very nice and fast fixing bugs.
-
Connect to wireguard server over a wireguard server -> client connection
Hey you should post your wg0.conf If you would like to build a WireGuard mesh try this: https://github.com/k4yt3x/wg-meshconf
-
How to add new client to wireguard in VPS without getting public IP changed on the client?
There are two factors at play here. The client's public IP actually depends on the gateway they use on accessing the internet. You can disable routing and your clients will keep their public IP and general internet access won't go through the VPS. However, if you want the traffic between "clients" also skip the VPS, then you want a mesh network. wesher and wg-meshconf can help you on configuring them.
-
Wiretrustee: WireGuard-Based Mesh Network
Looks great!
I've been using wg-meshconf[1] to assist in setting up Wireguard Mesh Networks on Linux for a while, works amazing!
A massive use case is to setup Kubernetes clusters, where network encryption is extremely important.
[1]: https://github.com/k4yt3x/wg-meshconf
- WireGuard full mesh configuration generator
wgsd
-
Mesh VPN - WireGuard admin
if your looking at setting up coredns aswell then i would highly suggest checking out wgsd https://github.com/jwhited/wgsd
- DNS System for storing WireGuard IPs
-
CVE-2022-41924 – tailscaled can be used to remotely execute code
https://github.com/jwhited/wgsd does NAT traversal with Wireguard, but you need to operate a CoreDNS server to do it.
More info on how it works: https://www.jordanwhited.com/posts/wireguard-endpoint-discov...
-
For CGNAT peers - is there an alternative which is open source and as simple to use as Tailscale?
Another one which looks promising is wgsd, a dns like plugin to discover peer's endpoints that sit behind a NAT. For me this is part of the solution, however not a complete one, as my client devices are also on Android and Android TV.
-
Wireguard with holepunching and DNS
that guide is literally someone promoting their CoreDNS plugin, so I'm confused as to what you mean: https://github.com/jwhited/wgsd
- Wiretrustee: WireGuard-Based Mesh Network
-
traceroute between two clients, server is always in the middle
If they are behind a NAT that you can't do port-forwarding on then you may need to run some additional software like https://github.com/jwhited/wgsd so 10.10.0.2 and 10.10.0.3 know where to look for each other by asking 10.10.0.1
-
Yet Another Mesh Overlay Tool
Our current implementation just has the nodes configured with PersistentKeepAlive by default, which works well enough for our small setup. In future iterations our plan is to incorporate another service. Our inclination is to use WGSD: https://github.com/jwhited/wgsd
What are some alternatives?
wesher - wireguard overlay mesh network manager
Netmaker - Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
headscale - An open source, self-hosted implementation of the Tailscale control server
tinc - a VPN daemon
innernet - A private network system that uses WireGuard under the hood.
cjdns - An encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing.
netbird - Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls.
wireproxy - Wireguard client that exposes itself as a socks5 proxy