Infrastructure

Networking

PagePoint runs as a standalone network with no dependency on customer IT infrastructure.

Current Direction

PPSM appliance owns DNS/DHCP through independent systemd services such as dnsmasq.
PPSM appliance owns site time through RTC-backed Linux time and chrony NTP service.
PPSM application configures, validates, monitors, and reports network services.
PPOE uses static or PPSM-reserved addressing and does not run network infrastructure services.
If a service must run continuously for PPOE to operate, it remains available even if the PPSM application restarts.
PPSM normal operation is wired-only on 192.168.50.2; Wi-Fi is retained only as an intentional emergency access path.
Applied state on physical SM: netplan-wlan0-PagePoint autoconnect disabled, wlan0 dormant, former Wi-Fi address 192.168.50.110 inactive.

Device / service	Address	Role
PPOE / OE	`192.168.50.1`	Operations engine, phone UI, audio runtime.
PPSM	`192.168.50.2`	DNS, DHCP, Android validation, NTP, Service Portal, touchscreen service workflows.
Phones	DHCP range	Operator devices provisioned to PagePoint Wi-Fi, PPOE UI, PPSM NTP, and DYY9 timezone.

The SM may keep a PagePoint Wi-Fi profile for recovery, but it should not autoconnect during normal operation.

Interface	Normal state	Purpose
PPSM Ethernet	Enabled, static `192.168.50.2`	Primary service identity for DNS/DHCP/validation/NTP, Service Portal, and touchscreen-backed workflows.
PPSM Wi-Fi	Profile retained, autoconnect disabled, currently dormant	Emergency technician access only when the wired service path is unavailable.

Enable PPSM Wi-Fi only as a deliberate service action.
Use the temporary DHCP address only long enough to restore service access.
Disable Wi-Fi again after recovery.
Do not depend on the PPSM Wi-Fi address for normal DNS, DHCP, NTP, portal, or provisioning workflows.

Dual-homing the PPSM can make local names such as pagepoint-ppsm.local resolve to the wrong interface.
Routing, mDNS, browser access, time service, and diagnostic results become ambiguous when the infrastructure appliance appears at two addresses.
The wired/static address remains the architecture target and the stable service identity.

Live DNS/DHCP ownership moved from PPOE to PPSM on 2026-07-06.
PPOE dnsmasq.service was disabled and inactive after cutover.
PPSM runs pagepoint-dnsmasq.service and pagepoint-validation.service.
PPSM DNS resolves pagepointheadend to 192.168.50.1 and pagepoint-ppsm to 192.168.50.2.
Android validation hostnames resolve to PPSM, where the validation responder returns HTTP 204.

UP: PagePoint network is functioning and Internet is reachable.
ISOLATED: PagePoint network is functioning as a standalone network without Internet.
WARN: Network is functioning but has a reported issue requiring review.
DOWN: Network or validation path is not functioning.
Android Validation SPOOF: Site-spoofed validation response is active for isolated PagePoint operation.

PagePoint uses standard Linux timekeeping. PPSM is the site time authority; OE and phones are NTP clients.

RTC hardware: DS3231 on GPIO SDA 21 / SCL 20 through i2c-rtc-gpio.
PPSM chrony is enabled and active.
PPSM chrony serves the PagePoint subnet with allow 192.168.50.0/24 and local fallback stratum 10.
OE systemd-timesyncd uses 192.168.50.2; verification showed OE synchronized with PPSM NTP.
Phones are provisioned with Android global ntp_server=192.168.50.2.
DYY9 phones are pinned to America/New_York with automatic timezone disabled so daylight-saving behavior comes from the IANA/Android timezone database, not from guessing the site location.