HHLONIX

Methodology

How Hlonix decides whether a router fits an ISP

The checker is a deterministic rules engine backed by dated evidence. It separates country, access technology, provider authentication, router capability and service features instead of producing a generic compatibility score.

Page reviewed 28 September 2026Dataset snapshot 23 September 2026Cited sources See evidence registerHow Hlonix verifies →

1. Country and service profile first

Hlonix does not apply one provider-wide rule when the same ISP offers different access technologies. FTTP, cable, FTTC/VDSL and provider-managed gateway profiles are separate when the hardware path changes.

2. Physical handoff before software settings

The checker asks whether your router receives Ethernet from an ONT/NTD/modem or must terminate VDSL itself. This prevents an Ethernet-only router from being called compatible with a DSL wall socket.

3. Match the WAN protocol

PPPoE, DHCP/IPoE, provider-managed access, MER-style behavior and special DHCP options are treated separately. VLAN requirements are checked independently.

4. Keep service features separate

Internet access can work while phone or TV does not. When current provider evidence says a managed feature needs the ISP box, that requirement changes the verdict.

5. Grade the evidence

High confidence uses direct current ISP/manufacturer documentation. Medium confidence identifies profiles that rely partly on provider-hosted community or model-specific knowledge-base material.

6. Prefer conservative unknowns

If the exact line, gateway firmware or router model cannot be verified, Hlonix returns a check-required result rather than guessing.

7. No combinatorial thin pages

The interactive checker calculates ISP × router combinations in the browser. Indexable pages are limited to stable country, provider, router, methodology and workflow guides with independent explanatory value.

Next step

Page reviewed 28 September 2026 · compatibility dataset snapshot 23 September 2026.