PPPoE vs hotspot vs DHCP/IPoE for small ISPs and WISPs
Choose an access model around who pays, how they connect, and how support proves service is restored. Compare residential fixed wireless, public Wi-Fi and FTTH.
Match access to the service
For a small WISP, the useful first question is who owns the connection. A home usually buys a recurring service for one site. A visitor buys access for a session or period. An FTTH customer may connect through a bridged ONT and a separate router. Those arrangements need different identity and support checks.
If you already know your access model, review the PPPoE billing scope or hotspot billing scope. Both describe ISPAgents guided-pilot boundaries separately from the network design below.
Choose by service, not by radio or fibre
| Access model | Where it often fits | Identity to retain | Operational tradeoff |
|---|---|---|---|
| PPPoE | Residential fixed wireless; FTTH where the customer router or ONT terminates PPP | Customer and service ID, PPP username, NAS, session ID and assigned address | A clear login boundary, with credentials and session recovery to manage |
| Hotspot | Public Wi-Fi, guest networks and short-duration access | Account or voucher reference, site, session and observed device | Browser login fits visitors; shared devices and login state complicate identity |
| DHCP/IPoE | Fixed wireless or FTTH designed around circuit/device identity | Service ID, trusted circuit/port/VLAN mapping, lease and device identifiers | No PPP login; dependable provisioning and enforcement become essential |
IPoE means carrying IP over Ethernet; DHCP commonly supplies addressing, but a DHCP lease alone is neither a customer account nor payment authorization. Hotspot also commonly uses DHCP. These are not three mutually exclusive ways to obtain an IP address: a hotspot login page adds an access decision after the device joins the network.
For residential fixed wireless, keep a working PPPoE design if it gives support a reliable username-to-home mapping. Evaluate IPoE when you can retain that mapping through CPE replacement and address changes. For public Wi-Fi, consider the visitor's login and expiry journey. For FTTH ONTs, confirm bridge/router mode and where PPP or DHCP terminates; fibre alone does not choose the access model. These are design recommendations, not ISPAgents compatibility certifications.
Keep the billing decision separate from enforcement
A useful architecture is:
Customer + service → billing decision → authorization policy → NAS enforcement → session and traffic evidence.
The NAS is the access router that admits or restricts the subscriber. RADIUS can carry authentication, authorization and accounting between that router and a policy server. It does not decide whether a payment is reconciled.
For a monthly home service, define the plan, due date, grace period and any intentional hold. For visitor access, define validity, activation, expiry and usage rules. In either case, document who can change access and what evidence support needs after a payment. A finance record marked paid cannot establish that the customer's traffic is passing.
Suspension and reconnect: CoA is different from an address list
| Mechanism | What it changes | What must be verified |
|---|---|---|
| RADIUS authorization policy | What a future authentication is allowed to receive | Correct subscriber policy, rate/profile and rejection behavior |
| RADIUS CoA | Supported attributes on an existing session | NAS support, session targeting and the actual resulting rate or policy |
| RADIUS Disconnect | Ends the selected session so the client can authenticate again | Persistent policy changed first; fresh authentication and accounting afterward |
| RouterOS address list plus firewall policy | Traffic treatment for the matching address | Correct current address, applicable rules and recovery after address changes |
An address-list entry is only a match condition; the firewall rule supplies the action. Scope it to a verified service address. Do not block a shared public NAT address as if it identified one subscriber. Review IPv4 and IPv6, rule order and any forwarding shortcuts with the network engineer.
For example, a paid household still under a suspended policy needs the correct authorization restored before a reconnect. If the prior policy limited speed, check the intended rate too. An ACK is control-plane evidence; confirm a fresh session and customer traffic before reporting service restored. Pause after a timeout or NAK instead of repeatedly disconnecting the customer.
RouterOS supports RADIUS for PPP and Hotspot, and supports selected CoA attributes. Verify the configured incoming port and permitted source; do not assume the NAS and controller defaults agree. See the MikroTik RADIUS manual. These vendor mechanisms do not establish that an ISPAgents adapter is released.
MikroTik checks before choosing a path
- PPPoE: audit local accounts and profiles before enabling RADIUS. Local user records can take precedence over RADIUS; prove which path authenticated the test session. See PPP AAA.
- Hotspot: test login, expiry, session removal and the payment/support destinations available before login. MikroTik documents its Hotspot gateway as IPv4-dependent; do not assume equivalent IPv6 hotspot login enforcement. See Hotspot documentation.
- DHCP/IPoE: record the trusted circuit or device mapping and test lease renewal and replacement equipment. RouterOS has DHCP RADIUS options, but those require their own policy and accounting validation. See DHCP documentation.
Keep customer, device and session identity distinct
A customer may have multiple services; a service may have replacement hardware and many sessions over time. Keep those records separate. A PPP username is an access identity, an ONT serial identifies equipment, and a lease address can change. A browser's observed MAC address is not a durable person identifier.
Correlate accounting using the NAS and session identity, timestamps and access username, rather than joining everything on an IP address. Missing or stale accounting means the current state is unknown. A Stop record ends that session; it does not prove all connections for the household are offline. See the subscriber/device identity guide.
A small pilot acceptance checklist
- Name one service group, one NAS, the policy owner and rollback owner.
- Match each customer to the exact access identity and intended rate/profile.
- Prove authentication and rejection with test accounts, then Start, Interim and Stop accounting for the same session.
- Rehearse one suspension and restore through the chosen path; check actual traffic, rate and an unaffected peer.
- Test the approved outage posture and rollback before expanding the group.
Where ISPAgents fits today
ISPAgents provides basic subscriber management: records, search and device assignment. Its canonical device identity foundation helps organize observations around a device; it is not a guarantee that every session or billing identity will match automatically.
Guided pilot: CRM/Customer 360, ISP customer billing, service-policy previews and result recording, MikroTik RouterOS operations, and existing FreeRADIUS integration require scoped onboarding. Live access mutation remains gated. ISPAgents Managed RADIUS is a guided pilot, requiring tenant-specific onboarding, live smoke and launch signoff; no general availability or hard SLA is claimed. IPAM is roadmap. Automatic end-to-end DHCP/IPoE or hotspot billing enforcement is not a shipped promise.
Review WISP management scope, FreeRADIUS integration, or the Winbox-to-RADIUS migration checklist with the operator running your pilot.
Frequently asked questions
Is PPPoE always better than DHCP/IPoE for a WISP?
No. PPPoE offers a login and session boundary; DHCP/IPoE avoids a PPP login but needs a dependable service-to-circuit or device mapping. Choose around your CPE, access network and recovery procedure.
Does disconnecting a subscriber suspend their account?
Not by itself. If authorization still permits access, the subscriber can reconnect. Change the intended authorization policy, verify it, and then refresh the session through the tested NAS path.
Does ISPAgents automate all three access models today?
No. Service-policy, MikroTik operations and RADIUS integrations remain guided pilot. Each access path needs explicit scope and recovery proof; an IPoE or hotspot design is not a shipped integration promise.
Continue the operations map.
One Subscriber, One Device Identity
Available: The canonical identity foundation supports mapping protocol observations toward one device/customer path using strong serial/MAC evidence. It does not establish universal billing, RADIUS, or controller integration.
Open pageGuidesFair-usage policies for unlimited ISP plans
Keep access available after a usage threshold, explain the reduced speed before purchase, and give support a policy they can defend.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page