Reach LAN devices without an agent through NetBird

These steps route your home LAN over NetBird to reach the devices that run no agent, such as a printer or a NAS admin page. A client away from home then opens each one at its own LAN address. The mainland edition has no NetBird; its route page is the EasyTier one.

Before you start, check these:

• The hub has joined NetBird, as Join the hub to NetBird describes, and a client reaches the hub through NetBird.
• The hub runs in router or side gateway mode, as Make the hub a router or side gateway describes.
• You are an administrator of the NetBird account in its console.

Read the subnets the hub serves

1. In the panel, open the Access page.
2. Select the NetBird card.
3. Under LAN routes, select the subnet that holds the device's address, such as 192.168.10.0/24 for a printer at 192.168.10.20. The panel copies the subnet.

Add the subnet as a resource

The console's Add Network wizard asks for the network, its resource, a policy, then the routing peer, and the next three sections follow it.

1. In the NetBird console, open Network Routing > Networks.
2. Select Add Network.
3. Type a Name for the network, then continue to Add Resource.
4. Type a Name for the resource.
5. Paste the subnet into Address.
6. Continue to the access control step.

Allow the clients' group

Every client of the hub joins NetBird with the hub's setup key, so it is in the group that key assigns. The Setup Keys list shows that group in the key's Groups column.

1. In the access control step, select Add Policy.
2. Set the source to the group your setup key assigns.
3. Set the destination to the resource you added.
4. Set the protocol to All.
5. Select Continue.
6. Select Submit.

Make the hub a routing peer

1. In Add Routing Peer, pick the hub's peer from the list. Leave Install NetBird alone.
2. Select Continue.
3. Select Submit.

The network's page lists its resource, its routing peer and its policy.

Check from a client

In the desktop client or the Android app, away from home:

1. On the Hubs page, find the virtual network line under the hub's row.
2. If the line reads Not connected, select Connect. A line that was already connected takes the new route itself.
3. In a browser, open the device's LAN address, such as http://192.168.10.20.

When the device stays unreachable

If the virtual network line reads Connected · with an address and the device does not answer, check the policy in Allow the clients' group. A red line on the Access page names a route problem, and Troubleshooting has its fix.