Set Up a LAN for Field Operations

Build a reliable local network for your Field Day site so every station can reach Field Day Commander.

How-To Guides › LAN Setup

What You Need

Field Day Commander runs on your local network. Every device that needs to log contacts, view scores, or sign the guestbook connects to the same LAN. You don't need an internet connection.

  • A Wi-Fi router. A cheap home router works fine.
  • The server running Field Day Commander (a Raspberry Pi, laptop, or any Linux box).
  • Client devices with a web browser (laptops, tablets, phones).
  • An ethernet cable to connect the server to the router.

Setting It Up

1 Power on the router. Leave the WAN/internet port empty. You don't need upstream connectivity.

2 Plug the Field Day Commander server into a LAN port on the router with an ethernet cable.

3 Connect client devices to the router's Wi-Fi network.

4 Open a browser on any client and use the hostname configured during installation. If you deployed with an IP address instead, use that IP. The installation guide explains how to verify the address.

That's the whole setup. The router handles DHCP (assigning IP addresses) and Wi-Fi. The server runs Field Day Commander. Clients open a browser and connect.

Give the Server a Static IP

Your router hands out IP addresses automatically, but the server's address could change if it reboots. Give it a fixed address so every browser tab pointed at it keeps working.

The easiest way is a DHCP reservation. Log into your router's admin page and assign a fixed IP to the server's MAC address. The server still gets its address from the router, but the router always gives it the same one. Most routers support this under a "DHCP reservation" or "address reservation" setting.

If your router doesn't support reservations, you can set a static IP on the server itself. On Raspberry Pi OS, or any other system that uses NetworkManager:

On the serverTerminal or SSH session
# Find the active NetworkManager connection name
nmcli connection show --active

# Set a static IP
sudo nmcli con mod "Wired connection 1" \
  ipv4.addresses 192.168.1.50/24 \
  ipv4.gateway 192.168.1.1 \
  ipv4.method manual

# Apply the change
sudo nmcli con up "Wired connection 1"

Replace Wired connection 1 in both commands with the connection name shown in the NAME column. This is the NetworkManager connection name, which may differ from the interface name, such as eth0. See NetworkManager’s nmcli examples for connection profiles and manual IP settings.

Pick an address outside your router's DHCP range so it won't conflict with automatically assigned addresses. Check your router's admin page to see what range it uses.

Accessing Field Day Commander

Clients reach Field Day Commander at the address you gave the deploy script with --domain. That option does not rename the device or create a hostname. Prefer a hostname that resolves from your station devices, using mDNS or your local DNS. Verify it before deploying; Choose and Verify Your Server’s Hostname walks through this. If hostname resolution cannot be set up, the server’s actual LAN IP is a fallback. Find it with hostname -I on the server. If you deployed with the IP, that's http://192.168.1.50 (or whatever address you chose). The server only answers to that name, so a browser pointed at a different hostname or IP for the same machine will get a blank page. If you change the address later, re-run the deploy script with the new --domain.

Browsers only need the web port. Live updates on the dashboards travel over the same connection, so there's no second port to open or remember.

If you're running Field Day Commander on a Raspberry Pi, mDNS may already be working, which means devices can reach it by hostname without knowing the IP. Check the device name with hostname on the server. If you followed Prepare a Raspberry Pi and actually named it fd-commander, deploying with --domain fd-commander.local lets everyone use http://fd-commander.local. Some clients may not resolve .local names. Test the devices your operators will bring; use local DNS if needed, or deploy with a fixed LAN IP as a fallback.

Tip

Write the server's address on a piece of paper and tape it to the table at each station. Simple works.

Wi-Fi Tips

Wi-Fi at a Field Day site is fighting against HF transmitters, generators, and whatever else is producing RF. A few things help:

  • Use 5 GHz if you can. It's less congested and less susceptible to interference than 2.4 GHz.
  • Keep the router central and elevated. Don't bury it behind a generator or under a table.
  • Use a simple SSID and password. You'll be telling people what they are all day. Something like FieldDay with a short password works.
  • Bring a spare ethernet cable. If Wi-Fi gets flaky, plugging a laptop directly into the router keeps that station running.

Test It First

Set everything up at home before Field Day and make sure it works:

1 Power on the router and server. Wait for Field Day Commander to start.

2 Connect a phone or laptop to the Wi-Fi.

3 Open a browser and go to the server's address. You should see the login page.

4 Try a second device. Log a test contact from each and make sure they both see it.

Watch out

If you're using a Raspberry Pi, make sure it has a reliable power supply. A Pi that loses power under load can corrupt its SD card or interrupt logging.

Quick Reference

Fill this in before you leave the house and bring it to the site:

Router SSID: _______________

Wi-Fi Password: _______________

Server IP: _______________

Router Admin: _______________