Weft Start free trial

Blog

Blog

Practical guides to building and running a network on WireGuard. A new one every week. Subscribe by RSS.

Guide · · 5 min read

Ask the demo network a question

The demo console now has Ask Weft: ask it why a site is slower or who can reach the servers, and it answers from the demo's own data. We also tried to talk it into changing things.

Read it →

Guide · · 4 min read

Applications: say who may use what, not who is on which network

Describe the systems your people use as applications: where each one lives, by address or by name, and on which ports. Then say which groups may use it. Everyone else is kept out, a group change in Entra or a device that fails a health check takes access away within minutes, and every application shows who used it.

Read it →

Feature · · 3 min read

Your laptop in the office, with the same rules as at home

Most office networks decide who you are by the socket you plug into. The Weft app now notices when it is behind one of your offices and tunnels to that office's box, so a person keeps their own groups and unlocks at their desk. About ten seconds to move, either way.

Read it →

Guide · · 3 min read

Make your sensitive applications ask for a fresh sign-in

Being in the right group is enough for most systems. For payroll or board reporting it shouldn't be. Weft can now make a device unlock an application with a fresh sign-in, your organisation's sign-in and Weft's code, before it can reach it, for as long as you choose.

Read it →

Guide · · 4 min read

Sign in with your own Microsoft Entra ID, and let its groups decide who reaches what

Connect Microsoft Entra ID to Weft in four steps. Your people sign in with their work accounts, your Entra groups set their console role and can be used in network policy, multi-factor stays your own Conditional Access policy, and a test sign-in shows exactly what comes back before anything goes live.

Read it →

Guide · · 4 min read

Ask for a code at every sign-in, and have laptops sign in again every few hours

Turn on Weft's own sign-in code for people who sign in with their work account, and choose how long a laptop stays connected before its owner signs in again: eight hours unless you say otherwise. Two settings, and what your people see on each device.

Read it →

Guide · · 2 min read

See what your network policy blocked, and allow it in one click

Deny-by-default policy is right, and silent when it bites. Weft's policy page now lists the flows the policy refused, grouped the way you think, with an Allow this button that fills in the rule. Shown on a real network.

Read it →

Guide · · 2 min read

Your Weft sites in your own Grafana

Weft exports every site's health, link latency and loss, traffic and alerts in the format Prometheus reads. One read-only secret, one scrape job, and the numbers sit beside everything else you watch. Tested with a real Prometheus and Grafana.

Read it →

Guide · · 4 min read

Launch a Weft site in your own AWS account, with one line or two

Add a site, choose AWS, and a filled-in CloudFormation form opens in your account. Tick one box and the site gets a second internet line from first boot. We timed it.

Read it →

Guide · · 4 min read

Launch a Weft site in your own Azure subscription

Add a site, choose Azure, paste three values into the Azure portal. We tried it in a brand-new subscription and wrote down everything that got in the way.

Read it →

Guide · · 6 min read

Two internet lines, and Teams keeps working

When an office's line fails, Weft now moves Teams, Zoom and the rest of its local breakout to the other line within two seconds, and lets you choose which line each service prefers.

Read it →

Guide · · 6 min read

Find any device by name, from any office

Office B could reach the file server at 192.168.50.20, but not as "fileserver". Weft now gives every device in your organisation a name that works from every site, including offices that share an address range, and offices that run their own DNS. Here is how it works, and how we tested it.

Read it →

Guide · · 4 min read

Look round a working Weft console without signing up

One click opens the console of a made-up company with four sites, six devices and a day of traffic. No account and nothing to install. Look at almost anything; change nothing.

Read it →

News · · 4 min read

Weft now supports Ubuntu 26.04

Weft sites now run on Ubuntu 24.04 or 26.04 LTS. What changes in 26.04 for a router, how we tested it, the two FRR 10.5 problems we found and fixed on the way, and how to move an existing site.

Read it →

Guide · · 4 min read

Two-factor sign-in, and a sign-in page that looks like Weft

You can now ask for a six-digit code from an authenticator app after your password. Turning it on or off needs a fresh sign-in, so an unlocked computer is not enough. The sign-in page now carries Weft's colours and logo.

Read it →

Guide · · 3 min read

One sign-in for every customer network you look after

For IT providers: create a customer's organisation yourself or be invited into theirs, and move between them from one sign-in. Each customer stays its own organisation, and we tested that the walls hold.

Read it →

Guide · · 4 min read

Reach a camera recorder or a small server from outside, safely

Port forwarding, done the careful way: you must say who can connect, the page says where to connect, and we tested what happens when it goes wrong as well as when it goes right.

Read it →

Guide · · 4 min read

See every site and device, and cut one off in about a second

Every site and device in one view, then quarantine one or remove it. We measured how long that really took. It was nearly three minutes, so we changed it. Now it is about a second, including connections already open.

Read it →

Guide · · 5 min read

Where your internet leaves, and what gets translated on the way

Every network has to answer two questions: where does internet traffic leave, and who translates the addresses? The console now answers both in one place, including a to-do list for your firewall that we tested by following it word for word.

Read it →

Guide · · 5 min read

Run a Weft site in Docker or on Proxmox

Already have a server that runs containers? A Weft site can live there, as one Docker container or a Proxmox container, without touching the host's own network. We ran both, joined them to an office, and sent traffic between them.

Read it →

Guide · · 5 min read

Which box for which office: a buyer's guide to Weft hardware

Weft runs on any small machine with Ubuntu 24.04 or 26.04, so the box is your choice. How many ports each size of office needs, how much CPU WireGuard wants, and a look at one Amazon brand, ANDAQI — which we have not yet tested ourselves.

Read it →

Guide · · 3 min read

Keep the guest network away from your servers

Staff and guests on separate LANs at the same office, a server at another, and one rule: staff may reach it, guests may not. Built from the LANs themselves, so it keeps working when addresses change. Tested from both sides.

Read it →

Guide · · 3 min read

Reach the network behind your office router

The CCTV, building controls or lab network sits behind a router on the office LAN, and the other offices cannot see it. One route in the console fixes that, with no OSPF or BGP to set up. Tested: the branch reached it in under a minute.

Read it →

Guide · · 4 min read

One cable, every network: VLANs on your Weft box

Staff, guests and phones on separate networks, all on one port to the switch. Each VLAN becomes its own LAN with its own addresses, reachable from the other offices. And if the switch sends a VLAN nobody set up, Weft says so.

Read it →

Guide · · 3 min read

How big an AWS instance does a Weft site need?

We measured WireGuard between pairs of AWS instances from t4g.small to c7i.xlarge. Every one bursts to gigabits; what matters is what it holds for hours. A t4g.small ran at 2.77 Gbit/s for ten minutes, then fell to 0.12.

Read it →

Guide · · 5 min read

Two clouds and the office, with static routes both ways

An office, an app in one AWS region and its database in another, all joined with no VPN gateways and no peering. Two kinds of static route make it work: Weft's, to the servers, and each cloud's, back again. Tested, including what happens without the second kind.

Read it →

Guide · · 4 min read

Send every office's internet through head office's firewall

One firewall to filter, log and present a single address for every office. Point Weft at it, and a branch with no internet of its own comes out of head office's. Tested, with the one step that is easy to miss.

Read it →

Guide · · 3 min read

Your cloud VPC as just another office

Put a small Weft box in your AWS VPC and the private servers there become reachable from the office and from laptops, with no VPN gateway, no public addresses on the servers, and two route-table entries. Tested.

Read it →

Guide · · 3 min read

Give a contractor one server and nothing else

Deny by default, then allow exactly what is needed: a contractor's laptop that reaches the billing server and is refused everything else on the network. Three groups-and-rules steps, tested from the laptop.

Read it →

Guide · · 3 min read

Three offices on three continents

London, New York and Singapore joined with one command each: the real round-trip times, why the offices talk directly, where to put your hubs, and what remote staff see when one office goes dark.

Read it →

Guide · · 4 min read

Let Microsoft 365 leave every office directly

Send the branch's internet through head office's firewall, but let Outlook, SharePoint and Teams go straight out of the branch's own line, as Microsoft recommends. Three tick boxes, and the firewall's own counter to prove it.

Read it →

Guide · · 4 min read

Two head offices, and each branch uses the nearer one

With a firewall in London and another in Virginia, a branch in Virginia should not reach the internet through London. One setting makes each office use the nearest: a web request went from 0.465 s to 0.040 s, and when the near one failed, traffic moved to the far one within about a minute.

Read it →

Guide · · 4 min read

Reach the printer at the other office

Put each office's own network behind its Weft box, so a PC in one office and a laptop at home can both reach a printer in the other. Real test, with timings.

Read it →

Guide · · 4 min read

Add a second office, then pull the plug on the first

Join a second office to the first with one command, make it a standby hub, and watch what remote staff experience when the first office's box loses power. Timed, with screenshots.

Read it →

Guide · · 3 min read

Two internet lines, and not one dropped request

Give an office a second internet line and Weft runs a tunnel over each. We cut line 1 while a PC asked the other office for a page every two seconds: sixty requests, none failed.

Read it →

Guide · · 6 min read

Turn a small box in your office into a WireGuard concentrator

One Ubuntu machine becomes the place your laptops connect to, with the office's internet line as their way out. Nine steps from a bare box to a connected device, with screenshots.

Read it →