https://paart.app/help/client/Recent content in The client on PaartHugoenLux-World PChttps://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/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/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/The problem: one resolver for the whole machine A WireGuard configuration names a single resolver on its DNS line, and while the tunnel is up the system uses it. That is fine when the tunnel is the only network you care about. It stops being fine the moment you still need your own. Reaching server.customer.local over HTTPS means that name has to resolve — and it only exists on the customer’s DNS.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/The problem this solves You need a server at one customer while you are working on the network of another, and you would rather not lose your own local network in the process. With one tunnel at a time, that is three disconnections and three reconnections. Every switch costs a handshake, and anything you had open on the first network drops. What a Mac can do On a Mac, Paart can hold several WireGuard connections up at the same time.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.