Hack GPON – how to access, change and edit fibre ONTs

Original Article ↗ Hacker News Discussion ↗

Reverse‑engineering GPON fiber ONTs is giving technically adept users ways to bypass ISP‑supplied gateway hardware, clone devices, or swap in SFP modules, raising both enthusiasm for hardware freedom and concerns about network security and legality. Commenters contrast regions where regulators already mandate “bring your own device” policies or require bridge mode with markets where ISPs lock customers into opaque, rental-only ONT/router combos. The thread also broadens into a debate over GPON vs active fiber architectures, the operational trade-offs of letting customers supply ONTs, and calls for open-source, open-hardware ONT designs.

Purpose of Hack-GPON / ONT Hacking

  • Main interest is not “free HBO/free internet” but:
    • Replacing ISP-mandated gateways and combo devices.
    • Cloning ISP ONTs (MAC/serial/IDs) to use preferred GPON/XGS-PON ONTs or SFP(+) modules.
    • Gaining control over configuration, monitoring, and firmware.
  • Some see it as a “fiber equivalent” of owning your own cable modem.

Legal, Policy, and ISP Reactions

  • ISPs typically monitor ONTs and can detect and blacklist “alien” devices.
  • There is concern about criminal liability (referencing past DOCSIS “uncapping” cases), especially if monetized.
  • Sites offering this information tend to include heavy disclaimers.
  • Several countries/regions moving toward or already mandating BYOD router/ONT freedom (NL, parts of EU, Italy, Austria, Spain, Portugal).
    • Often the compromise: ISP controls ONT/modem but must provide bridge mode and open specs.
    • ISPs usually reserve the right to change technology (e.g., GPON → XGS-PON) and only guarantee service, not a specific standard.

Why People Want Their Own ONT

  • Avoid rental fees and low-quality or buggy ISP gear.
  • Use form factors they prefer (e.g., GPON/XGS-PON SFP modules, integrated fiber routers).
  • Enable features or performance the ISP ONT lacks:
    • Higher connection table limits for heavy use (e.g., Tor relays).
    • Lower latency, hairpin NAT, better diagnostics, or logging to Grafana.
    • Faster upgrades or hot spares without waiting for ISP truck rolls.
  • Privacy / security concerns about ISP-controlled boxes directly reachable from the ISP network.

Pushback and Practical Concerns

  • Some argue an ONT is a “dumb” L2 media converter and customer ownership adds little value vs. owning the router.
  • Misbehaving ONTs on a shared PON can affect neighbors; support burden and upgrade complexity rise when customers choose arbitrary hardware.
  • Others counter that ISPs can still deprecate old protocols with long notice and no requirement to support every device.

PON vs AON and Network Architecture Debates

  • Strongly mixed views:
    • Critics see GPON/PON as an over-complicated, shortsighted shared medium; prefer dedicated active fiber (AON/home-run).
    • Defenders note PON is vastly cheaper to deploy, supports high speeds (XGS-PON, 50G PON), and is “good enough” for decades.
  • Some countries use hybrid or wholesale models:
    • Physical P2P fibers but operated as PON.
    • Separate infrastructure providers (e.g., NZ/UK-like models) that multiple ISPs share, improving competition.
  • Observations that investment is increasingly XGS-PON-focused; some older AON deployments stagnate at 1 Gbps.

Tools, Hardware, and Open-Source Aspirations

  • Mention of specific ONTs and SFP ONUs being cloned or configured via UART/telnet; newer firmware sometimes locks this down.
  • Additional resource: pon.wiki for practical ONT→SFP swap guides.
  • Desire for:
    • An open-source, open-hardware ONT, or at least open firmware builds for common devices.
    • A “DD-WRT for ONTs” to inspect and extend ISP hardware behavior.