RLReadyLinks Docs

ReadyWall firewalls

What a ReadyWall firewall does, how it connects to ReadyView, and where each feature lives on the firewall's page in the dashboard.

ReadyWall is the ReadyLinks firewall family. Each firewall runs ReadyLinks firewall software, based on OPNsense, with the ReadyView agent built in. The agent connects the firewall to the ReadyView cloud dashboard. It reports the firewall's health and traffic, and it applies changes you make in ReadyView.

You can manage a ReadyWall in two places:

  • ReadyView (the cloud dashboard): day-to-day monitoring and the common settings, from anywhere, for every firewall in your organization.
  • The firewall's own web interface: everything ReadyView doesn't cover, and the settings that control what ReadyView may change.

#Where to find things

Open a firewall from Devices > Firewalls in your site's menu. Its page has six tabs. Every tab except Overview lists its sections down the side and shows one section at a time.

TabSectionsGuide
OverviewHealth, gateways, interfaces, WAN connectivity, live trafficMonitoring and reports
ActivitySecurity report, Live log, HistoryMonitoring and reports, Rules, NAT, and aliases
SecurityRules: Firewall rules, Port forwards and NAT, Aliases, Group policiesRules, NAT, and aliases
Protection: Threat protection, Blocklists, Regions, DNS filteringThreat protection
Organization: Fleet templatesThreat protection
NetworkLocal network: VLANs and DHCP, Leases and ARPNetworks and DHCP
Routing: Route table, Routes, Dynamic routingRouting
Internet: Uplinks, Speed limitsInternet uplinks
Access: Guest login pages, Client VPN, Site VPNGuest access and VPN
ToolsPing, traceroute and DNS; iperf server; Connections; Packet capture; Log filesTools
SettingsFirmware and restarts, Configuration backups, Warm spareFirmware, backups, and HA

Some sections need a newer ReadyView agent than others. When a firewall's agent is too old for a section, ReadyView hides that section or says the firewall needs an update. See Firmware, backups, and HA.

#How ReadyView talks to the firewall

The firewall always opens the connection, outbound to the ReadyView cloud. You don't need to open any inbound ports or give the firewall a public management address. It needs outbound TCP 8883 to mqtt.readylinks.io, plus DNS and NTP. See Firewall rules for cloud connectivity.

Over that connection:

  • the firewall reports its status every 15 seconds by default, and its traffic and WAN statistics every minute;
  • each time you open a section, ReadyView asks the firewall for that section's current settings. While it waits, it may show the last answer it saw, up to seven days old, with the time it was read. You can't edit until the firewall's own answer arrives, so a save never writes old values back;
  • each change you save is signed by ReadyView and checked by the firewall before it applies it.

If the firewall can't reach ReadyView after applying a change, it undoes the change on its own. A mistake made from ReadyView can't leave the firewall cut off from the dashboard. See How changes work.

#Start here

Edit this page on GitLab

Last updated October 29, 2026