Skip to content
Ömer Tiryaki (Home)
← All notes

Guidechecked

Building an office network

Router, switch, Wi-Fi, separate networks for guests and phones, and remote access via VPN. This is how I set up a small company network.

Take stock

Before a single cable is laid, the plan is set. For that you need a clear picture of what exists today and what will be added in the next few years. Skimp here and you will be replacing switches or pulling extra cable later.

  1. Count devices: workstations, laptops, printers, servers or NAS, phones, cameras, guest devices.
  2. Walk the rooms: where do people sit, where is Wi-Fi needed, where can a small network cabinet go?
  3. Check the internet line: download and upload bandwidth, static or changing IP address, the provider’s router.
  4. Plan for growth: roughly a third more ports and addresses than you need today.

Choosing hardware

For separate networks every device must support VLANs according to IEEE 802.1Q. A typical home router usually cannot do this. It then stays in front of a proper firewall as a modem, for example OPNsense or a Ubiquiti gateway.

  1. Firewall or router with VLANs, VPN and regular updates.
  2. Managed switch with PoE. Access points usually need PoE+ (802.3at, up to 30 W per port). Check the switch’s total PoE budget.
  3. Ceiling-mounted access points instead of one strong router in the cabinet.
  4. Cabling with Cat 6 or Cat 6A, all wall sockets on a patch panel. Cat 6 carries 10 Gbit/s only up to about 55 m, Cat 6A over the full 100 m.
  5. A UPS for the firewall, switch and phone system, so a short power cut does not restart everything.

IP plan and VLANs

Each group of devices gets its own VLAN with its own address range. This lets the firewall decide between networks who may talk to whom. A guest with an infected laptop then never even sees the accounting systems. Servers, printers and the phone system get fixed addresses; everything else uses DHCP.

VLAN 10  Office     192.168.10.0/24
VLAN 20  Guests     192.168.20.0/24   internet only
VLAN 30  Phones     192.168.30.0/24

Fixed addresses: .2 to .49   DHCP: .50 to .250

Tip:Pick ranges that are rare in home networks. Many home routers use 192.168.0.x or 192.168.1.x, the FRITZ!Box uses 192.168.178.x. If the office uses the same range as someone’s home network, the laptop cannot reach the server over the VPN.

DHCP, fixed addresses and DNS

Exactly one DHCP server hands out addresses per VLAN, usually the firewall. Devices that others need to find get a reservation: the DHCP server always gives them the same address based on their MAC address. This is cleaner than an address typed into the device, because everything lives in one place. For DNS every device asks the firewall, which resolves local names itself and forwards the rest to an external resolver. That way you reach the printer as drucker.intern.example.de instead of a number.

Reservations in the office network (example)
192.168.10.1    firewall     gateway, DNS, DHCP
192.168.10.5    nas          file storage
192.168.10.20   drucker      floor printer

Local zone: intern.example.de
Forwarding: an external DNS resolver of your choice

Caution:Do not use the .local suffix, it is reserved for mDNS. A subdomain of your own domain is better, or .internal, which ICANN has reserved for private networks.

Configuring the switch

A port is either an access port or a trunk. An access port connects an end device that knows nothing about VLANs; it runs untagged in its assigned VLAN. A trunk carries several VLANs at once, and every packet gets a tag with the VLAN number. You need trunks to the firewall and to the access points, because several networks share one cable there.

Port   Mode     untagged   tagged    Device
1-16   Access   10         -         Workstations
17-20  Access   30         -         Phones
21-23  Trunk    10         20, 30    Access points
24     Trunk    10         20, 30    Uplink to firewall

Tip:Label the patch panel, wall sockets and switch ports the same way, for example “R2-05” for room 2, socket 5. Disable unused ports or put them in an empty VLAN.

Setting up Wi-Fi

Every Wi-Fi network (SSID) is mapped to a VLAN: the office Wi-Fi to the office network, the guest Wi-Fi to the guest network. Stick to two or three SSIDs, because each extra one costs airtime. Radio is a shared medium, so planning channels and transmit power matters more than the top speed on the box.

  1. Encryption WPA3-Personal. If there are older devices, use the WPA2/WPA3 mixed mode until they are replaced.
  2. Enable client isolation on the guest Wi-Fi so guests cannot see each other.
  3. In the 2.4 GHz band use only channels 1, 6 and 11 so neighbouring access points do not overlap. In the 5 GHz band a 40 MHz channel width is usually enough in offices.
  4. Lower the transmit power rather than setting it to maximum. Otherwise devices cling to a distant access point instead of moving to the nearest one.

Firewall rules

The basic rule is: everything not explicitly allowed is denied. The firewall checks the rules from top to bottom and applies the first one that matches. Specific rules therefore go at the top, the block for everything else at the very bottom.

Source      Destination             Service          Action
Guests      Firewall                DNS, DHCP        allow
Guests      Office, phones, admin   all              block
Guests      Internet                all              allow
Phones      Phone system            SIP, RTP         allow
Phones      SIP provider            SIP, RTP         allow
Office      Phone system            HTTPS            allow
Office      Internet                all              allow
VPN         Office                  as needed        allow
any         any                     all              block

Tip:Test every rule from the network in question: put a laptop on the guest Wi-Fi, then try to open the printer or the firewall’s admin page. Both must fail.

Telephony

IP phones get their own VLAN so voice does not fight file downloads for bandwidth and the firewall can control the traffic precisely. A call with the G.711 codec needs about 100 kbit/s in each direction. The bottleneck is almost always the upload of the internet line. QoS only helps if the firewall knows the line: enter download and upload slightly below the real values and prioritise voice packets marked DSCP EF.

  1. Power the phones via PoE, then they keep running on the UPS.
  2. Turn off SIP ALG on the router and firewall. It rewrites SIP packets and often causes one-way audio or dropped calls.
  3. Open the ports listed in the phone system’s and SIP provider’s documentation, do not guess. With 3CX the built-in firewall checker shows whether everything is right.

Remote access via VPN

Access from outside only goes through a VPN, for example WireGuard. Every person gets their own access that can be revoked individually. Opening server ports directly to the internet is off limits. The VPN gets its own network so you can define in the firewall exactly what VPN users can reach.

[Interface]
PrivateKey = <LAPTOP-PRIVATE-KEY>
Address = 192.168.99.2/32
DNS = 192.168.10.1

[Peer]
PublicKey = <FIREWALL-PUBLIC-KEY>
Endpoint = vpn.example.com:51820
AllowedIPs = 192.168.10.0/24
PersistentKeepalive = 25

Caution:WireGuard itself has no multi-factor login. The private key is the access. Protect it with disk encryption and a screen lock, and use MFA wherever the firewall or remote access solution offers it.

Securing and maintaining

A network is not finished once it is built. Firmware gets security holes, configurations change, and without logs you will not know what happened when something breaks. The NET layer modules in the BSI IT-Grundschutz Compendium are a good reference.

  1. Every device with its own long admin password. Management only from the office network or via VPN, never from the internet.
  2. Install firmware updates on a fixed schedule, critical vulnerabilities immediately.
  3. After every change, export the firewall and switch configuration and store it outside the devices.
  4. Send logs to a central syslog server and sync every device’s clock via NTP, otherwise the entries will not line up.

Document it

Network plan, addresses, VLANs and port assignments go into documentation, passwords into a password manager. That way someone else can take over the network too.

Tip:Also record the internet provider login, contract numbers and support contacts. Otherwise, during an outage, someone ends up hunting for the right hotline.

Common mistakes

Most problems in small networks come down to a few recurring causes. When something does not work, check this list first.

  1. Double NAT: the provider’s router and the firewall both translate addresses. VPN and telephony suffer. Fix: put the provider router into modem or bridge mode, or set the firewall as its exposed host.
  2. Wrong VLAN tagging: an access point is connected to an access port instead of a trunk. Then only one Wi-Fi works and the others get no address.
  3. DHCP conflicts: the provider router still hands out addresses itself, or a fixed address lies inside the DHCP range. Devices then drop off at random.
  4. Guests see the printer: the printer is in the wrong VLAN, or a rule allows too much. Also check whether the firewall relays mDNS between networks.

Order and checklist

The order I follow. Each step is tested before the next one starts.

  1. Set up the router or firewall, update the firmware, change the admin password.
  2. Create VLANs, DHCP ranges, reservations and local DNS names.
  3. Assign switch ports: workstations untagged in the office network, access points and uplinks tagged.
  4. Set up Wi-Fi with WPA3, a separate guest Wi-Fi in the guest network, devices isolated from each other.
  5. Set firewall rules: guests only to the internet, phones only to the phone system and the provider.
  6. Create one VPN access per person and test it from outside, for example over the mobile network.
  7. Back up the configuration, update the documentation, put the next update date in the calendar.

More notes

Privacy

No tracking cookies

Nothing about you is collected here.

What your browser remembers

None of it is used for analytics.

Read the privacy policy