exitnode.guide A guide by Firezone

Exit nodes and what they cost you

An exit node is a device that sends all the internet traffic of other devices out through its own connection. It protects you on public Wi-Fi and gives you a fixed egress IP. This guide explains how an exit node works and where one node is not sufficient.

See the Firezone full tunnelBook a demo

How an exit node carries internet trafficA laptop on public Wi-Fi sends all its traffic through an encrypted tunnel. The tunnel passes through the Wi-Fi hotspot, where an eavesdropper on the same network cannot read it. The exit node on a network that you trust decrypts the traffic and forwards it to a website. The website sees the address of the exit node. A second exit node is optional and gives failover.Public Wi-FiNetwork you trustInternettunneltunnelcannot readforwardLaptopsends all trafficWi-Fi hotspotsees encrypted dataEavesdroppersame Wi-Fi networkExit nodedecrypts and forwardsSecond exit nodeoptional, for failoverWebsitesees the node address
  1. The laptop sends all traffic

    The default route of the laptop points into the tunnel, so each packet for the internet goes to the exit node.

  2. The local network sees a tunnel

    The hotspot and the other people on it see encrypted packets to one address, and nothing more.

  3. The exit node forwards

    The exit node decrypts each packet, replaces the source address with its own, and sends the packet on.

  4. The website sees the node

    The website sees the public address of the exit node, not the address of the Wi-Fi network.

What an exit node is

An exit node is a device on a private overlay network that forwards the internet traffic of other devices. The other devices send all their traffic to it through an encrypted tunnel. The traffic then leaves for the internet from the connection of the exit node.

"Exit node" is the term that mesh VPN products use. The same idea has other names. A legacy VPN calls it a full tunnel, and a consumer VPN calls it a VPN server. The difference is who runs the machine. You run your own exit node, on a network that you select.

An exit node does not give access to private services. It changes only the path that internet traffic takes.

Why people use an exit node

  • Public Wi-Fi. The Wi-Fi in a hotel, an airport, or a coffee shop is shared with strangers. With an exit node, the local network sees only an encrypted tunnel. It cannot see which sites you visit, and it cannot change your DNS answers.
  • A fixed egress IP. Many SaaS products and partner firewalls accept traffic only from an approved list of addresses. When a team sends its traffic through one exit node, each person has the same egress IP.
  • A regional egress. Some services behave differently in each country. An exit node in a region lets a tester or a support engineer see the service as a local user sees it.
  • One place to monitor. All internet traffic passes one point, so a team can log it or filter it there.

How an exit node works

An exit node uses three mechanisms that are also in every home router.

The default route

The client replaces the default route of the device, 0.0.0.0/0 for IPv4 and ::/0 for IPv6. Each packet with no more specific route now goes into the tunnel.

Forwarding and NAT

The exit node has IP forwarding turned on, so it accepts packets that are for other destinations. It then replaces the source address of each packet with its own public address. Replies come back to the exit node, and the exit node sends them back through the tunnel.

DNS

DNS queries must also leave through the exit node, or through an encrypted resolver. If queries continue to go to the resolver of the local network, that network learns each name that you visit.

The limits of an exit node

One node is a bottleneck

Each device that uses the exit node shares its CPU and its uplink. A node on a home connection can serve a small number of people. A video call for a full team can fill it. One node is also one point of failure. If it stops, each user loses internet access until they select a different node.

You move the trust, you do not remove it

The exit node sees what the Wi-Fi network would have seen. It sees each destination address and all traffic that has no encryption of its own. An exit node is only as safe as the machine and the person who operates it.

Latency

Each packet goes to the exit node first, and then to its destination. If the exit node is far from the user, each request makes a long trip. A user in Singapore with an exit node in Virginia feels the delay on every page.

Access to the network of the node

An exit node in an office or a cloud network can usually reach the private hosts next to it. Make sure that internet traffic from remote users cannot reach those hosts through the node.

How to run exit nodes well

  1. Run more than one node. Put nodes near the places where your people work, and plan for the loss of one node.
  2. Size the node for the traffic. Internet traffic is much larger than traffic for private apps. Measure the peak, not the average.
  3. Keep private traffic on its own path. Traffic for a private app goes directly to that app, not through the exit node.
  4. Isolate the node. Give it a route to the internet and no route to private hosts.
  5. Decide who must use it. A contractor on a managed laptop and an engineer on a home network have different needs. Assign the exit node to groups, not to all people.
  6. Control DNS. Send queries to a resolver that you trust, and encrypt them where possible.

How Firezone does the job of an exit node

Firezone does not use the term exit node. The equivalent is the Internet Resource. It routes 0.0.0.0/0 and ::/0 through Gateways that you run in a special Site, the Internet Site.

  • The nearest healthy Gateway. Deploy Gateways in the regions where your people work. Each Client uses the nearest healthy Gateway, and it moves to a different one if that Gateway fails.
  • Private Resources keep their own path. A DNS, IP, or CIDR Resource is more specific than the Internet Resource, so it always takes priority. That traffic goes to the Gateway in its own Site.
  • The egress is isolated. Gateways in the Internet Site serve only the Internet Resource. They reject traffic for private address ranges, so internet access gives no path to private hosts.
  • A Policy decides who uses it. Give the Internet Resource to one Group, and add conditions if you need them.
  • Users keep control. A user can turn the Internet Resource off in the Client if it causes a problem. It is off by default when a user first gets access.

You select how each Client resolves public names. You can keep the resolver of each network, use a DNS over HTTPS provider, or use your own resolvers. See Configure DNS.

The Internet Resource is available on the Team plan and up. Firezone recommends a minimum of 4 CPU cores for each Gateway in the Internet Site. See the sizing guide.

A consumer VPN, a mesh VPN exit node, and Firezone

The three approaches all send internet traffic through a different machine. They differ in who runs that machine and in what occurs when it fails.

Consumer VPNMesh VPN exit nodeFirezone
Who runs the egress machineThe VPN providerYouYou, as Gateways in the Internet Site
The egress IP is yours onlyNoUsually shared with other customersYesYes
The user selects the egress locationYesYesNoThe Client uses the nearest healthy Gateway
Automatic failoverPartialThe user selects a different serverPartialThe user usually selects a different nodeYesThe Client moves to a healthy Gateway
Private apps keep their own pathNoNo private accessYesYesA more specific Resource takes priority
A rule for who can use itNoYesWith an access control listYesA Policy for a Group

The table describes the usual design of each category. A specific product can be different. Read the documentation of the product before you decide.

Common questions

What is an exit node?

An exit node is a device that forwards the internet traffic of other devices. The other devices send all their traffic to it through an encrypted tunnel. The traffic then leaves for the internet from the connection of the exit node.

Is an exit node the same as a VPN?

It does the same job as a full tunnel VPN or a consumer VPN server. The difference is that you run the exit node. You decide where it is, who can use it, and what it logs.

Does an exit node hide my IP address?

It replaces your address with the public address of the exit node. A website sees the node and not your local network. The operator of the exit node, and the network that the node is on, can still see your traffic.

Does an exit node make the internet slower?

Usually, yes. Each packet makes an extra trip to the exit node, and all users share the capacity of the node. The effect is small when the node is near you and has spare capacity.

Can I select a country for my traffic in Firezone?

No. The Client uses the nearest healthy Gateway in the Internet Site, and the user does not select one. You control the egress locations when you decide where to deploy Gateways.

Can I use a Firezone Gateway to get a fixed egress IP for one SaaS app?

Yes. You can route selected DNS Resources through a Gateway, so that the traffic leaves from the public IP of that Gateway. This does not need the Internet Resource. See the NAT Gateway guide.

Run your own egress, near each user

Firezone is zero trust access built on WireGuard. Deploy Gateways to the Internet Site, give the Internet Resource to a Group, and private Resources keep their own path.

See plans and pricingBook a demo