A captive portal sits between a newly connected client and normal internet access. The network gives the client local addressing, detects or redirects an unauthenticated web request, presents payment/login/session controls, then authorizes traffic according to the controller’s policy.
Digital-payment support is platform/integration specific. Verify the vending platform’s supported provider or API/QR workflow and test settlement before advertising GCash/Maya acceptance.
The customer portal starts/redeems sessions; the admin portal changes business/network settings. They may share a host/IP but must not be treated as the same permission level.
Use one clearly defined routing/controller layer and add access points for coverage. Avoid accidental double NAT or multiple DHCP servers unless the design intentionally requires them.
Explain WPS enrollment, its convenience and why PIN mode received security criticism.
Explain DNS updates, caching and reachability separately.
Explain automatic NAT mappings and the local trust model neutrally.
Explain why latency can spike under load and how shaping/queue management differs from simple priority labels.
Teach useful segmentation concepts without assuming enterprise-switch experience.
Explain Layer-2 addressing and why modern privacy features make MAC-based identity imperfect.
