https://paart.app/Recent content in WireGuard, built for the way I actually work on PaartHugoenLux-World PChttps://paart.app/client/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/client/https://paart.app/help/client/adding-a-connection/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/adding-a-connection/What you need A WireGuard configuration, issued by the server you want to reach — a router, a firewall, a home server, or a machine someone administers for you. Paart is a client: it cannot create one for you. It arrives in one of two shapes, and on the Mac you can also paste one straight in: A .conf file in standard wg-quick format. A file that works in another client works here.https://paart.app/help/managed/wireguard-from-opnsense/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/managed/wireguard-from-opnsense/The problem: WireGuard does not scale by hand WireGuard is small, fast and pleasant to run for one person. Running it for thirty is a different job. Every new user means generating a key pair, writing a peer block into the firewall configuration, assembling a client configuration, and getting it to the right device without emailing a private key. Every departure means finding that peer block again and removing it. Every replaced laptop means doing both.https://paart.app/faq/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/faq/https://paart.app/help/client/private-key/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/private-key/Most of a configuration is harmless — addresses, a hostname, a port. One line is not. PrivateKey proves your device is allowed on that network. It is not a password you can change casually: it is half of a key pair the server already knows. Treat it as you would a password Do not send it to anyone, us included. There is no situation in which Lux-World PC needs your private key, and we will never ask for it.https://paart.app/help/client/tunnel-will-not-connect/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/tunnel-will-not-connect/WireGuard is quiet by design: when it fails it does not say why, it simply never completes a handshake. The causes are few, and this is the order worth checking them in. 1. Your connection is not reachable from outside The most common cause of all, and it is not in your configuration. Many providers put customers behind shared IPv4, also called CGNAT: your router then has no address of its own on the internet, and nothing can open a connection towards it.https://paart.app/help/client/connected-but-no-traffic/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/connected-but-no-traffic/WireGuard says connected, or shows a successful handshake, but the resource you need still does not respond. Perhaps the remote LAN is unreachable, a service will not open, or Internet access stops when you enable the tunnel. Start by finding which part of the connection works. A tunnel can be enabled without exchanging useful traffic; a successful handshake does not prove that the remote gateway can reach your server or return its reply.https://paart.app/help/client/routing/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/routing/AllowedIPs is the routing decision Despite the name, AllowedIPs in [Peer] does two jobs: outbound it decides what gets routed into the tunnel, inbound it decides what the peer may send you. Value Effect 0.0.0.0/0, ::/0 Everything goes through the tunnel — a full tunnel. 10.0.0.0/24 Only that range goes through — a split tunnel. The rest uses your normal connection. Neither is more correct. A split tunnel reaches the office while leaving video calls on your own connection; a full tunnel sends everything to the far end, which is what you want when you trust it more than the local Wi-Fi.https://paart.app/help/client/split-dns/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/split-dns/On a Mac, a WireGuard configuration whose DNS = line names a server usually sends every name lookup to that server while the tunnel is up: the remote network’s names, and everything else. Split DNS is the alternative. A resolver is chosen for particular domains, and every other name keeps the DNS you normally use. Search domains are a third, separate mechanism: they complete short names, and they do not choose a resolver.https://paart.app/help/client/several-tunnels-at-once/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/several-tunnels-at-once/You can use multiple WireGuard tunnels on a Mac with a client or command-line setup that supports them. For both remote networks to work, the client must keep both tunnels active, macOS must send each destination through the right interface, and DNS must resolve each name correctly. This guide covers IPv4 networks. Two “Connected” indicators are not enough. Verify access to a real service on each network while both tunnels are active.https://paart.app/help/client/on-demand/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/help/client/on-demand/Why rules rather than a switch A VPN you have to remember to turn on is off precisely when it matters — on the café Wi-Fi you joined while reading something else. Rules move that decision from your memory to the device. One connection carries these rules at a time. Arming another moves them; it does not add a second set. What a rule can look at A specific Wi-Fi network, matched by name.https://paart.app/about/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/about/Paart is built by a small team in Luxembourg. Being small shapes the product. Paart connects to networks you already control, and we run none of them. There is no service behind the app, no traffic passing through anything we own, and no data to sell — because there is none to collect. The privacy policy says so in detail, and it is the same page Apple reads. How Paart is built The app is written for Apple’s own platforms — iPhone, iPad and Mac, as one universal purchase.https://paart.app/contact/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/contact/This reaches us directly. No account to create, no ticket number to keep. Leave an email address and we reply to it. Leave none and the message still arrives — we simply have no way to answer.https://paart.app/legal/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/legal/Lux-World PC S.à r.l. publishes this website and the Paart app. Publisher Company Lux-World PC S.à r.l. Registered office 50, rue des Artisans — L-3712 Rumelange — Luxembourg Trade and Companies Register RCS Luxembourg B72290 VAT number LU18119580 Business permit 90599C, issued by the Luxembourg ministry responsible for small and medium-sized enterprises Director of publication François Maymil Contact fm@lwpc.lu For anything about the app, the contact form reaches us faster than email.https://paart.app/managed/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/managed/https://paart.app/privacy/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/privacy/Lux-World PC publishes Paart. This page is short because there is little to say, and that is the point. We are not on the path Paart is a client. We operate no VPN server. The tunnel runs from your device to a network that is not ours, so there is no browsing history to keep, no lookup to log and no connection record to hand over — not as a policy we could change, but as a consequence of where the tunnel ends.https://paart.app/roadmap/Mon, 01 Jan 0001 00:00:00 +0000https://paart.app/roadmap/A date on a roadmap is a promise that goes stale without anyone noticing. A state is either true today or it is not. What we build after the first release is decided by what people ask for — which is why the last section below is a vote rather than a list of our own intentions.