Local networks¶
Where: Connectivity > Interfaces & network > Local networks tab.
Each LAN is shown with its address, the addresses handed out, and its way to the internet, on one page rather than across Interfaces, DHCP and NAT.
A network is not a port¶
A local network owns its address, its DHCP range and its firewall rules. Ports are attached to it. A network with nothing attached keeps its address and DHCP scope and shows nothing attached under Reachable on — a valid state, not a fault.
So you can create a network before the cabling exists, move it between ports without its address or rules changing, and put several ports on one network.
Adding a LAN¶
Click Add a LAN:
| Field | Meaning |
|---|---|
| Name | What you call it — Office, Workshop, Tills… |
| Port | Where to start it; can be changed later |
| Network | This device's address on the LAN with its prefix, e.g. 192.168.2.1/24. Clients get addresses from the same range |
| Leaves by | The uplink this network is translated out of |
| DNS for clients | Resolvers handed out. This device only answers DNS when web filtering is on, so an external resolver is the default |
| What this network is for | Optional role (Guest, Connected equipment (IoT), Telephony (VoIP), DMZ, Servers), so a shared rule set can say "guest" instead of naming a port |
Click Create. This sets the address, the DHCP range, the outbound translation and the firewall rules, and turns on routing. Then apply and confirm.
The same form is available as + Add Interface > LAN on the Interfaces & network tab.
Each network in the list¶
| Column | Meaning |
|---|---|
| Network | The device's address and prefix |
| Addresses handed out | The DHCP pool, or None — static only |
| Leaves by | The uplink it is translated out of |
| Reachable on | The attached ports |
Nothing translates this network to the internet
Clients get an address and reach nothing: the outbound NAT rule is missing. See Outbound NAT.
Editing¶
Edit changes the network, Hand out addresses and the Address pool. Changing the network moves the port address, the DHCP pool, the router given to clients and the outbound translation together. Reservations that fall outside a new network are listed and removed.
Attaching ports¶
Attach ports opens Ports on this network:
- Attached — ports on the network; Detach removes one without touching the address or DHCP scope.
- Available — free ports; Attach adds one.
- Ports with their own network — ports that already carry an address. Add a VLAN puts this network on a tagged VLAN over that port instead, and the port keeps its address. The equipment on that port must then send this network on the shown tag.
Allowing more ports¶
A network whose address sits directly on a port can only be reached there. Allow more ports moves the address onto its own interface and bridges the port to it; the address, DHCP range and rules do not change. Click Convert, then apply and confirm.
This re-addresses a network in use: if you are connected through it, you lose the portal until it settles, and the device restores the previous configuration if you do not confirm. It is refused while the device is offline.
Networks built by hand¶
A network built directly on the Interfaces & network and DHCP tabs appears marked not managed here. Edit it on those tabs.
Removing a network¶
Removing a network deletes its address, DHCP scope, translation and firewall rules. Anything plugged into its port loses its network.
Related¶
- DHCP
- VLANs
- Outbound NAT
- Integrations — building a whole network from a role