Showing preview only (1,127K chars total). Download the full file or copy to clipboard to get everything.
Repository: hack-gpon/hack-gpon.github.io
Branch: main
Commit: 868142ad9377
Files: 240
Total size: 1.0 MB
Directory structure:
gitextract_epc6vhe9/
├── .github/
│ └── workflows/
│ ├── notify-telegram-pr.yml
│ ├── pages.yml
│ └── preview-pr.yaml
├── .gitignore
├── 404.md
├── CONTRIBUTING.md
├── Gemfile
├── LICENSE
├── README.md
├── _config.docker.yml
├── _config.yml
├── _gpon/
│ ├── g_984_series.md
│ ├── gpon-auth.md
│ ├── mib.md
│ ├── ont.md
│ ├── pptp_veip.md
│ └── vendor.md
├── _includes/
│ ├── cig_password.html
│ ├── cig_password_xgspon.html
│ ├── head_custom.html
│ ├── icons/
│ │ └── custom.html
│ ├── image.html
│ ├── root_lantiq.html
│ ├── serial_dump.html
│ └── ymodem_lantiq.html
├── _layouts/
│ └── default.html
├── _ont/
│ ├── ont-adtran-sdx-611.md
│ ├── ont-adtran-sdx-611q.md
│ ├── ont-adtran-sdx-621i.md
│ ├── ont-adtran.md
│ ├── ont-bt-pon-bt-g711ax.md
│ ├── ont-bt-pon.md
│ ├── ont-calix-801gt.md
│ ├── ont-calix-801gv2.md
│ ├── ont-calix-gp1000g.md
│ ├── ont-calix-gp1100g.md
│ ├── ont-calix.md
│ ├── ont-carlitoxxpro-cpgos03-0490-v1.md
│ ├── ont-carlitoxxpro-cpgos03-0490-v2.md
│ ├── ont-carlitoxxpro.md
│ ├── ont-cig-g-97c1.md
│ ├── ont-cig-g-97cm.md
│ ├── ont-cig-g-97cp.md
│ ├── ont-cig-g-97s.md
│ ├── ont-cig-g-97sp.md
│ ├── ont-cig.md
│ ├── ont-d-link-dpn-100-rev-a2.md
│ ├── ont-d-link-dpn-100-rev-c1.md
│ ├── ont-d-link.md
│ ├── ont-fibermall-gpon-onu-clb+.md
│ ├── ont-fibermall-gpon-onu-stb+.md
│ ├── ont-fibermall.md
│ ├── ont-fs-com-gpon-onu-stick-with-mac.md
│ ├── ont-fs-com-mod.md
│ ├── ont-fs-com-onu1710-1g.md
│ ├── ont-fs-com.md
│ ├── ont-genexis-ft-g2110c-2.5g.md
│ ├── ont-genexis-ft-g2110c.md
│ ├── ont-genexis.md
│ ├── ont-halny-hl-gsfp.md
│ ├── ont-halny.md
│ ├── ont-hilink-hl23446.md
│ ├── ont-hilink.md
│ ├── ont-hisense-lte3415-sca+.md
│ ├── ont-hisense-lte3415-sh+.md
│ ├── ont-hisense.md
│ ├── ont-huawei-eg8010h.md
│ ├── ont-huawei-eg8010n.md
│ ├── ont-huawei-hg8010h.md
│ ├── ont-huawei-hg8110h.md
│ ├── ont-huawei-hg8240h.md
│ ├── ont-huawei-ma5671a-carlito.md
│ ├── ont-huawei-ma5671a-fs-mod.md
│ ├── ont-huawei-ma5671a-root-web.md
│ ├── ont-huawei-ma5671a-root.md
│ ├── ont-huawei-ma5671a-rooted.md
│ ├── ont-huawei-ma5671a-sf.md
│ ├── ont-huawei-ma5671a-ymodem.md
│ ├── ont-huawei-ma5671a.md
│ ├── ont-huawei-useful-command.md
│ ├── ont-huawei.md
│ ├── ont-kaon-pg1892g.md
│ ├── ont-kaon.md
│ ├── ont-leox-lxt-010g-d.md
│ ├── ont-leox-lxt-010h-d.md
│ ├── ont-leox-lxt-010s-h.md
│ ├── ont-leox-lxt-240g-c1.md
│ ├── ont-leox.md
│ ├── ont-luna-sdk-useful-commands.md
│ ├── ont-nokia-g-010g-a.md
│ ├── ont-nokia-g-010g-d.md
│ ├── ont-nokia-g-010g-p.md
│ ├── ont-nokia-g-010g-q.md
│ ├── ont-nokia-g-010g-r.md
│ ├── ont-nokia-g-010g-t.md
│ ├── ont-nokia-g-010s-a.md
│ ├── ont-nokia-g-010s-b.md
│ ├── ont-nokia-g-010s-p.md
│ ├── ont-nokia-g-010s-q.md
│ ├── ont-nokia-use.md
│ ├── ont-nokia-useful-command.md
│ ├── ont-nokia.md
│ ├── ont-odi-realtek-dfp-34g-2c2.md
│ ├── ont-odi-realtek-dfp-34x-2c2.md
│ ├── ont-odi-zte-dfp-34g-2c2.md
│ ├── ont-odi-zte-dfp-34x-2c2.md
│ ├── ont-odi.md
│ ├── ont-sercomm-fg1000b-11.md
│ ├── ont-sercomm-fg1000b.md
│ ├── ont-sercomm-fg1000r.md
│ ├── ont-sercomm-fgs202.md
│ ├── ont-sercomm.md
│ ├── ont-sourcephotonics-sps-34-24t-hp-tdfm.md
│ ├── ont-sourcephotonics-sps-34-24t-hp-tdfo.md
│ ├── ont-sourcephotonics.md
│ ├── ont-t-w-tw2362h-cdel.md
│ ├── ont-t-w-twcgpon657.md
│ ├── ont-t-w.md
│ ├── ont-technicolor-afm0002.md
│ ├── ont-technicolor-afm0003.md
│ ├── ont-technicolor.md
│ ├── ont-template.md
│ ├── ont-tplink-xz000-g3.md
│ ├── ont-tplink.md
│ ├── ont-ufiber-uf-instant.md
│ ├── ont-ufiber-uf-loco.md
│ ├── ont-ufiber-uf-nano.md
│ ├── ont-ufiber-wave-fiber-onu.md
│ ├── ont-ufiber.md
│ ├── ont-uplink-gp502r.md
│ ├── ont-uplink.md
│ ├── ont-vsol-v2801f.md
│ ├── ont-vsol-v2801q.md
│ ├── ont-vsol-v2802rh.md
│ ├── ont-vsol.md
│ ├── ont-yotc-m2-2050-g40.md
│ ├── ont-yotc.md
│ ├── ont-zisa-op151s.md
│ ├── ont-zisa.md
│ ├── ont-zte-f6005.md
│ ├── ont-zte-f6005v3.md
│ ├── ont-zte-f601.md
│ ├── ont-zte.md
│ ├── ont-zyxel-pmg1005-t20b.md
│ ├── ont-zyxel-pmg3000-d20b.md
│ ├── ont-zyxel-pmg3100-t0.md
│ ├── ont-zyxel-pmg5100-t0.md
│ ├── ont-zyxel-pmg5318.md
│ ├── ont-zyxel.md
│ └── serial_dump/
│ ├── fg1000b-11_boot_cfe.txt
│ ├── fs-com-onu1710-1g/
│ │ ├── bootlog.txt
│ │ └── uboot-env.txt
│ ├── ma5671a_minishell.txt
│ ├── yotcm2-2050-g40.txt
│ └── yotcm2-2050-g40newrevision.txt
├── _ont_epon/
│ ├── bcctv.md
│ ├── bcctv_PNC11C.md
│ ├── free_iliad.md
│ ├── free_iliad_F-MDCONU3A.md
│ ├── free_iliad_F-MDCONU5A.md
│ └── free_iliad_P-MDONU4B.md
├── _ont_xgs/
│ ├── ont-ALL-BM410-XGSPON-GBIC.md
│ ├── ont-ECIN-EN-XGSFPP-OMAC-v1.md
│ ├── ont-allnet.md
│ ├── ont-cig-XG-99S.md
│ ├── ont-cig.md
│ ├── ont-ecin.md
│ ├── ont-fs-XGS-ONU-25-20NI-cli.md
│ ├── ont-fs-XGS-ONU-25-20NI.md
│ ├── ont-fs-com.md
│ ├── ont-hisense-ltf7267-bha+.md
│ ├── ont-hisense.md
│ ├── ont-huawei-hn8010ts.md
│ ├── ont-huawei-useful-command.md
│ ├── ont-huawei.md
│ ├── ont-nokia-use.md
│ ├── ont-nokia-useful-command.md
│ ├── ont-nokia-xs-010s-q.md
│ ├── ont-nokia-xs-010x-q.md
│ ├── ont-nokia.md
│ ├── ont-zte-f2801s.md
│ ├── ont-zte.md
│ ├── ont-zyxel-pm7300-t0.md
│ ├── ont-zyxel.md
│ └── serial_dump/
│ └── fs-XGS-ONU-25-20NI_minishell.txt
├── _router_pon/
│ ├── avm.md
│ ├── avm_fritzbox.md
│ ├── avm_fritzbox_5530.md
│ ├── avm_fritzbox_5590.md
│ ├── free_iliad.md
│ ├── free_iliad_box_pop.md
│ ├── ont-zte-f6645p.md
│ ├── ont-zte.md
│ ├── tp_link.md
│ ├── tp_link_xb432v.md
│ └── tp_link_xx800v.md
├── _sass/
│ └── custom/
│ └── custom.scss
├── _sfp/
│ ├── bosa-tosa-rosa.md
│ ├── ont-wo-mac.md
│ └── sfp-standard.md
├── _sfp_cage/
│ ├── banana-pi.md
│ ├── broadcom-57810s.md
│ ├── digitus-10gbps-dn-82211.md
│ ├── fiberethernet-media-converter-2.5.md
│ ├── macchiatobin.md
│ ├── mikrotik.md
│ ├── tp-link.md
│ ├── turris.md
│ ├── ubiquiti.md
│ ├── zte.md
│ └── zyxel.md
├── _tools/
│ ├── ascii-hex.md
│ ├── gpon-omci-vlan-parser.md
│ ├── molex-ont.md
│ ├── ont-ethtool-print-eeprom.md
│ ├── ont-lantiq-print-eeprom.md
│ ├── speed-gpon-eth.md
│ └── ttl-uart-adapter.md
├── assets/
│ ├── css/
│ │ ├── just-the-docs-dark.scss
│ │ ├── just-the-docs-default.scss
│ │ └── just-the-docs-light.scss
│ ├── js/
│ │ ├── cigpassword.js
│ │ ├── omci-vlan.js
│ │ ├── rootLantiq.js
│ │ ├── serialUtil.js
│ │ ├── vue/
│ │ │ └── vue-lantiq-eeprom.vue
│ │ ├── vue-eeprom.js
│ │ └── xymini.js
│ └── ts/
│ └── LTF7267-BHA-ploam.ts
├── bin/
│ └── just-the-docs
├── browserconfig.xml
├── docker-compose.yml
├── faq.md
├── index.md
├── package.json
├── privacy-policy.md
├── quick-start.md
├── rakefile
├── site.webmanifest
└── tsup.config.ts
================================================
FILE CONTENTS
================================================
================================================
FILE: .github/workflows/notify-telegram-pr.yml
================================================
name: notify-telegram-pr
on:
pull_request_target:
types: [opened, reopened]
issues:
types: [opened, reopened]
jobs:
build:
name: Notify Telegram
runs-on: ubuntu-latest
steps:
- name: send telegram message on PR opened
if: github.event.pull_request
uses: appleboy/telegram-action@master
with:
to: ${{ secrets.TELEGRAM_TO }}
token: ${{ secrets.TELEGRAM_TOKEN }}
if: github.event.issue
message: |
${{ github.actor }} created PR ${{ github.event.pull_request.title }}
See changes: ${{ github.event.pull_request.html_url }}
- name: send telegram message on issue opened
if: github.event.issue
uses: appleboy/telegram-action@master
with:
to: ${{ secrets.TELEGRAM_TO }}
token: ${{ secrets.TELEGRAM_TOKEN }}
if: github.event.issue
message: |
${{ github.actor }} created issue ${{ github.event.issue.title }}
See issue: ${{ github.event.issue.html_url }}
================================================
FILE: .github/workflows/pages.yml
================================================
# Sample workflow for building and deploying a Jekyll site to GitHub Pages
name: Deploy Jekyll site to Pages
on:
# Runs on pushes targeting the default branch
push:
branches: ["main"]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
contents: read
pages: write
id-token: write
# Allow one concurrent deployment
concurrency:
group: "pages"
cancel-in-progress: true
jobs:
# Build job and deploy
build:
runs-on: ubuntu-latest
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Setup node
uses: actions/setup-node@v3
with:
node-version: 20
- name: Install Node deps
run: npm ci
- name: Compile typescript
run: npm run build
- name: Setup Ruby
uses: ruby/setup-ruby@v1
with:
ruby-version: '3.0' # Not needed with a .ruby-version file
bundler-cache: true # runs 'bundle install' and caches installed gems automatically
cache-version: 0 # Increment this number if you need to re-download cached gems
- name: Setup Pages
id: pages
uses: actions/configure-pages@v5
- run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}" # defaults output to '/_site'
env:
JEKYLL_ENV: production
- name: Upload artifact
uses: actions/upload-pages-artifact@v3 # This will automatically upload an artifact from the '/_site' directory
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4
================================================
FILE: .github/workflows/preview-pr.yaml
================================================
name: preview-pr
on:
pull_request_target:
types: [opened, reopened, synchronize]
permissions:
pull-requests: write
jobs:
authorize:
environment:
${{ github.event_name == 'pull_request_target' &&
github.event.pull_request.head.repo.full_name != github.repository &&
'external' || 'internal' }}
runs-on: ubuntu-latest
steps:
- run: "true"
build:
needs: authorize
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
with:
ref: ${{ github.event.pull_request.head.sha }}
- name: Setup Ruby
uses: ruby/setup-ruby@v1
with:
ruby-version: '3.0'
bundler-cache: true
- run: bundle exec jekyll build --baseurl ""
- name: Publish to Cloudflare Pages
id: preview-pages
uses: cloudflare/pages-action@v1
with:
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
accountId: ${{ secrets.CLOUDFLARE_ACCOUNT }}
projectName: hack-gpon-preview
directory: _site
branch: preview
- uses: thollander/actions-comment-pull-request@v2
with:
message: |
Preview of the website obtained from the PR: ${{ steps.preview-pages.outputs.url }}
================================================
FILE: .gitignore
================================================
### Jekyll ###
_site/
.sass-cache/
.jekyll-cache/
.jekyll-metadata
Gemfile.lock
assets/js/zzzz-search-data.json
node_modules/
assets/js/generated
================================================
FILE: 404.md
================================================
---
layout: default
title: Page not found
permalink: /404
nav_exclude: true
search_exclude: true
description: Opps. The page you are looking for got lost.
---
<p>This is not the ONT you are looking for. Try using the navigation bar {% if site.search_enabled != false %}or search {% endif %}to find what you're looking for or go to the <a href="{{ '/' | relative_url }}">website's home page</a>.</p>
<div class="ont-404 mt-9">
<svg width="116.52087mm" height="36.783329mm" viewBox="0 0 116.52087 36.783329" version="1.1" id="svg28164" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
<path id="path31930" d="m 0,11.403492 v 6.35 c 0,0.584491 0.473832,1.058334 1.058334,1.058334 0.102211,0 0.19827,0 0.290938,0 h 2.8840618 v 1.058333 c 0,0.264583 0.529166,0.529167 1.058333,0.529167 l 12.4286992,0.517789 c 0.49499,0.684954 1.162822,1.069287 1.858801,1.069711 H 32.808333 V 20.928492 H 34.925 v -1.058333 c 1.169003,0 2.116666,-0.71075 2.116666,-1.5875 0,-0.87675 -0.947663,-1.5875 -2.116666,-1.5875 V 15.636826 H 32.808333 V 14.578492 H 19.579167 c -0.67963,0.01667 -1.328582,0.399071 -1.812293,1.067647 L 5.2916668,16.165992 c -0.529167,0 -1.058333,0.264584 -1.058333,0.529167 v 1.058333 H 1.490348 c -0.131088,-0.0042 -0.276807,0 -0.432014,0 v -6.35 z m 19.579167,4.233334 h 1.5875 v 2.645833 2.645833 h -1.5875 c -0.876753,0 -1.5875,-1.184592 -1.5875,-2.645833 0,-1.461241 0.710747,-2.645833 1.5875,-2.645833 z m 2.645833,0 h 1.058333 v 5.291666 H 22.225 Z m 2.116667,0 H 25.4 v 5.291666 h -1.058333 z m 2.116666,0 H 31.75 v 5.291666 H 26.458333 Z M 15.875,16.695159 h 1.058333 v 3.175 h -3.175 V 17.753492 H 12.7 v 1.852084 H 9.5249998 v -1.5875 h -1.058333 v 1.322916 h -3.175 v -2.116666 h 1.058333 v 1.058333 h 1.058333 v -1.058333 h 3.1750002 v 1.322916 h 1.058334 v -1.5875 h 3.175 v 1.852084 H 15.875 Z m 16.933333,0 h 1.058334 v 3.175 h -1.058334 z m 2.091862,1.058333 c 0.587095,0 1.083138,0.236908 1.083138,0.529167 0,0.292259 -0.496043,0.529167 -1.083138,0.529167 z"></path>
<path d="M 44.906979,27.034723 H 116.52088 V 9.7486096 H 44.906979 Z m 11.641664,-1.058334 h -10.58333 v -1.940278 h 8.11389 V 12.410555 h -8.11389 v -1.603611 h 10.58333 z m 43.744457,0 H 57.606983 V 10.806944 H 100.2931 Z m 15.16945,0 h -14.11112 v -1.940278 h 12.02973 l -0.0353,-11.1125 h -11.99445 v -2.116667 h 14.11112 z M 53.020873,13.276388 v 9.877779 h -7.05556 v -9.877779 h 3.81 z M 109.46532,14.6875 v 0.705555 h -1.76389 v 0.705556 h 1.76389 v 0.705555 h -1.76389 v 0.705556 h 1.76389 v 0.705556 h -1.76389 v 0.705555 h 1.76389 v 0.705556 h -1.76389 v 0.705555 h 1.76389 V 21.0375 h -1.76389 v 0.705556 h 1.76389 v 1.411111 h -8.11389 l 0.0706,-4.198056 -0.0706,-4.974167 h 8.11389 z m 2.82223,8.466667 h -1.76389 v -9.172223 l 1.75727,-0.01654" id="path2"></path>
<rect id="rect13056" height="8.8194437" x="33.669872" y="20.397436" width="1.058" transform="rotate(-30.427871)"></rect>
<rect id="rect13056-0" height="8.8194437" x="19.819189" y="29.127432" width="1.058" transform="rotate(-47.800842)"></rect>
<rect id="rect13056-3" height="8.8194437" x="52.298908" y="-11.319631" width="1.058" transform="matrix(0.86226741,0.50645327,0.50645327,-0.86226741,0,0)"></rect>
<rect id="rect13056-0-9" height="8.8194437" x="47.068806" y="4.4197102" width="1.058" transform="matrix(0.6717097,0.74081447,0.74081447,-0.6717097,0,0)"></rect>
</svg>
</div>
================================================
FILE: CONTRIBUTING.md
================================================
<!-- omit in toc -->
# Contributing to Hack-Gpon
First off, thanks for taking the time to contribute! ❤️
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
> - Star the project
> - Tweet about it
> - Refer this project in your project's readme
> - Mention the project at local meetups and tell your friends/colleagues
<!-- omit in toc -->
## Table of Contents
- [I Have a Question](#i-have-a-question)
- [I Want To Contribute](#i-want-to-contribute)
- [Reporting Bugs](#reporting-bugs)
- [Suggesting Enhancements](#suggesting-enhancements)
- [Your First Code Contribution](#your-first-code-contribution)
- [Improving The Documentation](#improving-the-documentation)
- [Styleguides](#styleguides)
- [Commit Messages](#commit-messages)
- [Join The Project Team](#join-the-project-team)
## I Have a Question
> If you want to ask a question, we assume that you have read the available [Documentation](https://hack-gpon.org/).
Before you ask a question, it is best to search for existing [Issues](https://github.com/hack-gpon/hack-gpon.github.io/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, we recommend the following:
- Open an [Issue](https://github.com/hack-gpon/hack-gpon.github.io/issues/new).
- Provide as much context as you can about what you're running into.
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
We will then take care of the issue as soon as possible.
<!--
You might want to create a separate issue tag for questions and include it in this description. People should then tag their issues accordingly.
Depending on how large the project is, you may want to outsource the questioning, e.g. to Stack Overflow or Gitter. You may add additional contact and information possibilities:
- IRC
- Slack
- Gitter
- Stack Overflow tag
- Blog
- FAQ
- Roadmap
- E-Mail List
- Forum
-->
## I Want To Contribute
> ### Legal Notice <!-- omit in toc -->
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
### Reporting Bugs
<!-- omit in toc -->
#### Before Submitting a Bug Report
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
- Make sure that you are using the latest version.
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://hack-gpon.org/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/hack-gpon/hack-gpon.github.ioissues?q=label%3Abug).
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
- Collect information about the bug:
- Stack trace (Traceback)
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
- Possibly your input and the output
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
<!-- omit in toc -->
#### How Do I Submit a Good Bug Report?
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <>.
<!-- You may add a PGP key to allow the messages to be sent encrypted as well. -->
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
- Open an [Issue](https://github.com/hack-gpon/hack-gpon.github.io/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
- Explain the behavior you would expect and the actual behavior.
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
- Provide the information you collected in the previous section.
Once it's filed:
- The project team will label the issue accordingly.
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
<!-- You might want to create an issue template for bugs and errors that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
### Suggesting Enhancements
This section guides you through submitting an enhancement suggestion for Hack-Gpon, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
<!-- omit in toc -->
#### Before Submitting an Enhancement
- Make sure that you are using the latest version.
- Read the [documentation](https://hack-gpon.org/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
- Perform a [search](https://github.com/hack-gpon/hack-gpon.github.io/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
<!-- omit in toc -->
#### How Do I Submit a Good Enhancement Suggestion?
Enhancement suggestions are tracked as [GitHub issues](https://github.com/hack-gpon/hack-gpon.github.io/issues).
- Use a **clear and descriptive title** for the issue to identify the suggestion.
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. <!-- this should only be included if the project has a GUI -->
- **Explain why this enhancement would be useful** to most Hack-Gpon users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
<!-- You might want to create an issue template for enhancement suggestions that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
### Your First Code Contribution
<!-- TODO
include Setup of env, IDE and typical getting started instructions?
-->
### Improving The Documentation
<!-- TODO
Updating, improving and correcting the documentation
-->
## Styleguides
### Commit Messages
<!-- TODO
-->
## Join The Project Team
<!-- TODO -->
<!-- omit in toc -->
## Attribution
This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!
================================================
FILE: Gemfile
================================================
source "https://rubygems.org"
gem "webrick"
gem "rake"
gem "json"
group :jekyll_plugins do
gem "jekyll-last-modified-at"
gem "jekyll-redirect-from"
gem "jekyll-remote-theme"
gem "jekyll-seo-tag"
gem 'jekyll-default-layout'
gem 'jekyll-include-cache'
gem 'jekyll-sitemap'
end
================================================
FILE: LICENSE
================================================
MIT License
Copyright (c) 2022 hack-gpon
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
================================================
FILE: README.md
================================================
```
_ _ _ ____ ____ ___ _ _
| | | | __ _ ___ | | __ / ___|| _ \ / _ \ | \ | |
| |_| | / _` | / __|| |/ / | | _ | |_) || | | || \| |
| _ || (_| || (__ | < | |_| || __/ | |_| || |\ |
|_| |_| \__,_| \___||_|\_\ \____||_| \___/ |_| \_|
```
# Hack GPON
Based on just-the-docs theme:
- [GitHub](https://github.com/just-the-docs/just-the-docs)
- [Demo](https://just-the-docs.github.io/just-the-docs/)
if you want to contribute there is something to be done:
- a unique template for all sticks
- how to use arduino as TTL/UART adapter
- theoretical information on GPON
- absent stick information
- quick start
- absent and new ont
## How to build
This website uses typescript, so remember to:
- Install node (20)
- Run npm ci to install all relevant typescript packages
- Run npm run build to transpile ts to js
Alternatively, you can just run:
`docker-compose up -d typescript` which will build all the required typescript files for you
================================================
FILE: _config.docker.yml
================================================
url: "http://localhost:4000"
================================================
FILE: _config.yml
================================================
remote_theme: simonebortolin/just-the-docs
title: "Hack GPON"
baseurl:
permalink: '/:title'
search_enabled: true
search:
# Split pages into sections that can be searched individually
# Supports 1 - 6, default: 2
heading_level: 2
# Maximum amount of previews per search result
# Default: 3
previews: 3
# Maximum amount of words to display before a matched word in the preview
# Default: 5
preview_words_before: 5
# Maximum amount of words to display after a matched word in the preview
# Default: 10
preview_words_after: 10
# Set the search token separator
# Default: /[\s\-/]+/
# Example: enable support for hyphenated search words
tokenizer_separator: /[\s/]+/
# Display the relative url in search results
# Supports true (default) or false
rel_url: true
# Enable or disable the search button that appears in the bottom right corner of every page
# Supports true or false (default)
button: false
plugins:
- jekyll-seo-tag
- jekyll-last-modified-at
- jekyll-redirect-from
- jekyll-default-layout
- jekyll-sitemap
color_scheme: "auto"
enable_switch_color_scheme: true
enable_localstorage_color_scheme: true
nav_sort: case_sensitive
aux_buttons:
- title: "GitHub"
color: 'purple'
icon: 'github'
link: '//github.com/hack-gpon/hack-gpon.github.io'
- title: "Telegram"
color: 'blue'
icon: 'telegram'
link: '//t.me/HackGPON'
#aux_links:
# "Hack GPON on GitHub":
# - "//github.com/hack-gpon/hack-gpon.github.io"
# "Hack GPON on Telegram":
# - "//t.me/HackGPON"
back_to_top: true
back_to_top_text: "Back to top"
footer_content: "Copyright © 2022-2023. The documentation hereby found is distributed under the terms of the <a href=\"https://github.com/hack-gpon/hack-gpon.github.io/blob/main/LICENSE\">MIT License</a>. Any external reference, link or software retains its original license and is not under the control of this website. <a href=\"/privacy-policy\">Privacy Policy</a>."
last_edit_timestamp_script: true
gh_edit_link: true # show or hide edit this page link
gh_edit_link_text: "Edit this page on GitHub"
gh_edit_repository: "https://github.com/hack-gpon/hack-gpon.github.io" # the github URL for your repo
gh_edit_branch: "main" # the branch that your docs is served from
# gh_edit_source: docs # the source that your files originate from
gh_edit_view_mode: "tree"
gh_owner_name: hack-gpon
gh_repository_name: hack-gpon.github.io
whitelist:
- jekyll-redirect-from
mermaid_enabled: true
mermaid:
# Version of mermaid library
# Pick an available version from https://cdn.jsdelivr.net/npm/mermaid/
version: "9.1.3"
# Configured theme of mermaid diagrams
# Pick an avaiable theme from https://mermaid-js.github.io/mermaid/#/theming
theme: "default"
# Additional configuration available matching pattern as defined in https://mermaid-js.github.io/mermaid/#/./Setup.
# For example,
# logLevel: 'fatal',
# sequence:
# diagramMarginX: 50
# actorMargin: 50
# gantt:
# barGap: 4
# topPadding: 50
enable_modal: true
collections:
ont:
permalink: "/:path/"
output: true
ont_xgs:
permalink: "/xgs/:path/"
output: true
ont_epon:
permalink: "/epon/:path/"
output: true
router_pon:
permalink: "/router/:path/"
output: true
tools:
permalink: "/:path/"
output: true
sfp:
permalink: "/:path/"
output: true
gpon:
permalink: "/:path/"
output: true
sfp_cage:
permalink: "/:path/"
output: true
just_the_docs:
collections:
ont:
name: ONT GPON
nav_fold: true
ont_xgs:
name: ONT XGS-PON
nav_fold: true
ont_epon:
name: ONT EPON
nav_fold: true
router_pon:
name: Router PON
nav_fold: true
tools:
name: Tools
nav_fold: true
sfp:
name: SFP Resources & standard
nav_fold: true
gpon:
name: GPON Resources & standard
nav_fold: true
sfp_cage:
name: SFP cage
nav_fold: true
defaults:
-
scope:
path: "assets/**/*.pdf"
values:
sitemap: false
enable_rainbow: true
================================================
FILE: _gpon/g_984_series.md
================================================
---
title: GPON G.984 Series
has_children: false
nav_order: 3
layout: default
---
The information on this page is taken from the GPON standard and information from the major vendors of GPON equipment, each individual item containing a verifiable citation in the standard. Feel free to cite this page as: `{{ page.title }}, Hack GPON. Available at: https://hack-gpon.org{{ page.url }}`.
| G.984.1 | G.984.2 | G.984.3 | G.984.4 | G.988 (ex G.Imp984.4) |
| ----------------------- | ----------------------------------- | ------------------------------ | ---------------------------------- | ------------------------ |
| General Characteristics | Physical Media Dependant Layer | Transmission Convergence Layer | ONT Management & Control Interface | OMCI Implementer's Guide |
| Architecture | Bit Rate/coding | GTC Protocol | Reference model | |
| Distance/Reach | Wavelength | GTC Framing | OMCI requirement | |
| Split Ratio | Optical element specs and operation | ONU Activation | MIBs | |
| Protection | Link budget (amendment) | Security / FEC | OMCC | |
| | | Alarms / Monitoring | | |
| | | OMCI | | |
# General Concepts[^zyxel]
- Bitrate: 1.2 Gbps Upstream; 2.4 Gbps Downstream.
- Physical Reach: Max physical distance between OLT and ONT.
- Differential Fiber Distance: Distance between closest and farthest ONT from OLT (max = 20km)
## Basic Performance Parameters[^cisco]
| Upstream (Rate - Gbps) | Downstream (Rate - Gbps) |
| ---------------------- | ------------------------ |
| 0.15552 | 1.24416 |
| 0.62208 | 1.24416 |
| 1.24416 | 1.24416 |
| 0.15552 | 2.48832 |
| 0.62208 | 2.48832 |
| **1.24416** | **2.48832** |
| 2.48832 | 2.48832 |
1.24416 Gbps up, 2.48832 Gbps down is the most supported speed combination at current time.
# GPON Terminology
{% include image.html file="quick-start/gpon-terminology.png" alt="Overview of GPON Terminology" caption="Overview of GPON Terminology" %}
## ONU Identifier (ONU-ID)[^zyxel]
* 8 bit identifier (0~255)
* 0 .. 253 Assignable
* 254 Reserved
* 255 Broadcast/unassigned
* The OLT assigns an id to any ONU during the ONU's activation using the PLOAM channel.
* ONU-ID is unique across the PON and remains valid until the ONU is powered off, deactivated by the OLT or moves itself into an inactive state.
## Allocation Identifier (Alloc-ID)[^zyxel]
* Alloc-ID is a 12-bit identifier (0 .. 4095) that the OLT assigns to an ONU's traffic-bearing entity.
* 0 .. 253 Default
* 254 Broadcast
* 255 Unassigned
* 256 .. 4095 Assignable
* A Traffic-bearing entity can be represented either by a T-CONT or by the upstream OMCC.
## Transmission Containers (T-CONT)[^zyxel],[^broadbandforum]
A Transmission Container (T-CONT) is an ONU object representing a group of logical connections that appear as a single entity for the purpose of upstream bandwidth assignment on the PON.
* Bandwidth assignment and QoS control are performed in every T-CONT by fixed and dynamic methods.
* There are 5 types of T-CONT Traffic Descriptors:
* Type 1: fixed bandwidth;
* Type 2 and Type 3: guaranteed bandwidth;
* Type 4: best-effort;
* Type 5: mixed type, involving all bandwidth types and bearing all services
| Type 1 | Type 2 | Type 3 | Type 4 | Type 5 |
| --------- | --------- | --------- | ------ | ---------------- |
| SIR | | | | SIR |
| | AIR | AIR | | AIR |
| PIR = SIR | PIR = AIR | PIR > AIR | PIR | PIR >= SIR + AIR |
* For TR-156 and TR-167, each T-CONT represents a traffic class
* Each ONU is assigned at least one Alloc-ID which is equal to that ONU's ONU-ID and may be assigned additional Alloc-IDs per the OLT's discretion.
* Typically have 4 T-CONTs, supporting 4 traffic classes, plus an extra one for OMCI
* The default Alloc-ID is used to carry the upstream PLOAM and OMCC traffic and may carry user data traffic.
* The OLT schedules upstream traffic across all ONUs according to the priority and weight assigned to each T-CONT, and their buffer occupancy. Other bandwidth assignment mechanisms are available, for example fixed bandwidth, assured bandwidth, and nonassured bandwidth[^broadbandforum].
## Dynamic Bandwidth Allocation (DBA)
{% include image.html file="quick-start/pon_dba.jpg" alt="PON DBA Abstraction" caption="PON DBA Abstraction" %}
Dynamic Bandwidth Allocation (DBA) is a technique by which traffic bandwidth in a shared telecommunications medium can be allocated on demand and fairly between different users of that bandwidth. It is performed on the upstream traffic[^zyxel].
With DBA, the OLT assesses the bandwidth needs of the ONUs in real time and allocates upstream PON capacity accordingly[^broadbandforum].
DBA basic model supports[^zyxel]:
- Fixed bandwidth (highest priority)
- Assured bandwidth
- Non-assured bandwidth
- Best-effort bandwidth (lowest priority)
{% include image.html file="quick-start/bda-pratical.jpg" alt="Bandwidth Assignment practical example" caption="Bandwidth Assignment practical example" %}
## GPON transmission basics[^cisco]
Key Terms:
- Physical layer overhead upstream (PLOu) - Upstream physical layer overhead.
- Physical layer OAM upstream (PLOAMu) - PLOAM messages of upstream data. Think of this as a message-based operation and management channel between the OLT and ONU/ONTs.
- Power level sequence upstream (PLSu) - Upstream power level sequence
- Dynamic bandwidth report upstream (DBRu) - Upstream dynamic bandwidth report
Payload - User data
- PCBd - Physical Control Block downstream
- OMCC - Optical Network Unit Management and Control Channel
- OMCI - Optical Network Unit Management and Control Interface
### GPON Encapsulation
GPON uses two layers of encapsulation:
1. TDM and Ethernet frames are wrapped into GTC Encapsulation Method (GEM) frames, which have a GFP-like format (derived from Generic Frame Procedure ITU G.7401).
The main purpose of the GEM frame is to provide a frame-oriented service, as an alternative to ATM, in order to efficiently accommodate Ethernet and TDM frames. With GEM, all traffic is mapped across the GPON network using a variant of SONET/SDH GFP. GEM natively supports transportation of voice, video, and data without an added ATM or IP encapsulation layer[^medium],[^fs].
2. ATM and GEM frames are both encapsulated into GTC frames that are finally transported over the PON[^medium],[^fs].
ITU-T G.984 defines GEM as the only data transport scheme for GPON. Bandwidth allocation in GPON grants individual transmission opportunities to the ONU's traffic-bearing entities on the timescale of a single GTC frame[^zyxel].
As shown in the image, the difference between a downstream and upstream frame.
{% include image.html file="quick-start/gtc-layer-framing.png" alt="Downstream and Upstream GTC frame" caption="Downstream and Upstream GTC frame" %}
### Downstream[^zyxel],[^broadbandforum],[^cisco]
{% include image.html file="quick-start/gpon-downstream.jpg" alt="GPON Downstream" caption="GPON Downstream" %}
A downstream GPON frame has a fixed length of 125 μs and is 38880 bytes long which corresponds to the downstream data rate of 2.48832 Gbps, comprised of two components: physical control block downstream (PCBd) and payload.
{% include image.html file="quick-start/gtc-layer-frame.png" alt="GTC Layer framing" caption="GTC Layer framing" %}
The PCBd length range depends on the number of allocation structures per frame.
The OLT broadcasts PCBd to all ONU/ONTs. The ONU/ONTs receive the PCBd and performs operations based on the information received. GPON use Broadcast downstream data transmission with AES (Advanced Encryption Standard) to ensure secure delivery to destination:
- Traffic multiplexing is centralized.
- GEM Port-ID is the key to identify the GEM frames that belong to different downstream logical connections.
- Only frames with the appropriate Port-IDs are allowed through to the GEM client function.
- Each ONU filters the downstream GEM frame based on their GEM Port-ID and processes only the GEM frames that belong to that ONU.
PCBd consists of the GTC header and BWmap:
- GTC Header - Used for frame delimitation, synchronization, and forward error correction (FEC).
- BWmap - Field notifies very ONU of upstream bandwidth allocation. Specifies the start and end upstream time slots for the T-CONTs of each ONU. This ensures that all ONUs send data based on the time slots specified by the OLT to prevent data conflict.
{% include image.html file="quick-start/downstream-multiplexing.png" alt="Downstream multiplexing (shaded GEM port indicates multicast)" caption="Downstream multiplexing (shaded GEM port indicates multicast)" %}
1. The OLT sends Ethernet frames from Uplink ports to the GPON service processing module based on configured rules to the PON ports.
2. The GPON service processing module then encapsulates the Ethernet frames into GEM port data packets for downstream transmission.
3. GPON transmission convergence (GTC) frames that contain GEM PDUs are broadcast to all ONT/ONUs connected to the GPON port.
4. The ONT/ONU filters the received data based on the GEM port ID contained in the GEM PDU header and only retains data significant to the GEM ports on this ONT/ONU.
5. The ONT decapsulates the data and sends the Ethernet frames to the end users via service ports.
### Upstream[^zyxel],[^broadbandforum],[^cisco]
{% include image.html file="quick-start/gpon-upstream.jpg" alt="GPON Upstream" caption="GPON Upstream" %}
In the Upstream channel, GEM traffic is carried over one or more T-CONTs. The OLT receives the transmission associated with the T-CONT and the frames are forwarded to the GEM TC adapter and then the GEM client.
- Use Time Division Multiple Access (TDMA) for upstream data transmission w/o AES encryption.
* Distance between the OLT and ONT/ONU is measured (Ranging):
* The OLT starts the process on an ONU when the ONU first registers with the OLT and obtains round trip delay (RTD) of the ONU. Based on the RTD, other key components are identified:
* Calculation of the physical reach of that specific ONU, as this OLT requires a proper equalization delay (EqD) for each ONU based on physical reach.
* RTC and EqD synchronize data frames sent by all ONUs.
* Time slots are allocated based on distance. In order to prevent data conflict (collisions), the OLT must be able to precisely measure the distance between itself and each ONU to provide a proper time slot to facilitate data upstream. This allows the ONUs to send data at specified time slots, to prevent issues upstream. This process is achieved through a technique called ranging.
* The ONT/ONU sends traffic upstream based on the granted time slot.
- Dynamic Bandwidth Allocation (DBA) enables the OLT to monitor in real-time, congestion, bandwidth usage, and configuration.
- Traffic multiplexing is distributed.
- The OLT grants upstream bandwidth allocation.
- The ONU traffic-bearing entities are identified by their Allocations IDs.
- Alloc-IDs are multiplexed in time as specified by the bandwidth-map (provided by the OLT in the downstream frame).
- Within its bandwidth allocation, the ONU uses the GEM Port-IF as key to identify upstream GEM frames.
- Each upstream frame contains the content carried by one or more T-CONTs.
- All ONUs connected to a GPON port share the upstream bandwidth.
- All ONUs send their data upstream at their own time slots based on bandwidth map (BWmap) requirements.
- Each ONU reports the status of data to be sent to the OLT by use of upstream frames. OLT uses DBA to allocate upstream time slots to ONUs and sends updates in each frame.
- Burst Technology: Upstream packet flow is achieved via bursts, with each ONU/ONT responsible for data transmission within its allocated time slots. When an ONU/ONT is not within its time slot, the device disables transmission of its optical transceiver to prevent other ONU/ONT impact.
{% include image.html file="quick-start/upstream-multiplexing.png" alt="Upstream multiplexing" caption="Upstream multiplexing" %}
1. ONT/ONUs send Ethernet frames to GEM ports based on configured rules that map service ports and GEM ports.
2. GEM ports encapsulate the Ethernet frames into GEM PDUs and add these PDUs to T-CONT queues based on rules that map GEM ports and T-CONT queues.
3. T-CONT queues use time slots based on DBA, then transmit upstream GEM PDUs to the OLT.
4. OLT decapsulates the GEM PDU, the original Ethernet frame is now seen.
5. OLT sends the Ethernet frames from a specified uplink port based on rules that map service ports and uplink ports.
## Protocol stack for the C/M-plane[^standardgpon]
The control and management plane in the GTC system consists of three parts: embedded OAM,
PLOAM and OMCI. The embedded OAM and PLOAM channels manage the functions of the PMD
and the GTC layers. The OMCI provides a uniform system for managing higher (service-defining)
layers.
{% include image.html file="quick-start/uplane.png" alt="The U-plane protocol stack and identification by Port-ID" caption="The U-plane protocol stack and identification by Port-ID" %}
## Configuration Methods[^zyxel]
Several methods are available for the installation and activation of the ONU.
– Method A: Match serial number and password.
– Method C: Match PLOAM password or serial number.
– Method C-autolock: Match serial number.
– Method D: Volatile auto provision by template.
– Method E: Non-volatile auto provision by template.
If the ONU is not legal, the ONU registration activation will fail, see [GPON Auth](/gpon-auth) for the ONU States.
## Protocol Stacks[^cisco],[^fs]
The GPON protocol has its own stack, just Ethernet or IP.
{% include image.html file="gpon.jpg" alt="PON DBA Abstraction" caption="PON DBA Abstraction" %}
### Ethernet over GEM[^standardgpon]
The Ethernet frames are carried directly in the GEM frame payload. The preamble and start frame delimiter (SFD) bytes are discarded prior to GEM encapsulation. Each Ethernet frame shall be mapped to a single GEM frame (as shown in Figure) or multiple GEM frames, in which case the fragmentation rules apply.
{% include image.html file="quick-start/gem_frame.jpg" alt="Frame structure for Ethernet mapping into GEM frame" caption="Frame structure for Ethernet mapping into GEM frame" %}
Resolves Ethernet frames and directly maps the data of Ethernet frames into the GEM payload. GEM frames automatically encapsulate header information.
1:1 alignment between an Ethernet Frame and GEM Frame.
## OMCI[^cisco]
- ONU Management and Control Interface (OMCI) messages are used to discover ONT/ONUs for management and control.
- These specialized messages are sent over dedicated GEM ports established between an OLT and an ONT/ONU.
- The OMCI protocol allows an OLT to:
* Establish and release connections with the ONT.
* Manage the UNIs on the ONT.
* Request configuration information and performance statistics.
* Autonomously alert events, such as a link failure.
- Key Points:
* Protocol runs over a GEM connection between the OLT and ONT.
* GEM connection is established while the ONT initializes.
* Protocol operation is asynchronous - OLT controller functions as a primary, ONT controller as secondary.
### Management Information Base (MIB) and Management entities (ME's)[^arsat]
MIBs (Management Information Base) formed by Management Entities (MEs) are used to fully describe the ONU configuration, status and several other actions.
OMCI constitutes the protocol which supports the set of actions performed over an ONU to create, delete and more on those MEs
- A Managed Entity (ME) is composed of attributes, actions and notifications defining its characteristics.
- Managed Entity (ME Class Value)
- Purpose of the entity
- Autonomously instantiated by the ONU or explicitly created by the OLT
- Relationship(s) with other managed entities
- Attributes: Attribute Definition
- ME id: provides a unique number for each instance of this managed entity.
- List of attributes: Attribute Number within ME determined by the order in which attributes are listed
- Actions: operations that may be performed on the entity (Create/Get/Set/Test, etc.)
- Notifications (Alarm, AVC, TCA, Test Result)
- There can be multiple instances of any Managed Entity: each instance has the same attributes, actions and notifications even though the values of the attributes may be different from one another.
### VEIP and PPTP[^huaweiveip],[^cdatatec]
According to the application, ONU can be divided into six types, namely SFU (Single Family Unit) ONU, HGU (Home Gateway Unit) ONU, MDU (Multi-Dwelling Unit) ONU, SBU (Single Business Unit) ONU, MTU (Multi-Tenant Unit) ONU and CBU (Cellular Backhaul Unit) ONU. However, only SFU (Single Family Unit) ONU and HGU (Home Gateway Unit) ONU are used by the end-users in practical applications.
HGU ONU takes the Virtual Ethernet Interface Point (VEIP) as an OMCI administrative domain and a non-OMCI administrative domain (like TR-069). At the switchover point of the data plane, the ME can be managed only through the OMCI and is visible to the non-OMCI management domain, but not manageable. Similarly, all UNI-side modules under the VEIP are invisible to and cannot be managed by the OMCI. They are visible and manageable only to the non-OMCI management domain. In addition, each ONU should have only one VEIP.
When the ONU uploads MIBs, the ONU reports only the mandatory MEs and supported optional MEs. It does not report the MEs related to LOID authentication, performance monitoring and T-CONT MEs of the OMCC channel.
The ONU should be used according to the device type and report either VEIP or PPTP during MIB upload. The SFU only uses and reports PPTP. VEIP should not be used. HGUs can only use and report VEIPs. PPTP should not be used. The OLT determines the ONU type based on the ONU Type attribute in ME:ONU Capability. Only one VEIP is allowed in each HGU. ONUs will report VEIP or PPTP (Physical Path Termination Point) when MIB is uploaded according to the type of the device, while HGUs can only use and report VEIP rather than PPTP. The OLT will judge the type of each ONU device according to the ONU type attribute in ONU capability.
{% include image.html file="quick-start/veip.jpg" alt="Service Process of HGU ONU" caption="Service Process of HGU ONU" %}
SFU ONUs only support the OMCI management domain. PPTP is what SFU uses and reports, while VEIP is not available. The processing mode of OMCI configured data flow is different from that of RG flow. For OMCI data flow, there is a one-to-one mapping between the GEM port on the WAN side and the UNI port on the LAN side. All data packets can pass through without MAC address learning or forwarding. Wireless interfaces are not allowed in OMCI.
SFU ONUs are designed for a single family unit with broadband access terminal function without a more complex home gateway function from the perspective of application and ONU capacity. SFU ONUs, mainly used in FTTH scenarios, typically have 1 or 4 Ethernet interfaces and are available for Ethernet / IP services, optional VoIP services (built-in IAD), or CATV services.
SFU ONUs work under bridging mode (layer 2 of ISO model), support multiple VLAN functions, and their Ethernet port can be configured and managed by the OLT through OMCI / OAM. Combined with a home gateway, SFU ONUs are good at providing strong service capability.
<hr>
[^standardgpon]: *G.984.3: Gigabit-capable passive optical networks (GPON): Transmission convergence layer specification* https://www.itu.int/rec/T-REC-G.984.3
[^fs]: *Comparison of EPON and GPON* https://community.fs.com/blog/comparison-of-epon-and-gpon.html
[^zyxel]: *GPON E2E Fundamentals*, Zyxel 2018
[^huawei]: *GPON Fundamentals*, Huawei 2010 http://jm.telecoms.free.fr/QCM_Fibre/GPON-Fundamentals_Huawei.pdf
[^broadbandforum]: *GPON in FTTx Broadband Deployments*, Broadband Forum 2010 https://www.broadband-forum.org/download/MR-246.pdf
[^wolon]: *Fiber SFP Module Compatibility with APC, UPC, PC* https://www.wolonte.com/news.asp?id=599
[^cisco]: *Understand GPON Technology* https://www.cisco.com/c/en/us/support/docs/switches/catalyst-pon-series/216230-understand-gpon-technology.html
[^medium]: *HTFuture: EPON vs GPON Standard* https://medium.com/@ivyhtfuture/epon-vs-gpon-standard-b8ec20c55bb3
[^telecom]: *Fifty Years of Fixed Optical Networks Evolution: A Survey of Architectural and Technological Developments in a Layered Approach* https://doi.org/10.3390/telecom3040035
[^huaweimultiplexing]: *GPON Principle---Data Multiplexing* https://forum.huawei.com/enterprise/en/gpon-principle-data-multiplexing/thread/458243-100181
[^huaweiveip]: *VEIP knowledge* https://forum.huawei.com/enterprise/en/veip-knowledge/thread/771975-100181
[^cdatatec]: *Differences between HGU ONU and SFU ONU* https://cdatatec.com/differences-hgu-onu-sfu-onu/
[^arsat]: *Gpon: Tecnology*, ARSAT
================================================
FILE: _gpon/gpon-auth.md
================================================
---
title: GPON Auth (ONU Online Status)
has_children: false
nav_order: 3
layout: default
---
The information on this page is taken from the GPON standard and information from the major vendors of GPON equipment, each individual item containing a verifiable citation in the standard. Feel free to cite this page as: `{{ page.title }}, Hack GPON. Available at: https://hack-gpon.org{{ page.url }}`.
# ONU activation state: `Ox`[^huawei],[^standardgpon]
The process for an unconfigured ONU to go online involves five states:
- **`O1` Initial:** the OLT sends a message to the ONU to start the ONU, and the ONU enters the standby state;
- **`O2` Standby:** After receiving the message, the ONU extracts the delimiter value, power level, and pre-allocated compensation delay from the message, and adjusts its configurations accordingly, to support subsequent information exchanges.
- **`O3` Serial number:** The OLT sends a serial number (SN) request to the ONU. The ONU sends its SN to the OLT. After receiving the ONU's SN, the OLT allocates a temporary ONU-ID to the ONU.
- **`O4` Ranging:** The OLT sends a ranging request to the ONU. After receiving the ranging request from the OLT, the ONU responds with a message carrying its SN and ONU-ID. The OLT calculates the compensation delay and sends it to the ONU in a message. After receiving the message, the ONU sets the compensation delay accordingly.
- **`O5` Operation:** The OLT sends a password request to the ONU. The ONU returns a password to the OLT.
- **`O6` Intermittent LODS state.**
- **`O7` Emergency Stop state.**
The password is not configured on the OLT: if the automatic discovery function is enabled on the OLT's PON port, the OLT reports an ONU auto-discovery alarm to the CLI or NMS. The ONU goes online normally only after being confirmed.
```mermaid
graph TD
O1[O1 Initial state] -->|Downstream Synchronization attained| O2[O2-03 Standby-Serial number]
O2 -->|Assign ONU-ID Ploam and Equalization delay assigned| O4[O4 Ranging State]
O4 -->|Ranging Time PLOAM and Equalization delay assigned| O5[O5 Operation]
O5 & O4 & O2 -->|Loss of downstream syncronizzation| O6[O6 Intermittent LODS state]
O2 ---->|Disable S/N Request| O7[O7 Emergency stop state]
O2 -->|Broadcast deactivate ONU-ID Request| O1
O4 --->|TO1 time expires| O2
O4 & O5 ---->|Disable S/N Request| O7
O7 ---->|Enable S/N Request| O1
O6 ---->|TO2 timer expires| O1
O6 -->|Downstream Synchronization restored| O5
O5 & O4 ---->|Deactive ONU-ID Request| O1
```
# Fake O5 Status[^anime4000]
There is a known issue with Alcatel/Nokia OLTs giving fake `O5` ONU Status, OLTs will hold OMCI Provisioning until correct OMCI Information is received.
This happens when the OLT detects that the ONT is `drunk`, so it tries to update the firmware before opening the GEM link. If this happens, the user has to try changing the software version or other data.
This is most likely to reduce logs from misconfigured ONTs and to be able to send updates automatically to ONTs.
<hr>
[^huawei]: *The Process for an ONU to go Online* https://forum.huawei.com/enterprise/en/the-process-for-an-onu-to-go-online-gpon-technical-posts-12/thread/462895-100181
[^standardgpon]: *G.984.3: Gigabit-capable passive optical networks (GPON): Transmission convergence layer specification* https://www.itu.int/rec/T-REC-G.984.3
[^anime4000]: *`O5` No Internet* https://github.com/Anime4000/RTL960x/blob/main/Docs/fakeO5.md
================================================
FILE: _gpon/mib.md
================================================
---
title: GPON MIB
has_children: false
nav_order: 3
layout: default
---
The OMCI standard is defined in a way such that suppliers can offer modular and incremental functionality to meet different levels of customer needs.
The [^G_988] and [^G_984_4] standards define the protocol needed to handle all the features of the PON specifications ([^G_984_1], [^G_987], [^G_9807_1], ...), as well as a number of services and functionalities.
The standard was born with B-PON, then modified with G-PON and separated with XGS-PON. OMCI supports interoperability, yet it allows for optional components and future extensions.
A protocol-independent MIB (Management Information Base) describes the exchange of information across OMCI [^G_988] and [^G_984_4]. This protocol is defined in terms of MEs. MEs are abstract representations of resources and services in an ONU. Only a small subset of the list of MEs is mandatory.
The existence of other MEs depends on the architecture and feature set supported by the vendor's [^G_988] and [^G_984_4]. Major ISPs and vendors have created their own extensions for MIBs [^att_open_omci], [^verizon_open_omci].
Each ME consists of an entry ID and zero, one or more instances. Each instance has its own ID, usually starting at 0, but this is not always the case. Every instance has one or more attributes, each characterised by ID, size and content.
Various MEs are often interrelated. Clause 8.2 of [^G_988] and [^G_984_4] shows the relationship graphs between the various MEs.
Clause 9 of [^G_988] and [^G_984_4] describes how the various MEs are created. There are formally 2 modes: a managed entity which is auto-instantiated by the ONT or a managed entity which is instantiated on explicit request by the OLT.
In each of the 2 cases the various MEs can be: (R), (W). Only for MEs auto-instantiated by the ONT there is also (R, W) while only for MEs auto-instantiated by the OLT there are also (R, Set-by-create), (W, Set-by-create), or (R, W, Set-by-create).
| Mode | Description [^G_984_4] |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| (R) | On instantiation of the managed entity (either autonomously or on request of the OLT via a create action), the ONT sets the attribute to a default value. The OLT can only read the value of the attribute. In case of an autonomous attribute value change, the ONT will send an attribute value change notification to the OLT. |
| (W) | On instantiation of the managed entity (either autonomously or on request of the OLT via a create action), the ONT sets the attribute to a default value. The OLT can only write the value of the attribute. In case of an autonomous attribute value change, the ONT will NOT send an attribute value change notification to the OLT. |
| (R, W) | On instantiation of the managed entity (either autonomously or on request of the OLT via a create action), the ONT sets the attribute to a default value. The OLT can both read and write the value of the attribute. In case of an autonomous attribute value change, the ONT will send an attribute value change notification to the OLT. |
| (R, Set-by-create) | On instantiation of the managed entity (by necessity on request of the OLT via a create action), the ONT sets the attribute to the value specified in the create command. Subsequently, the OLT can only read the value of the attribute. In case of an autonomous attribute value change, the ONT will send an attribute value change notification to the OLT. |
| (W, Set-by-create) | On instantiation of the managed entity (by necessity on request of the OLT via a create action), the ONT sets the attribute to the value specified in the create command. Subsequently, the OLT can only write the value of the attribute. In case of an autonomous attribute value change, the ONT will NOT send an attribute value change notification to the OLT. |
| (R, W, Set-by-create) | On instantiation of the managed entity (by necessity on request of the OLT via a create action), the ONT sets the attribute to the value specified in the create command. Subsequently, the OLT can both read and write the value of the attribute. In case of an autonomous attribute value change, the ONT will send an attribute value change notification to the OLT. |
The following table is the result of combining the various tables in Table 8-1, Table 11-2 of [^G_984_4], Table 8-1, Table 11.2.4-1 of [^G_988], Table 1 of [^att_open_omci], Table B1 of [^verizon_open_omci].
The new ME introduced in G.988 [^G_988] do not have a description because G.988 abolished a summary description. In the corresponding ITU Clauses, all attrubits are described, and their purpose.
| Managed entity ID | Managed entity | Description G.984[^G_984_4] | Clause G.984[^G_984_4] | Clause G.988[^G_988] | AT&T Open OMCI[^att_open_omci] | Verizon Open OMCI[^verizon_open_omci] | Required/optional G.984[^G_984_4] | Mandatory G.987[^G_987], G.9807.1[^G_9807_1] | Mandatory G.989[^G_988] | Mandatory G.986[^G_988] | Mandatory IEEE 802.3, 802.3av[^G_988] |
| ----------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | -------------------- | ------------------------------ | ------------------------------------- | --------------------------------- | -------------------------------------------- | ----------------------- | ----------------------- | ------------------------------------- |
| 1 | ONT[^B-PON] | | | | | | | | | | |
| 2 | ONU data | Used for OMCI MIB management | 9.1.3 | 9.1.3 | 5.1.3 | M | R | M | M | M | M |
| 3 | PON IF line cardholder | | | | | | | | | | |
| 4 | PON IF line card | | | | | | | | | | |
| 5 | Cardholder | Used for a circuit pack plug-in slot. Can also represent a virtual cardholder to distinguish types of ports in an integrated ONT | 9.1.5 | 9.1.5 | 5.1.5 | M | CR | M | M | | M |
| 6 | Circuit pack | Used for a plug-in circuit pack module. Can also represent a virtual circuit pack to distinguish types of ports in an integrated ONT | 9.1.6 | 9.1.6 | 5.1.6 | M | CR | | | | |
| 7 | Software image | Used for the software image of the ONT or its components that contain independently manageable software | 9.1.4 | 9.1.4 | 5.1.4 | M | R | M | M | | M |
| 8 | UNI[^B-PON] | | | | | | | | | | |
| 9 | TC Adapter[^B-PON] | | | | | | | | | | |
| 10 | Physical path termination point ATM UNI | | | | | | | | | | |
| 11 | Physical path termination point Ethernet UNI | Used for physical path termination point at the Ethernet UNI | 9.5.1 | 9.5.1 | 5.5.1 | M | CR | | | M | |
| 12 | Physical path termination point CES UNI | Used for physical path termination point at the CES UNI | 9.8.1 | 9.8.1 | | No | CR | | | | |
| 13 | Logical N × 64 kbit/s sub - port connection termination point (CTP) | Used as logical interface for structured CES | 9.8.2 | 9.8.2 | | No | CR | | | | |
| 14 | Interworking VCC termination point | Used for DSL ATM mode interworking | 9.13.4 | 9.13.4 | | No | CR | | | | |
| 15 | AAL 1 profile[^B-PON] | | | | | | | | | | |
| 16 | AAL 5 profile | Used for DSL ATM mode interworking | 9.13.5 | 9.13.5 | | No | CR | | | | N/A |
| 17 | AAL 1 protocol monitoring history data[^B-PON] | | | | | | | | | | |
| 18 | AAL 5 performance monitoring history data | Used for DSL ATM mode interworking | 9.13.6 | 9.13.6 | | No | CR | | | | N/A |
| 19 | AAL 2 profile | | | | | | | | | | |
| 20 | (Intentionally left blank) | | | | | | | | | | |
| 21 | (NOTE – In [^G_984_4] this was called CES service profile-G) | Used for CES services supported by the ONT | 9.8.3 | 9.8.3 | | No | CR | | | | |
| 22 | (Reserved) | | | | | | | | | | |
| 23 | CES physical interface performance monitoring history data | Used for CES interface performance monitoring | 9.8.4 | 9.8.4 | | No | O | | | | |
| 24 | Ethernet performance monitoring history data | Used for Ethernet interface performance monitoring | 9.5.2 | 9.5.2 | 5.5.2 | M | O | | | | |
| 25 | VP network CTP[^B-PON] | | | | | | | | | | |
| 26 | ATM VP cross-connection | | | | | | | | | | |
| 27 | Priority queue[^B-PON] | | | | | | | | | | |
| 28 | DBR/CBR traffic descriptor | | | | | | | | | | |
| 29 | UBR traffic descriptor | | | | | | | | | | |
| 30 | SBR1/VBR1 traffic descriptor | | | | | | | | | | |
| 31 | SBR2/VBR2 traffic descriptor | | | | | | | | | | |
| 32 | SBR3/VBR3 traffic descriptor | | | | | | | | | | |
| 33 | ABR traffic descriptor | | | | | | | | | | |
| 34 | GFR traffic descriptor | | | | | | | | | | |
| 35 | ABT/DT/IT traffic descriptor | | | | | | | | | | |
| 36 | UPC disagreement monitoring history data[^B-PON] | | | | | | | | | | |
| 37 | (Intentionally left blank) | | | | | | | | | | |
| 38 | ANI [^B-PON] | | | | | | | | | | |
| 39 | PON TC adapter | | | | | | | | | | |
| 40 | PON physical path termination point | | | | | | | | | | |
| 41 | TC adapter protocol monitoring history data | | | | | | | | | | |
| 42 | Threshold data[^B-PON] | | | | | | | | | | |
| 43 | Operator specific | | | | | | | | | | |
| 44 | Vendor specific | | | | | | | | | | |
| 45 | MAC bridge service profile | Used for MAC bridge supported by the ONT | 9.3.1 | 9.3.1 | 5.3.1 | M | CR | | | | |
| 46 | MAC bridge configuration data | Used for MAC bridge supported by the ONT | 9.3.2 | 9.3.2 | | M | CR | | | | |
| 47 | MAC bridge port configuration data | Used to organize and record data associated with a bridge port | 9.3.4 | 9.3.4 | 5.3.2 | M | CR | | | | |
| 48 | MAC bridge port designation data | Used for MAC bridge supported by the ONT | 9.3.5 | 9.3.5 | | No | CR | | | | |
| 49 | MAC bridge port filter table data | Used for MAC bridge supported by the ONT | 9.3.6 | 9.3.6 | | M | CR | | | | |
| 50 | MAC bridge port bridge table data | Used for MAC bridge supported by the ONT | 9.3.8 | 9.3.8 | | M | CR | | | | |
| 51 | MAC bridge performance monitoring history data | Used for MAC bridge performance monitoring | 9.3.3 | 9.3.3 | | M | O | | | | |
| 52 | MAC bridge port performance monitoring history data | Used for MAC bridge port performance monitoring | 9.3.9 | 9.3.9 | | M | O | | | | |
| 53 | Physical path termination point POTS UNI | Used for physical path trail termination point at the POTS UNI | 9.9.1 | 9.9.1 | 5.9.1 | M | CR | | | | |
| 54 | Voice CTP | | | | | | | | | | |
| 55 | Voice PM history data | | | | | | | | | | |
| 56 | AAL2 PVC profile[^B-PON] | | | | | | | | | | |
| 57 | AAL2 CPS protocol monitoring history data[^B-PON] | | | | | | | | | | |
| 58 | Voice service profile | Used for voice | 9.9.6 | 9.9.6 | 5.9.6 | No | CR | | | | |
| 59 | LES service profile | | | | | | | | | | |
| 60 | AAL2 SSCS parameter profile1 | | | | | | | | | | |
| 61 | AAL2 SSCS parameter profile2 | | | | | | | | | | |
| 62 | VP performance monitoring history data | Used for DSL ATM mode interworking | 9.13.10 | 9.13.10 | | No | CR | | | | |
| 63 | Traffic scheduler[^B-PON] | | | | | | | | | | |
| 64 | T-CONT buffer | | | | | | | | | | |
| 65 | UBR+ traffic descriptor | | | | | | | | | | |
| 66 | AAL2 SSCS protocol monitoring history data[^B-PON] | | | | | | | | | | |
| 67 | IP port configuration data | Used for IP port supported by the ONT | 9.4.3 | n/a | | M | CR | | | | |
| 68 | IP router service profile | Used for IP router supported by the ONT | 9.4.1 | n/a | | M | CR | | | | |
| 69 | IP router configuration data | Used for IP router supported by the ONT | 9.4.2 | n/a | | M | CR | | | | |
| 70 | IP router performance monitoring history data 1 | Used for IP router performance monitoring | 9.4.6 | n/a | | | O | | | | |
| 71 | IP router performance monitoring history data 2 | Used for IP router performance monitoring | 9.4.7 | n/a | | | O | | | | |
| 72 | ICMP performance monitoring history data 1 | Used for ICMP performance monitoring | 9.4.8 | n/a | | | O | | | | |
| 73 | ICMP performance monitoring history data 2 | Used for ICMP performance monitoring | 9.4.9 | n/a | | | O | | | | |
| 74 | IP route table | Used for IP router supported by the ONT | 9.4.4 | n/a | | M | CR | | | | |
| 75 | IP static routes | Used for IP router supported by the ONT | 9.4.5 | n/a | | M | CR | | | | |
| 76 | ARP service profile | Used for IP port supported by the ONT | 9.4.10 | n/a | | | CR | | | | |
| 77 | ARP configuration data | Used for IP port supported by the ONT | 9.4.11 | n/a | | | CR | | | | |
| 78 | VLAN tagging operation configuration data | | 9.3.12 | 9.3.12 | | No | | | | | |
| 79 | MAC bridge port filter pre - assign table | Used for Ethernet type filtering | 9.3.7 | 9.3.7 | | M | O | | | | |
| 80 | Physical path termination point ISDN UNI | Used for ISDN port supported by the ONT | 9.9.21 | n/a | | No | O | | | | |
| 81 | (Reserved) | | | | | | | | | | |
| 82 | Physical path termination point video UNI | Used for electrical video output port | 9.13.1 | 9.13.1 | | No | O | | | | |
| 83 | Physical path termination point LCT UNI | Used for local craft terminal port | 9.13.3 | 9.13.3 | | No | O | | | | |
| 84 | VLAN tagging filter data | Used for VLAN tagging | 9.3.11 | 9.3.11 | 5.3.4 | M | O | | | | |
| 85 | ONU[^B-PON] | | | | | | | | | | |
| 86 | ATM VC cross-connection | | | | | | | | | | |
| 87 | VC network CTP[^B-PON] | | | | | | | | | | |
| 88 | VC PM history data | | | | | | | | | | |
| 89 | Ethernet performance monitoring history data 2 | Used for Ethernet performance monitoring | 9.5.3 | 9.5.3 | | No | O | | | | |
| 90 | Physical path termination point video ANI | Used for optical RF video input port | 9.13.2 | 9.13.2 | | No | O | | | | |
| 91 | Physical path termination point IEEE 802.11 UNI | Used for 802.11 interface supported by the ONT | 9.6.1 | n/a | | | CR | | | | |
| 92 | IEEE 802.11 station management data 1 | Used for 802.11 interface supported by the ONT | 9.6.2 | n/a | | | CR | | | | |
| 93 | IEEE 802.11 station management data 2 | Used for 802.11 interface supported by the ONT | 9.6.3 | n/a | | | CR | | | | |
| 94 | IEEE 802.11 general purpose object | Used for 802.11 interface supported by the ONT | 9.6.4 | n/a | | | CR | | | | |
| 95 | IEEE 802.11 MAC and PHY operation and antenna data | Used for 802.11 interface supported by the ONT | 9.6.5 | n/a | | | CR | | | | |
| 96 | IEEE 802.11 performance monitoring history data | Used for 802.11 interface supported by the ONT | 9.6.7 | n/a | | | O | | | | |
| 97 | IEEE 802.11 PHY FHSS DSSS IR tables | Used for 802.11 interface supported by the ONT | 9.6.6 | n/a | | | CR | | | | |
| 98 | Physical path termination point xDSL UNI part 1 | Used for the physical path termination point at an xDSL CO modem | 9.7.1 | 9.7.1 | | No | CR | | | | |
| 99 | Physical path termination point xDSL UNI part 2 | Used for the physical path termination point at an xDSL CO modem | 9.7.2 | 9.7.2 | | No | CR | | | | |
| 100 | xDSL line inventory and status data part 1 | | 9.7.12 | 9.7.12 | | No | | | | | |
| 101 | xDSL line inventory and status data part 2 | Contains inventory and status information on an xDSL line | 9.7.13 | 9.7.13 | | No | CR | | | | |
| 102 | xDSL channel downstream status data | Contains status on a downstream xDSL channel | 9.7.19 | 9.7.19 | | No | CR | | | | |
| 103 | xDSL channel upstream status data | Contains status on an upstream xDSL channel | 9.7.20 | 9.7.20 | | No | CR | | | | |
| 104 | xDSL line configuration profile part 1 | Contains line parameters for an xDSL line | 9.7.3 | 9.7.3 | | No | CR | | | | |
| 105 | xDSL line configuration profile part 2 | Contains line parameters for an xDSL line | 9.7.4 | 9.7.4 | | No | CR | | | | |
| 106 | xDSL line configuration profile part 3 | Contains line parameters for an xDSL line | 9.7.5 | 9.7.5 | | No | CR | | | | |
| 107 | xDSL channel configuration profile | Contains configuration for an xDSL channel | 9.7.7 | 9.7.7 | | No | CR | | | | |
| 108 | xDSL subcarrier masking downstream profile | Contains masking information for the downstream subcarriers | 9.7.8 | 9.7.8 | | No | CR | | | | |
| 109 | xDSL subcarrier masking upstream profile | Contains masking information for the upstream subcarriers | 9.7.9 | 9.7.9 | | No | CR | | | | |
| 110 | xDSL PSD mask profile | Contains PSD masking information | 9.7.10 | 9.7.10 | | No | CR | | | | |
| 111 | xDSL downstream radio frequency interference (RFI) bands profile | Contains information on the downstream RFI bands | 9.7.11 | 9.7.11 | | No | CR | | | | |
| 112 | xDSL xTU-C performance monitoring history data | Performance monitoring data for an xDSL xTU-C modem path | 9.7.21 | 9.7.21 | | No | O | | | | |
| 113 | xDSL xTU-R performance monitoring history data | Performance monitoring data for an xDSL xTU-R modem path | 9.7.22 | 9.7.22 | | No | O | | | | |
| 114 | xDSL xTU-C channel performance monitoring history data | Performance monitoring data for an xDSL xTU-C channel | 9.7.23 | 9.7.23 | | No | O | | | | |
| 115 | xDSL xTU-R channel performance monitoring history data | Performance monitoring data for an xDSL xTU-R channel | 9.7.24 | 9.7.24 | | No | O | | | | |
| 116 | TC adaptor performance monitoring history data xDSL | Performance monitoring data for the xDSL ATM data path | 9.7.25 | 9.7.25 | | No | O | | | | |
| 117 | Physical path termination point VDSL UNI (ITU-T G.993.1 VDSL1) | | | | | | | | | | |
| 118 | VDSL VTU-O physical data | | | | | | | | | | |
| 119 | VDSL VTU-R physical data | | | | | | | | | | |
| 120 | VDSL channel data | | | | | | | | | | |
| 121 | VDSL line configuration profile | | | | | | | | | | |
| 122 | VDSL channel configuration profile | | | | | | | | | | |
| 123 | VDSL band plan configuration profile | | | | | | | | | | |
| 124 | VDSL VTU-O physical interface monitoring history data | | | | | | | | | | |
| 125 | VDSL VTU-R physical interface monitoring history data | | | | | | | | | | |
| 126 | VDSL VTU-O channel performance monitoring history data | | | | | | | | | | |
| 127 | VDSL VTU-R channel performance monitoring history data | | | | | | | | | | |
| 128 | Video return path service profile | Used for video return path management | 9.13.7 | n/a | | | CR | | | | |
| 129 | Video return path performance monitoring history data | Used for video return path management | 9.13.8 | n/a | | | CR | | | | |
| 130 | IEEE 802.1p mapper service profile | Used for 802.1p priority Ethernet UNI | 9.3.10 | 9.3.10 | 5.3.3 | M | CR | | | | |
| 131 | OLT-G | Used for OLT identification for interoperability facilitation | 9.12.2 | 9.12.2 | 5.12.2 | M | O | | | | |
| 132 | Multicast interworking VCC termination point | | | | | | | | | | |
| 133 | ONU power shedding | Used to control the power shedding service | 9.1.7 | 9.1.7 | 5.1.7 | M | CR | | | | |
| 134 | IP host config data | Used to define the Internet protocol service that may be used with a MAC bridge port. Member of IPHostData group | 9.4.12 | 9.4.1 | 5.4.1 | | CR | | | | |
| 135 | IP host performance monitoring history data | Used to hold PM counters and alarms for the IP host. Member of IPHostData group | 9.4.13 | 9.4.2 | 5.4.2 | | O | | | | |
| 136 | TCP/UDP config data | Used for the TCP or UDP configuration for a TCP/UDP service. Member of IPHostData group | 9.4.14 | 9.4.3 | 5.4.3 | | CR | | | | |
| 137 | Network address | Used to bind a network address (URI, IP address) to its associated security method. Member of IPHostData group | 9.12.3 | 9.12.3 | 5.12.3 | M | CR | | | | |
| 138 | VoIP config data | Used to discover VoIP signalling protocols supported and select a VoIP signalling to use. Also used to select a VoIP configuration method. Member of VoIPData group | 9.9.18 | 9.9.18 | 5.9.12 | M | CR | | | | |
| 139 | VoIP voice CTP | Used for VoIP voice channel termination point. Member of VoIPData group | 9.9.4 | 9.9.4 | 5.9.4 | No | CR | | | | |
| 140 | Call control performance monitoring history data | Used for call control performance monitoring history. Member of VoIPData group | 9.9.12 | 9.9.12 | | M | O | | | | |
| 141 | VoIP line status | Used for VoIP line status that relates to a POTS port. Member of VoIPData group | 9.9.11 | 9.9.11 | | M | O | | | | |
| 142 | VoIP media profile | Used to define codec and other media selection criteria. Member of VoIPData group | 9.9.5 | 9.9.5 | 5.9.5 | No | CR | | | | |
| 143 | RTP profile data | Used for RTP configuration for VoIP service | 9.9.7 | 9.9.7 | 5.9.7 | No | CR | | | | |
| 144 | RTP performance monitoring history data | Used to hold the last completed 15 minutes interval PM data for RTP. Member of VoIPData group | 9.9.13 | 9.9.13 | | M | O | | | | |
| 145 | Network dial plan table | Used to support network-defined dial plans. Member of VoIPData group | 9.9.10 | 9.9.10 | | No | O | | | | |
| 146 | VoIP application service profile | Used for VoIP calling feature services. Member of VoIPData group | 9.9.8 | 9.9.8 | | No | O | | | | |
| 147 | VoIP feature access codes | Used to define feature access codes for a POTS port. Member of VoIPData group | 9.9.9 | 9.9.9 | | No | O | | | | |
| 148 | Authentication security method | Used for the user id/password configuration to associate an IP session between the client and destination server | 9.12.4 | 9.12.4 | 5.12.4 | M | O | | | | |
| 149 | SIP config portal | Used to view SIP configuration when the IP path is being used to manage SIP. Member of SIPrelatedData group | 9.9.19 | 9.9.19 | | M | CR | | | | |
| 150 | SIP agent config data | Used to define a VoIP SIP agent configuration. Member of SIPrelatedData group | 9.9.3 | 9.9.3 | 5.9.3 | No | CR | | | | |
| 151 | SIP agent performance monitoring history data | Used for statistics for the VoIP SIP agent. Member of SIPrelatedData group | 9.9.14 | 9.9.14 | 5.9.8 | M | O | | | | |
| 152 | SIP call initiation performance monitoring history data | Used for statistics for the VoIP SIP agent. Member of SIPrelatedData group | 9.9.15 | 9.9.15 | 5.9.9 | M | O | | | | |
| 153 | SIP user data | Used for user (subscriber) specific SIP data. Member of SIPrelatedData group | 9.9.2 | 9.9.2 | 5.9.2 | No | CR | | | | |
| 154 | MGC config portal | Used to view H.248 configuration when the IP path is being used to manage H.248. Member of H248relatedData group | 9.9.20 | 9.9.20 | | M | CR | | | | |
| 155 | MGC config data | Used for configuration data associated with an MGC client. Member of H248relatedData group | 9.9.16 | 9.9.16 | 5.9.10 | M | CR | | | | |
| 156 | MGC performance monitoring history data | Used for run-time attributes and statistics associated with an active MGC client. Member of H248relatedData group | 9.9.17 | 9.9.17 | 5.9.11 | M | O | | | | |
| 157 | Large string | Used to hold a character string larger than 25 bytes and up to 375 bytes | 9.12.5 | 9.12.5 | 5.12.5 | M | CR | | | | |
| 158 | ONU remote debug | Used to allow remote debugging of an ONT | 9.1.12 | 9.1.12 | 5.1.8 | M | CR | | | | |
| 159 | Equipment protection profile | Defines equipment protection groups | 9.1.11 | 9.1.11 | | M | CR | | | | |
| 160 | Equipment extension package | Used for additional attributes that may be associated with an ONT or cardholder | 9.1.9 | 9.1.9 | | No | O | | | | |
| 161 | Port-mapping package[^B-PON] (use 297 for G-PON) | | | | | | | | | | |
| 162 | Physical path termination point MoCA UNI | Used for the physical path termination point for MoCA interfaces | 9.10.1 | 9.10.1 | | No | CR | | | | |
| 163 | MoCA Ethernet performance monitoring history data | Performance monitoring data for the Ethernet layer on the MoCA interface | 9.10.2 | 9.10.2 | | No | O | | | | |
| 164 | MoCA interface performance monitoring history data | Performance monitoring data for the physical layer on the MoCA interface | 9.10.3 | 9.10.3 | | No | O | | | | |
| 165 | VDSL2 line configuration extensions | Contains xDSL attributes unique to VDSL2 (G.993.2) | 9.7.6 | 9.7.6 | | No | CR | | | | |
| 166 | xDSL line inventory and status data part 3 | Contains additional test and status attributes for xDSL lines | 9.7.14 | 9.7.14 | | No | CR | | | | |
| 167 | xDSL line inventory and status data part 4 | Contains additional test and status attributes for xDSL lines | 9.7.15 | 9.7.15 | | No | CR | | | | |
| 168 | VDSL2 line inventory and status data part 1 | Contains additional test and status attributes for xDSL lines, specifically, extensions for VDSL2 | 9.7.16 | 9.7.16 | | No | CR | | | | |
| 169 | VDSL2 line inventory and status data part 2 | Contains additional test and status attributes for xDSL lines, specifically, extensions for VDSL2 | 9.7.17 | 9.7.17 | | No | CR | | | | |
| 170 | VDSL2 line inventory and status data part 3 | Contains additional test and status attributes for xDSL lines, specifically, extensions for VDSL2 | 9.7.18 | 9.7.18 | | No | CR | | | | |
| 171 | Extended VLAN tagging operation configuration data | Contains configuration parameters for enhanced VLAN operations, including adding, removing and changing multiple tags | 9.3.13 | 9.3.13 | 5.3.5 | M | CR | | | | |
| 172-239 | Reserved for future [^B-PON] managed entities | | | | | | | | | | |
| 240-255 | Reserved for vendor-specific managed entities | | | | | | | | | | |
| 256 | ONU-G (NOTE – In [^G_984_4] this was called ONT-G) | Used for ONT equipment management | 9.1.1 | 9.1.2 | 5.1.1 | M | R | M | M | | M |
| 257 | ONU2-G (NOTE – In [^G_984_4] this was called ONT2-G) | Used for ONT equipment management | 9.1.2 | 9.1.1 | 5.1.2 | M | R | M | M | | M |
| 258 | ONU-G (deprecated – note that the name is re-used for code point 256) | | | | | | | | | | |
| 259 | ONU2-G (deprecated – note that the name is re-used for code point 257) | | | | | | | | | | |
| 260 | PON IF line card-G | | | | | | | | | | |
| 261 | PON TC adapter-G | | | | | | | | | | |
| 262 | T-CONT | Used for DBA | 9.2.2 | 9.2.2 | 5.2.2 | M | R | M | M | | M |
| 263 | ANI-G | Used for ANI management | 9.2.1 | 9.2.1 | 5.2.1 | M | R | M | M | | M |
| 264 | UNI-G | Used for user network interface for GEM service | 9.12.1 | 9.12.1 | 5.12.1 | M | CR | | | | |
| 265 | ATM interworking VCC termination point | | | | | | | | | | |
| 266 | GEM interworking termination point | Used for non-ATM UNIs and GEM-based connections | 9.2.4 | 9.2.4 | 5.2.4 | M | CR | M | M | | M/E |
| 267 | GEM port performance monitoring history data (obsolete) | Used for GEM port performance monitoring | 9.2.6 | n/a | | | O | | | | |
| 268 | GEM port network CTP | Used for GEM port termination | 9.2.3 | 9.2.3 | 5.2.3 | M | CR | M | M | | M/E |
| 269 | VP network CTP (NOTE – In [^G_984_4] this was called VP network CTP-G) | Used for DSL ATM mode interworking | 9.13.9 | 9.13.9 | | No | CR | | | | |
| 270 | VC network CTP-G | | | | | | | | | | |
| 271 | GAL TDM profile (deprecated) | Used when the ONT supports GAL TDM | 9.2.9 | n/a | | M | O | | | | |
| 272 | GAL Ethernet profile | Used when the ONT supports GAL Ethernet | 9.2.7 | 9.2.7 | 5.2.6 | M | O | | | | N/A |
| 273 | Threshold data 1 | Used for PM threshold values | 9.12.6 | 9.12.6 | 5.12.6 | M | CR | | | | |
| 274 | Threshold data 2 | Used for PM threshold values | 9.12.7 | 9.12.7 | 5.12.7 | M | CR | | | | |
| 275 | GAL TDM performance monitoring history data (deprecated) | Used when GAL TDM layer performance monitoring is supported | 9.2.10 | n/a | | M | O | | | | |
| 276 | GAL Ethernet performance monitoring history data | Used when GAL Ethernet layer performance monitoring is supported | 9.2.8 | 9.2.8 | | M | O | | | | N/A |
| 277 | Priority queue (NOTE – In [^G_984_4] this was called Priority queue-G) | Used for ONTs that support priority queues to multiplex ATM or GEM traffic flows | 9.11.1 | 9.2.10 | 5.2.8 | | CR | | | | |
| 278 | Traffic scheduler (NOTE – In [^G_984_4] this was called Traffic scheduler-G) | Used for DBA | 9.11.2 | 9.2.11 | 5.2.9 | | CR | | | | |
| 279 | Protection data | Used for PON protection | 9.1.10 | 9.1.10 | | M | CR | | | | |
| 280 | Traffic descriptor (NOTE – In [^G_984_4] this was called GEM traffic descriptor) | Used for GEM-based connections | 9.11.3 | 9.2.12 | 5.2.10 | | CR | | | | |
| 281 | Multicast GEM interworking termination point | Used to manage multicasting support for GEM connection | 9.2.5 | 9.2.5 | 5.2.5 | M | CR | | | | |
| 282 | Pseudowire termination point | Used when the ONT supports the pseudowire function | 9.8.5 | 9.8.5 | | No | CR | | | | |
| 283 | RTP pseudowire parameters | Used when the ONT supports the pseudowire function | 9.8.6 | 9.8.6 | | No | CR | | | | |
| 284 | Pseudowire maintenance profile | Used when the ONT supports the pseudowire function | 9.8.7 | 9.8.7 | | No | CR | | | | |
| 285 | Pseudowire performance monitoring history data | Used when the ONT supports the pseudowire function | 9.8.8 | 9.8.8 | | No | CR | | | | |
| 286 | Ethernet flow termination point | Used when the ONT supports the pseudowire function over layer 2 | 9.8.9 | 9.8.9 | | No | CR | | | | |
| 287 | OMCI | Used when OMCI self-description is supported | 9.12.8 | 9.12.8 | 5.12.8 | No | CR | | | | |
| 288 | Managed entity | Used when OMCI self-description is supported | 9.12.9 | 9.12.9 | | No | CR | | | | |
| 289 | Attribute | Used when OMCI self-description is supported | 9.12.10 | 9.12.10 | | No | CR | | | | |
| 290 | Dot1X port extension package | Used for 802.1X control | 9.3.14 | 9.3.14 | 5.3.6 | No | CR | | | | |
| 291 | Dot1X configuration profile | Used for 802.1X control | 9.3.15 | 9.3.15 | | No | CR | | | | |
| 292 | Dot1X performance monitoring history data | Used for 802.1X control | 9.3.16 | 9.3.16 | | No | CR | | | | |
| 293 | Radius performance monitoring history data | Used for 802.1X radius client PM | 9.3.17 | 9.3.17 | | No | CR | | | | |
| 294 | TU CTP | Organizes data that describes the VC path adaptation processing functions of the ONT for SDH services | 9.8.10 | n/a | | | CR | | | | |
| 295 | TU performance monitoring history data | Performance monitoring data collected as a result of TU connection monitoring | 9.8.11 | n/a | | | O | | | | |
| 296 | Ethernet performance monitoring history data 3 | Used for Ethernet performance monitoring (RMON) | 9.5.4 | 9.5.4 | | No | O | | | | |
| 297 | Port-mapping package (NOTE – In [^G_984_4] this was called Port mapping package-G) | Used to map heterogeneous ports to an equipment entity | 9.1.8 | 9.1.8 | | M | O | | | | |
| 298 | Dot1 rate limiter | Provides for limiting and policing upstream traffic | 9.3.18 | 9.3.18 | | M | CR | | | | |
| 299 | Dot1ag maintenance domain | Supports 802.1ag configuration fault management | 9.3.19 | 9.3.19 | 5.3.7 | M | O | | | | |
| 300 | Dot1ag maintenance association | Supports 802.1ag configuration fault management | 9.3.20 | 9.3.20 | 5.3.8 | M | O | | | | |
| 301 | Dot1ag default MD level | Supports 802.1ag configuration fault management | 9.3.21 | 9.3.21 | | M | O | | | | |
| 302 | Dot1ag MEP | Supports 802.1ag configuration fault management | 9.3.22 | 9.3.22 | 5.3.9 | M | O | | | | |
| 303 | Dot1ag MEP status | Supports 802.1ag configuration fault management | 9.3.23 | 9.3.23 | | M | O | | | | |
| 304 | Dot1ag MEP CCM database | Supports 802.1ag configuration fault management | 9.3.24 | 9.3.24 | | M | O | | | | |
| 305 | Dot1ag CFM stack | Supports 802.1ag configuration fault management | 9.3.25 | 9.3.25 | 5.3.10 | M | O | | | | |
| 306 | Dot1ag chassis - management info | Supports 802.1ag configuration fault management | 9.3.26 | 9.3.26 | | M | O | | | | |
| 307 | Octet string | Allows for strings of up to 375 arbitrary octet values | 9.12.11 | 9.12.11 | | M | O | | | | |
| 308 | General purpose buffer | Used to return large blocks of data; structure defined with each specific application | 9.12.12 | 9.12.12 | | M | O | | | | |
| 309 | Multicast operations profile | Used to manage multicast at the ONT | 9.3.27 | 9.3.27 | 5.3.11 | M | CR | | | | |
| 310 | Multicast subscriber config info | Used to manage multicast at the ONT | 9.3.28 | 9.3.28 | 5.3.12 | M | CR | | | | |
| 311 | Multicast subscriber monitor | Used to manage multicast at the ONT | 9.3.29 | 9.3.29 | | M | O | | | | |
| 312 | FEC performance monitoring history data | Performance monitoring data for FEC on an ANI-G | 9.2.11 | 9.2.9 | 5.2.7 | M | O | | | | |
| 313 | RE ANI-G | | n/a | 9.14.1 | | | | | | | |
| 314 | Physical path termination point RE UNI | | n/a | 9.14.2 | | | | | | | |
| 315 | RE upstream amplifier | | n/a | 9.14.3 | | | | | | | |
| 316 | RE downstream amplifier | | n/a | 9.14.4 | | | | | | | |
| 317 | RE config portal | | n/a | 9.14.5 | | | | | | | |
| 318 | File transfer controller | | n/a | 9.12.13 | | | | | | | |
| 319 | CES physical interface performance monitoring history data 2 | | n/a | 9.8.12 | | | | | | | |
| 319 | CES physical interface performance monitoring history data 2 | | n/a | 9.8.12 | | | | | | | |
| 320 | CES physical interface performance monitoring history data 3 | | n/a | 9.8.13 | | | | | | | |
| 321 | Ethernet frame performance monitoring history data downstream | | n/a | 9.3.31 | 5.3.13 | | | | | | |
| 322 | Ethernet frame performance monitoring history data upstream | | n/a | 9.3.30 | 5.3.14 | | | | | | |
| 323 | VDSL2 line configuration extensions 2 | | n/a | 9.7.26 | | | | | | | |
| 324 | xDSL impulse noise monitor performance monitoring history data | | n/a | 9.7.27 | | | | | | | |
| 325 | xDSL line inventory and status data part 5 | | n/a | 9.7.28 | | | | | | | |
| 326 | xDSL line inventory and status data part 6 | | n/a | 9.7.29 | | | | | | | |
| 327 | xDSL line inventory and status data part 7 | | n/a | 9.7.30 | | | | | | | |
| 328 | RE common amplifier parameters | | n/a | 9.14.6 | | | | | | | |
| 329 | Virtual Ethernet interface point | | n/a | 9.5.5 | 5.5.3 | | | | | | |
| 330 | Generic status portal | | n/a | 9.12.14 | | | | | | | |
| 331 | ONU-E | | n/a | 9.1.13 | | | | | | M | N/A |
| 332 | Enhanced security control |
gitextract_epc6vhe9/ ├── .github/ │ └── workflows/ │ ├── notify-telegram-pr.yml │ ├── pages.yml │ └── preview-pr.yaml ├── .gitignore ├── 404.md ├── CONTRIBUTING.md ├── Gemfile ├── LICENSE ├── README.md ├── _config.docker.yml ├── _config.yml ├── _gpon/ │ ├── g_984_series.md │ ├── gpon-auth.md │ ├── mib.md │ ├── ont.md │ ├── pptp_veip.md │ └── vendor.md ├── _includes/ │ ├── cig_password.html │ ├── cig_password_xgspon.html │ ├── head_custom.html │ ├── icons/ │ │ └── custom.html │ ├── image.html │ ├── root_lantiq.html │ ├── serial_dump.html │ └── ymodem_lantiq.html ├── _layouts/ │ └── default.html ├── _ont/ │ ├── ont-adtran-sdx-611.md │ ├── ont-adtran-sdx-611q.md │ ├── ont-adtran-sdx-621i.md │ ├── ont-adtran.md │ ├── ont-bt-pon-bt-g711ax.md │ ├── ont-bt-pon.md │ ├── ont-calix-801gt.md │ ├── ont-calix-801gv2.md │ ├── ont-calix-gp1000g.md │ ├── ont-calix-gp1100g.md │ ├── ont-calix.md │ ├── ont-carlitoxxpro-cpgos03-0490-v1.md │ ├── ont-carlitoxxpro-cpgos03-0490-v2.md │ ├── ont-carlitoxxpro.md │ ├── ont-cig-g-97c1.md │ ├── ont-cig-g-97cm.md │ ├── ont-cig-g-97cp.md │ ├── ont-cig-g-97s.md │ ├── ont-cig-g-97sp.md │ ├── ont-cig.md │ ├── ont-d-link-dpn-100-rev-a2.md │ ├── ont-d-link-dpn-100-rev-c1.md │ ├── ont-d-link.md │ ├── ont-fibermall-gpon-onu-clb+.md │ ├── ont-fibermall-gpon-onu-stb+.md │ ├── ont-fibermall.md │ ├── ont-fs-com-gpon-onu-stick-with-mac.md │ ├── ont-fs-com-mod.md │ ├── ont-fs-com-onu1710-1g.md │ ├── ont-fs-com.md │ ├── ont-genexis-ft-g2110c-2.5g.md │ ├── ont-genexis-ft-g2110c.md │ ├── ont-genexis.md │ ├── ont-halny-hl-gsfp.md │ ├── ont-halny.md │ ├── ont-hilink-hl23446.md │ ├── ont-hilink.md │ ├── ont-hisense-lte3415-sca+.md │ ├── ont-hisense-lte3415-sh+.md │ ├── ont-hisense.md │ ├── ont-huawei-eg8010h.md │ ├── ont-huawei-eg8010n.md │ ├── ont-huawei-hg8010h.md │ ├── ont-huawei-hg8110h.md │ ├── ont-huawei-hg8240h.md │ ├── ont-huawei-ma5671a-carlito.md │ ├── ont-huawei-ma5671a-fs-mod.md │ ├── ont-huawei-ma5671a-root-web.md │ ├── ont-huawei-ma5671a-root.md │ ├── ont-huawei-ma5671a-rooted.md │ ├── ont-huawei-ma5671a-sf.md │ ├── ont-huawei-ma5671a-ymodem.md │ ├── ont-huawei-ma5671a.md │ ├── ont-huawei-useful-command.md │ ├── ont-huawei.md │ ├── ont-kaon-pg1892g.md │ ├── ont-kaon.md │ ├── ont-leox-lxt-010g-d.md │ ├── ont-leox-lxt-010h-d.md │ ├── ont-leox-lxt-010s-h.md │ ├── ont-leox-lxt-240g-c1.md │ ├── ont-leox.md │ ├── ont-luna-sdk-useful-commands.md │ ├── ont-nokia-g-010g-a.md │ ├── ont-nokia-g-010g-d.md │ ├── ont-nokia-g-010g-p.md │ ├── ont-nokia-g-010g-q.md │ ├── ont-nokia-g-010g-r.md │ ├── ont-nokia-g-010g-t.md │ ├── ont-nokia-g-010s-a.md │ ├── ont-nokia-g-010s-b.md │ ├── ont-nokia-g-010s-p.md │ ├── ont-nokia-g-010s-q.md │ ├── ont-nokia-use.md │ ├── ont-nokia-useful-command.md │ ├── ont-nokia.md │ ├── ont-odi-realtek-dfp-34g-2c2.md │ ├── ont-odi-realtek-dfp-34x-2c2.md │ ├── ont-odi-zte-dfp-34g-2c2.md │ ├── ont-odi-zte-dfp-34x-2c2.md │ ├── ont-odi.md │ ├── ont-sercomm-fg1000b-11.md │ ├── ont-sercomm-fg1000b.md │ ├── ont-sercomm-fg1000r.md │ ├── ont-sercomm-fgs202.md │ ├── ont-sercomm.md │ ├── ont-sourcephotonics-sps-34-24t-hp-tdfm.md │ ├── ont-sourcephotonics-sps-34-24t-hp-tdfo.md │ ├── ont-sourcephotonics.md │ ├── ont-t-w-tw2362h-cdel.md │ ├── ont-t-w-twcgpon657.md │ ├── ont-t-w.md │ ├── ont-technicolor-afm0002.md │ ├── ont-technicolor-afm0003.md │ ├── ont-technicolor.md │ ├── ont-template.md │ ├── ont-tplink-xz000-g3.md │ ├── ont-tplink.md │ ├── ont-ufiber-uf-instant.md │ ├── ont-ufiber-uf-loco.md │ ├── ont-ufiber-uf-nano.md │ ├── ont-ufiber-wave-fiber-onu.md │ ├── ont-ufiber.md │ ├── ont-uplink-gp502r.md │ ├── ont-uplink.md │ ├── ont-vsol-v2801f.md │ ├── ont-vsol-v2801q.md │ ├── ont-vsol-v2802rh.md │ ├── ont-vsol.md │ ├── ont-yotc-m2-2050-g40.md │ ├── ont-yotc.md │ ├── ont-zisa-op151s.md │ ├── ont-zisa.md │ ├── ont-zte-f6005.md │ ├── ont-zte-f6005v3.md │ ├── ont-zte-f601.md │ ├── ont-zte.md │ ├── ont-zyxel-pmg1005-t20b.md │ ├── ont-zyxel-pmg3000-d20b.md │ ├── ont-zyxel-pmg3100-t0.md │ ├── ont-zyxel-pmg5100-t0.md │ ├── ont-zyxel-pmg5318.md │ ├── ont-zyxel.md │ └── serial_dump/ │ ├── fg1000b-11_boot_cfe.txt │ ├── fs-com-onu1710-1g/ │ │ ├── bootlog.txt │ │ └── uboot-env.txt │ ├── ma5671a_minishell.txt │ ├── yotcm2-2050-g40.txt │ └── yotcm2-2050-g40newrevision.txt ├── _ont_epon/ │ ├── bcctv.md │ ├── bcctv_PNC11C.md │ ├── free_iliad.md │ ├── free_iliad_F-MDCONU3A.md │ ├── free_iliad_F-MDCONU5A.md │ └── free_iliad_P-MDONU4B.md ├── _ont_xgs/ │ ├── ont-ALL-BM410-XGSPON-GBIC.md │ ├── ont-ECIN-EN-XGSFPP-OMAC-v1.md │ ├── ont-allnet.md │ ├── ont-cig-XG-99S.md │ ├── ont-cig.md │ ├── ont-ecin.md │ ├── ont-fs-XGS-ONU-25-20NI-cli.md │ ├── ont-fs-XGS-ONU-25-20NI.md │ ├── ont-fs-com.md │ ├── ont-hisense-ltf7267-bha+.md │ ├── ont-hisense.md │ ├── ont-huawei-hn8010ts.md │ ├── ont-huawei-useful-command.md │ ├── ont-huawei.md │ ├── ont-nokia-use.md │ ├── ont-nokia-useful-command.md │ ├── ont-nokia-xs-010s-q.md │ ├── ont-nokia-xs-010x-q.md │ ├── ont-nokia.md │ ├── ont-zte-f2801s.md │ ├── ont-zte.md │ ├── ont-zyxel-pm7300-t0.md │ ├── ont-zyxel.md │ └── serial_dump/ │ └── fs-XGS-ONU-25-20NI_minishell.txt ├── _router_pon/ │ ├── avm.md │ ├── avm_fritzbox.md │ ├── avm_fritzbox_5530.md │ ├── avm_fritzbox_5590.md │ ├── free_iliad.md │ ├── free_iliad_box_pop.md │ ├── ont-zte-f6645p.md │ ├── ont-zte.md │ ├── tp_link.md │ ├── tp_link_xb432v.md │ └── tp_link_xx800v.md ├── _sass/ │ └── custom/ │ └── custom.scss ├── _sfp/ │ ├── bosa-tosa-rosa.md │ ├── ont-wo-mac.md │ └── sfp-standard.md ├── _sfp_cage/ │ ├── banana-pi.md │ ├── broadcom-57810s.md │ ├── digitus-10gbps-dn-82211.md │ ├── fiberethernet-media-converter-2.5.md │ ├── macchiatobin.md │ ├── mikrotik.md │ ├── tp-link.md │ ├── turris.md │ ├── ubiquiti.md │ ├── zte.md │ └── zyxel.md ├── _tools/ │ ├── ascii-hex.md │ ├── gpon-omci-vlan-parser.md │ ├── molex-ont.md │ ├── ont-ethtool-print-eeprom.md │ ├── ont-lantiq-print-eeprom.md │ ├── speed-gpon-eth.md │ └── ttl-uart-adapter.md ├── assets/ │ ├── css/ │ │ ├── just-the-docs-dark.scss │ │ ├── just-the-docs-default.scss │ │ └── just-the-docs-light.scss │ ├── js/ │ │ ├── cigpassword.js │ │ ├── omci-vlan.js │ │ ├── rootLantiq.js │ │ ├── serialUtil.js │ │ ├── vue/ │ │ │ └── vue-lantiq-eeprom.vue │ │ ├── vue-eeprom.js │ │ └── xymini.js │ └── ts/ │ └── LTF7267-BHA-ploam.ts ├── bin/ │ └── just-the-docs ├── browserconfig.xml ├── docker-compose.yml ├── faq.md ├── index.md ├── package.json ├── privacy-policy.md ├── quick-start.md ├── rakefile ├── site.webmanifest └── tsup.config.ts
SYMBOL INDEX (46 symbols across 7 files)
FILE: assets/js/cigpassword.js
function hexToBytes (line 1) | function hexToBytes(hex) {
function cigpassword_gpon (line 9) | function cigpassword_gpon(ont_serial, ont_user, length = 0, xgspon = fal...
FILE: assets/js/omci-vlan.js
function hex2bin (line 6) | function hex2bin(hexString){
function binSpliceToDec (line 24) | function binSpliceToDec(binArray, len) {
function vlanTableParse (line 30) | function vlanTableParse(hexString) {
FILE: assets/js/rootLantiq.js
constant LOAD_ADDR (line 1) | const LOAD_ADDR = "80800000"
constant IMAGE0_ADDR (line 2) | const IMAGE0_ADDR = "C0000 740000";
constant IMAGE1_ADDR (line 3) | const IMAGE1_ADDR = "800000 800000";
function detectUboot (line 5) | async function detectUboot(serial) {
function waitUbootStop (line 13) | async function waitUbootStop(serial, sfpModel, outputMsgCallback) {
function checkUbootUnlocked (line 26) | async function checkUbootUnlocked(serial) {
function waitFailbackShell (line 39) | async function waitFailbackShell(serial, outputMsgCallback) {
function lantiqRootUboot (line 68) | async function lantiqRootUboot(port, sfpModel, outputMsgCallback, output...
function unlockHuaweiShell (line 110) | async function unlockHuaweiShell(port, outputMsgCallback, outputErrorCal...
function changeBaudrate (line 134) | async function changeBaudrate(port, newBaudrate, currBaudrate, outputErr...
function sendImageMtd (line 163) | async function sendImageMtd(port, data, baudRate, outputErrorCallback, p...
function waitEndImageLoad (line 179) | async function waitEndImageLoad(port, baudRate, outputErrorCallback) {
function flashImageMtd (line 199) | async function flashImageMtd(port, image, baudRate, outputErrorCallback) {
FILE: assets/js/serialUtil.js
function delay (line 1) | function delay(ms) {
class SerialReadWrite (line 5) | class SerialReadWrite {
method constructor (line 6) | constructor(port, baudrate) {
method openPort (line 14) | async openPort() {
method closePort (line 18) | async closePort() {
method readBytes (line 22) | async readBytes(retryError = 5, errorNum = 0) {
method readLine (line 63) | async readLine(readCallback, timeout = undefined) {
method writeBytes (line 117) | async writeBytes(bytes) {
method writeString (line 139) | async writeString(str) {
FILE: assets/js/vue-eeprom.js
method getFile (line 7) | getFile(url) {
method addStyle (line 12) | addStyle(styleStr) {
method log (line 18) | log(type, ...args) {
FILE: assets/js/xymini.js
constant STX (line 8) | const STX = 0x02;
constant ACK (line 9) | const ACK = 0x06;
constant NAK (line 10) | const NAK = 0x15;
constant EOF (line 11) | const EOF = 0x04;
constant XYMINI_1K_MAGIC (line 12) | const XYMINI_1K_MAGIC = 0x43;
constant PAYLOAD_LEN (line 13) | const PAYLOAD_LEN = 1024;
constant BLOCK_LEN (line 14) | const BLOCK_LEN = PAYLOAD_LEN + 5;
constant CRC_POLY (line 15) | const CRC_POLY = 0x1021;
function uint16 (line 17) | function uint16 (n) {
function updateCrc (line 21) | function updateCrc(crcIn, incr) {
function crc16 (line 36) | function crc16(data) {
function detectXYMini (line 52) | async function detectXYMini(serial) {
function generateXYMiniBlock (line 65) | function generateXYMiniBlock(blockId, payload) {
function sendXYMini (line 94) | async function sendXYMini(serial, data, progressCallback) {
FILE: assets/ts/LTF7267-BHA-ploam.ts
function hexEncode (line 1) | function hexEncode(str: String): String {
function hisensePloam (line 12) | function hisensePloam(ascii_ploam: String): String {
Condensed preview — 240 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (1,130K chars).
[
{
"path": ".github/workflows/notify-telegram-pr.yml",
"chars": 1061,
"preview": "name: notify-telegram-pr\n\non:\n pull_request_target:\n types: [opened, reopened]\n issues:\n types: [opened, reopene"
},
{
"path": ".github/workflows/pages.yml",
"chars": 1777,
"preview": "# Sample workflow for building and deploying a Jekyll site to GitHub Pages\nname: Deploy Jekyll site to Pages\n\non:\n # Ru"
},
{
"path": ".github/workflows/preview-pr.yaml",
"chars": 1298,
"preview": "name: preview-pr\n\non:\n pull_request_target:\n types: [opened, reopened, synchronize]\n \npermissions:\n pull-request"
},
{
"path": ".gitignore",
"chars": 146,
"preview": "### Jekyll ###\n_site/\n.sass-cache/\n.jekyll-cache/\n.jekyll-metadata\nGemfile.lock\nassets/js/zzzz-search-data.json\nnode_mod"
},
{
"path": "404.md",
"chars": 3434,
"preview": "---\nlayout: default\ntitle: Page not found\npermalink: /404\nnav_exclude: true\nsearch_exclude: true\ndescription: Opps. The "
},
{
"path": "CONTRIBUTING.md",
"chars": 9363,
"preview": "<!-- omit in toc -->\n# Contributing to Hack-Gpon\n\nFirst off, thanks for taking the time to contribute! ❤️\n\nAll types of "
},
{
"path": "Gemfile",
"chars": 307,
"preview": "source \"https://rubygems.org\"\n\n\ngem \"webrick\" \ngem \"rake\"\ngem \"json\"\n\ngroup :jekyll_plugins do\n gem \"jekyll-last-modi"
},
{
"path": "LICENSE",
"chars": 1066,
"preview": "MIT License\n\nCopyright (c) 2022 hack-gpon\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\n"
},
{
"path": "README.md",
"chars": 991,
"preview": "```\n _ _ _ ____ ____ ___ _ _ \n| | | | __ _ ___ | | __ / ___|| _ \\ / _ \\ | \\ | |\n| |_"
},
{
"path": "_config.docker.yml",
"chars": 29,
"preview": "url: \"http://localhost:4000\"\n"
},
{
"path": "_config.yml",
"chars": 4129,
"preview": "remote_theme: simonebortolin/just-the-docs\ntitle: \"Hack GPON\"\nbaseurl: \npermalink: '/:title'\nsearch_enabled: true\nsearch"
},
{
"path": "_gpon/g_984_series.md",
"chars": 22010,
"preview": "---\ntitle: GPON G.984 Series\nhas_children: false\nnav_order: 3\nlayout: default\n---\n\nThe information on this page is taken"
},
{
"path": "_gpon/gpon-auth.md",
"chars": 3483,
"preview": "---\ntitle: GPON Auth (ONU Online Status)\nhas_children: false\nnav_order: 3\nlayout: default\n---\n\nThe information on this p"
},
{
"path": "_gpon/mib.md",
"chars": 191328,
"preview": "---\ntitle: GPON MIB\nhas_children: false\nnav_order: 3\nlayout: default\n---\n\nThe OMCI standard is defined in a way such tha"
},
{
"path": "_gpon/ont.md",
"chars": 1928,
"preview": "---\ntitle: GPON ONT Chipset\nhas_children: false\nnav_order: 2\nlayout: default\n---\n\n\n# Major Chipset Manufacturers\n\nCurren"
},
{
"path": "_gpon/pptp_veip.md",
"chars": 8027,
"preview": "---\ntitle: GPON PPTP and VEIP \nhas_children: false\nnav_order: 3\nlayout: default\n---\n\nONTs are the terminating elements o"
},
{
"path": "_gpon/vendor.md",
"chars": 2879,
"preview": "---\ntitle: ONU Vendor ID\nhas_children: false\nnav_order: 4\nlayout: default\n---\n\n> 4 ASCII characters\n\nNeeds to be set for"
},
{
"path": "_includes/cig_password.html",
"chars": 2011,
"preview": "<div>\n <form id=\"cig-password\" novalidate>\n <div class=\"form-floating mb-3\">\n <input type=\"text\" cl"
},
{
"path": "_includes/cig_password_xgspon.html",
"chars": 2601,
"preview": "<div>\n <form id=\"cig-password\" novalidate>\n <div class=\"form-floating mb-3\">\n <input type=\"text\" cl"
},
{
"path": "_includes/head_custom.html",
"chars": 440,
"preview": "<link rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"/apple-touch-icon.png\">\n<link rel=\"icon\" type=\"image/png\" sizes=\"32x3"
},
{
"path": "_includes/icons/custom.html",
"chars": 1990,
"preview": "<symbol id=\"svg-telegram\" viewBox=\"0 0 16 16\">\n <title>Telegram</title>\n <svg xmlns=\"http://www.w3.org/2000/svg\" f"
},
{
"path": "_includes/image.html",
"chars": 517,
"preview": "<figure>\n {% if {{include.url}} %}\n <a class=\"no_icon\" target=\"_blank\" rel=\"noopener\" href=\"{{include.url}}\">\n"
},
{
"path": "_includes/root_lantiq.html",
"chars": 7216,
"preview": "<div class=\"modal\" data-jtd-modal=\"root-modal\" data-jtd-modal-backdrop=\"static\" id=\"root-modal\">\n <div class=\"modal-c"
},
{
"path": "_includes/serial_dump.html",
"chars": 379,
"preview": "\n<details>\n <summary>{{include.title}}</summary>\n <div class=\"language-plaintext highlighter-rouge\">\n <div "
},
{
"path": "_includes/ymodem_lantiq.html",
"chars": 8162,
"preview": "<div class=\"modal\" data-jtd-modal=\"flash-modal\" data-jtd-modal-backdrop=\"static\" id=\"flash-modal\">\n <div class=\"modal"
},
{
"path": "_layouts/default.html",
"chars": 14806,
"preview": "---\nlayout: table_wrappers\n---\n\n<!DOCTYPE html>\n\n<html lang=\"{{ site.lang | default: 'en-US' }}\">\n{% include head.html %"
},
{
"path": "_ont/ont-adtran-sdx-611.md",
"chars": 3457,
"preview": "---\ntitle: Adtran SDX 611\nhas_children: false\nlayout: default\nparent: Adtran\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-adtran-sdx-611q.md",
"chars": 714,
"preview": "---\ntitle: Adtran SDX 611Q\nhas_children: false\nlayout: default\nparent: Adtran\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-adtran-sdx-621i.md",
"chars": 1308,
"preview": "---\ntitle: Adtran SDX 621i\nhas_children: false\nlayout: default\nparent: Adtran\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-adtran.md",
"chars": 56,
"preview": "---\ntitle: Adtran\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-bt-pon-bt-g711ax.md",
"chars": 11004,
"preview": "---\r\ntitle: BT-PON BT-G711AX\r\nhas_children: false\r\nlayout: default\r\nparent: BT-PON\r\n---\r\n\r\n# Hardware Specifications\r\n\r\n"
},
{
"path": "_ont/ont-bt-pon.md",
"chars": 56,
"preview": "---\ntitle: BT-PON\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-calix-801gt.md",
"chars": 1252,
"preview": "---\ntitle: Calix 801GT\nhas_children: false\nlayout: default\nparent: Calix\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-calix-801gv2.md",
"chars": 1263,
"preview": "---\ntitle: Calix GigaPoint 801Gv2\nhas_children: false\nlayout: default\nparent: Calix\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-calix-gp1000g.md",
"chars": 1254,
"preview": "---\ntitle: Calix GP1000g\nhas_children: false\nlayout: default\nparent: Calix\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-calix-gp1100g.md",
"chars": 1254,
"preview": "---\ntitle: Calix GP1100G\nhas_children: false\nlayout: default\nparent: Calix\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-calix.md",
"chars": 55,
"preview": "---\ntitle: Calix\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-carlitoxxpro-cpgos03-0490-v1.md",
"chars": 133,
"preview": "---\ntitle: CarlitoxxPro CPGOS03-0490 v1\nhas_children: false\nredirect_to: /ont-hilink-hl23446\nlayout: default\nparent: Car"
},
{
"path": "_ont/ont-carlitoxxpro-cpgos03-0490-v2.md",
"chars": 1599,
"preview": "---\ntitle: CarlitoxxPro CPGOS03-0490 v2\nhas_children: false\nlayout: default\nparent: CarlitoxxPro\n---\n\n# Hardware Specifi"
},
{
"path": "_ont/ont-carlitoxxpro.md",
"chars": 62,
"preview": "---\ntitle: CarlitoxxPro\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-cig-g-97c1.md",
"chars": 106,
"preview": "---\ntitle: CIG G-97C1\nhas_children: false\nredirect_to: /ont-nokia-g-010g-p\nlayout: default\nparent: CIG\n---"
},
{
"path": "_ont/ont-cig-g-97cm.md",
"chars": 991,
"preview": "---\ntitle: CIG G-97CM\nhas_children: false\nlayout: default\nparent: CIG\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-cig-g-97cp.md",
"chars": 2455,
"preview": "---\ntitle: CIG G-97CP\nhas_children: false\nlayout: default\nparent: CIG\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-cig-g-97s.md",
"chars": 105,
"preview": "---\ntitle: CIG G-97S\nhas_children: false\nredirect_to: /ont-nokia-g-010s-q\nlayout: default\nparent: CIG\n---"
},
{
"path": "_ont/ont-cig-g-97sp.md",
"chars": 1102,
"preview": "---\ntitle: CIG G-97SP\nhas_children: false\nlayout: default\nparent: CIG\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-cig.md",
"chars": 59,
"preview": "---\ntitle: CIG\nhas_children: true\nlayout: default\n---\n\n\n\n\n\n"
},
{
"path": "_ont/ont-d-link-dpn-100-rev-a2.md",
"chars": 2236,
"preview": "---\ntitle: D-LINK DPN-100 Rev A2\nhas_children: false\nlayout: default\nparent: D-LINK\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-d-link-dpn-100-rev-c1.md",
"chars": 2214,
"preview": "---\ntitle: D-LINK DPN-100 Rev C1\nhas_children: false\nlayout: default\nparent: D-LINK\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-d-link.md",
"chars": 56,
"preview": "---\ntitle: D-LINK\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-fibermall-gpon-onu-clb+.md",
"chars": 10907,
"preview": "---\ntitle: FiberMall GPON-ONU-CLB+\nhas_children: false\nlayout: default\nparent: FiberMall\n---\n\n{% include alert.html cont"
},
{
"path": "_ont/ont-fibermall-gpon-onu-stb+.md",
"chars": 9591,
"preview": "---\ntitle: FiberMall GPON-ONU-STB+\nhas_children: false\nlayout: default\nparent: FiberMall\n---\n\n{% include alert.html cont"
},
{
"path": "_ont/ont-fibermall.md",
"chars": 60,
"preview": "---\ntitle: FiberMall\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont/ont-fs-com-gpon-onu-stick-with-mac.md",
"chars": 42506,
"preview": "---\ntitle: FS.com GPON ONU Stick with MAC (GPON-ONU-34-20BI)\nhas_children: true\nalias: SourcePhotonics SPS-34-24T-HP-TDF"
},
{
"path": "_ont/ont-fs-com-mod.md",
"chars": 219,
"preview": "---\ntitle: FS.com Modded Firmware for Huawei MA5671A and FS.com GPON-ONU-34-20BI\nhas_children: false\nredirect_to: /ont-h"
},
{
"path": "_ont/ont-fs-com-onu1710-1g.md",
"chars": 13428,
"preview": "---\ntitle: FS.com ONU1710-1G\nhas_children: false\nlayout: default\nparent: FS.com\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-fs-com.md",
"chars": 58,
"preview": "---\ntitle: FS.com \nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont/ont-genexis-ft-g2110c-2.5g.md",
"chars": 7241,
"preview": "---\ntitle: FiberTwist G2110C-2.5G\nhas_children: false\nlayout: default\nparent: Genexis\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-genexis-ft-g2110c.md",
"chars": 1591,
"preview": "---\ntitle: FiberTwist G2110C\nhas_children: false\nlayout: default\nparent: Genexis\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-genexis.md",
"chars": 58,
"preview": "---\ntitle: Genexis\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont/ont-halny-hl-gsfp.md",
"chars": 1908,
"preview": "---\ntitle: HALNy HL-GSFP\nhas_children: false\nlayout: default\nparent: HALNy\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-halny.md",
"chars": 55,
"preview": "---\ntitle: HALNy\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-hilink-hl23446.md",
"chars": 1892,
"preview": "---\ntitle: Hilink HL23446\nhas_children: false\nalias: CarlitoxxPro CPGOS03-0490 v1\nlayout: default\nparent: Hilink\n---\n\n# "
},
{
"path": "_ont/ont-hilink.md",
"chars": 56,
"preview": "---\ntitle: Hilink\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-hisense-lte3415-sca+.md",
"chars": 125,
"preview": "---\ntitle: HiSense LTE3415-SCA+\nhas_children: false\nredirect_to: /ont-technicolor-afm0002\nlayout: default\nparent: HiSens"
},
{
"path": "_ont/ont-hisense-lte3415-sh+.md",
"chars": 124,
"preview": "---\ntitle: HiSense LTE3415-SH+\nhas_children: false\nredirect_to: /ont-technicolor-afm0003\nlayout: default\nparent: HiSense"
},
{
"path": "_ont/ont-hisense.md",
"chars": 57,
"preview": "---\ntitle: HiSense\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-huawei-eg8010h.md",
"chars": 2357,
"preview": "---\ntitle: Huawei EG8010H \nhas_children: false\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-huawei-eg8010n.md",
"chars": 571,
"preview": "---\ntitle: Huawei EG8010N \nhas_children: false\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-huawei-hg8010h.md",
"chars": 4172,
"preview": "---\ntitle: Huawei HG8010H \nhas_children: false\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-huawei-hg8110h.md",
"chars": 1249,
"preview": "---\ntitle: Huawei HG8110H\nhas_children: false\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-huawei-hg8240h.md",
"chars": 1249,
"preview": "---\ntitle: Huawei HG8240H\nhas_children: false\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-huawei-ma5671a-carlito.md",
"chars": 2017,
"preview": "---\ntitle: Carlito Firmware for Huawei MA5671A\nhas_children: false\nparent: Huawei MA5671A\nlayout: default\n---\n\n{% includ"
},
{
"path": "_ont/ont-huawei-ma5671a-fs-mod.md",
"chars": 5556,
"preview": "---\ntitle: FS Modded Firmware for Huawei MA5671A and FS.com GPON-ONU-34-20BI\nhas_children: false\nparent: Huawei MA5671A\n"
},
{
"path": "_ont/ont-huawei-ma5671a-root-web.md",
"chars": 4269,
"preview": "---\ntitle: Root Procedure for Huawei MA5671A (V3)\nhas_children: false\nparent: Huawei MA5671A\nlayout: default\n---\n\n# Root"
},
{
"path": "_ont/ont-huawei-ma5671a-root.md",
"chars": 15994,
"preview": "---\ntitle: List of Root Procedure for Huawei MA5671A\ndescription: For documentation purposes only. This page contains th"
},
{
"path": "_ont/ont-huawei-ma5671a-rooted.md",
"chars": 4315,
"preview": "---\ntitle: Huawei Rooted Firmware for Huawei MA5671A\nhas_children: false\nparent: Huawei MA5671A\nlayout: default\n---\n\n# U"
},
{
"path": "_ont/ont-huawei-ma5671a-sf.md",
"chars": 166,
"preview": "---\ntitle: SourcePhotonics Firmware for Huawei MA5671A\nhas_children: false\nredirect_to: /ont-fs-com-gpon-onu-stick-with-"
},
{
"path": "_ont/ont-huawei-ma5671a-ymodem.md",
"chars": 980,
"preview": "---\ntitle: Root Procedure for Huawei MA5671A (flash firmware)\nhas_children: false\nparent: Huawei MA5671A\nlayout: default"
},
{
"path": "_ont/ont-huawei-ma5671a.md",
"chars": 33647,
"preview": "---\ntitle: Huawei MA5671A\nhas_children: true\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-huawei-useful-command.md",
"chars": 4787,
"preview": "## Enabling telnet\n\nWe need access to a specific shell and in order to get it enabling telnet is required. On the ONT, t"
},
{
"path": "_ont/ont-huawei.md",
"chars": 56,
"preview": "---\ntitle: Huawei\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-kaon-pg1892g.md",
"chars": 1215,
"preview": "---\ntitle: KAON PG1892G\nhas_children: false\nlayout: default\nparent: KAON\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-kaon.md",
"chars": 54,
"preview": "---\ntitle: KAON\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-leox-lxt-010g-d.md",
"chars": 1626,
"preview": "---\ntitle: LEOX LXT-010G-D\nhas_children: false\nlayout: default\nparent: LEOX\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-leox-lxt-010h-d.md",
"chars": 4526,
"preview": "---\ntitle: LEOX LXT-010H-D\nhas_children: false\nlayout: default\nparent: LEOX\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-leox-lxt-010s-h.md",
"chars": 4601,
"preview": "---\ntitle: LEOX LXT-010S-H\nhas_children: false\nlayout: default\nparent: LEOX\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-leox-lxt-240g-c1.md",
"chars": 5681,
"preview": "---\ntitle: LEOX LXT-240G-C1\nhas_children: false\nlayout: default\nparent: LEOX\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-leox.md",
"chars": 57,
"preview": "---\ntitle: LEOX\nhas_children: true\nlayout: default\n---\n\n\n"
},
{
"path": "_ont/ont-luna-sdk-useful-commands.md",
"chars": 8270,
"preview": "# Useful files and binaries\n\n## Useful files\n- `/var/config/lastgood.xml` - Contains the user portion of the configurati"
},
{
"path": "_ont/ont-nokia-g-010g-a.md",
"chars": 2023,
"preview": "---\ntitle: Nokia G-010G-A\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-nokia-g-010g-d.md",
"chars": 3522,
"preview": "---\ntitle: Nokia G-010G-D\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-nokia-g-010g-p.md",
"chars": 2590,
"preview": "---\ntitle: Nokia G-010G-P\nhas_children: false\nlayout: default\nparent: Nokia\nalias: CIG G-97C1/CIG G-97CU\n---\n\n# Hardware"
},
{
"path": "_ont/ont-nokia-g-010g-q.md",
"chars": 5268,
"preview": "---\ntitle: Nokia G-010G-Q\nhas_children: false\nlayout: default\nparent: Nokia\nalias: CIG G-97CU\n---\n\n# Hardware Specificat"
},
{
"path": "_ont/ont-nokia-g-010g-r.md",
"chars": 11340,
"preview": "---\ntitle: Nokia G-010G-R\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-nokia-g-010g-t.md",
"chars": 5691,
"preview": "---\ntitle: Nokia G-010G-T\nhas_children: false\nlayout: default\nparent: Nokia\nalias: CIG G-97CP/G-97CU\n---\n\n# Hardware Spe"
},
{
"path": "_ont/ont-nokia-g-010s-a.md",
"chars": 9076,
"preview": "---\ntitle: Nokia G-010S-A\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-nokia-g-010s-b.md",
"chars": 4037,
"preview": "---\ntitle: Nokia G-010S-B\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-nokia-g-010s-p.md",
"chars": 4549,
"preview": "---\ntitle: Nokia G-010S-P\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-nokia-g-010s-q.md",
"chars": 3376,
"preview": "---\ntitle: Nokia G-010S-Q\nhas_children: false\nlayout: default\nparent: Nokia\nalias: CIG G-97S\n---\n\n# Hardware Specificati"
},
{
"path": "_ont/ont-nokia-use.md",
"chars": 928,
"preview": "# Usage\n\n{% include alert.html content=include.alertUsage alert=\"Note\" icon=\"svg-info\" color=\"blue\" %}\n\n\n{% unless inclu"
},
{
"path": "_ont/ont-nokia-useful-command.md",
"chars": 3428,
"preview": "# GPON ONU status\n\n## Getting the operational status of the ONU\n```sh\n#ONT>traffic\n#ONT/system>pon\n#ONT/system/pon>show "
},
{
"path": "_ont/ont-nokia.md",
"chars": 55,
"preview": "---\ntitle: Nokia\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-odi-realtek-dfp-34g-2c2.md",
"chars": 4299,
"preview": "---\ntitle: ODI Realtek DFP-34G-2C2 \ndescription: New model 2022 - v05\nhas_children: false\nlayout: default\nparent: ODI\n--"
},
{
"path": "_ont/ont-odi-realtek-dfp-34x-2c2.md",
"chars": 4458,
"preview": "---\ntitle: ODI Realtek DFP-34X-2C2 \ndescription: New model 2022 - v05\nhas_children: false\nlayout: default\nparent: ODI\n--"
},
{
"path": "_ont/ont-odi-zte-dfp-34g-2c2.md",
"chars": 3062,
"preview": "---\ntitle: ODI ZTE DFP-34G-2C2\ndescription: Old model 2020 - v04\nhas_children: false\nlayout: default\nparent: ODI\nalias: "
},
{
"path": "_ont/ont-odi-zte-dfp-34x-2c2.md",
"chars": 172,
"preview": "---\ntitle: ODI ZTE DFP-34G-2C2\ndescription: Old model 2020 - v04\nhas_children: false\nlayout: default\nparent: ODI\nnav_exc"
},
{
"path": "_ont/ont-odi.md",
"chars": 53,
"preview": "---\ntitle: ODI\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-sercomm-fg1000b-11.md",
"chars": 124,
"preview": "---\r\ntitle: Sercomm FG1000B.11s\r\nhas_children: false\r\nredirect_to: /ont-sercomm-fg1000b\r\nlayout: default\r\nparent: CIG\r\n-"
},
{
"path": "_ont/ont-sercomm-fg1000b.md",
"chars": 17172,
"preview": "---\ntitle: Sercomm FG1000B\nhas_children: false\nlayout: default\nparent: Sercomm\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-sercomm-fg1000r.md",
"chars": 1693,
"preview": "---\ntitle: Sercomm FG1000R\nhas_children: false\nlayout: default\nparent: Sercomm\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-sercomm-fgs202.md",
"chars": 4881,
"preview": "---\ntitle: Sercomm FGS202\nhas_children: false\nlayout: default\nparent: Sercomm\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-sercomm.md",
"chars": 57,
"preview": "---\ntitle: Sercomm\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-sourcephotonics-sps-34-24t-hp-tdfm.md",
"chars": 1213,
"preview": "---\ntitle: SourcePhotonics SPS-34-24T-HP-TDFM\nhas_children: false\nlayout: default\nparent: SourcePhotonics\n---\n\n# Hardwar"
},
{
"path": "_ont/ont-sourcephotonics-sps-34-24t-hp-tdfo.md",
"chars": 158,
"preview": "---\ntitle: SourcePhotonics SPS-34-24T-HP-TDFO\nhas_children: false\nredirect_to: /ont-fs-com-gpon-onu-stick-with-mac\nlayou"
},
{
"path": "_ont/ont-sourcephotonics.md",
"chars": 65,
"preview": "---\ntitle: SourcePhotonics\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-t-w-tw2362h-cdel.md",
"chars": 109,
"preview": "---\ntitle: T&W TW2362H-CDEL\nhas_children: false\nredirect_to: /ont-zisa-op151s\nlayout: default\nparent: T&W\n---"
},
{
"path": "_ont/ont-t-w-twcgpon657.md",
"chars": 2208,
"preview": "---\ntitle: T&W TWC GPON657\nhas_children: false\nlayout: default\nparent: T&W\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-t-w.md",
"chars": 53,
"preview": "---\ntitle: T&W\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-technicolor-afm0002.md",
"chars": 12620,
"preview": "---\ntitle: Vantiva AFM0002 (formerly Technicolor AFM0002) \nhas_children: false\nlayout: default\nparent: Vantiva (formerly"
},
{
"path": "_ont/ont-technicolor-afm0003.md",
"chars": 5479,
"preview": "---\ntitle: Vantiva AFM0003 (formerly Technicolor AFM0003)\nhas_children: false\nlayout: default\nparent: Vantiva (formerly "
},
{
"path": "_ont/ont-technicolor.md",
"chars": 80,
"preview": "---\ntitle: Vantiva (formerly Technicolor)\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-template.md",
"chars": 3330,
"preview": "# Hardware Specifications\r\n\r\n| | |\r\n| ---------------- | ------"
},
{
"path": "_ont/ont-tplink-xz000-g3.md",
"chars": 1308,
"preview": "---\ntitle: TP-Link XZ000-G3\nhas_children: false\nlayout: default\nparent: TP-Link\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-tplink.md",
"chars": 59,
"preview": "---\ntitle: TP-Link\nhas_children: true\nlayout: default\n---\n\n"
},
{
"path": "_ont/ont-ufiber-uf-instant.md",
"chars": 2067,
"preview": "---\ntitle: UFiber UF-Instant\nhas_children: false\nlayout: default\nparent: UFiber\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-ufiber-uf-loco.md",
"chars": 1494,
"preview": "---\ntitle: UFiber Loco\nhas_children: false\nlayout: default\nparent: UFiber\n---\n\n{% include alert.html content=\"This devic"
},
{
"path": "_ont/ont-ufiber-uf-nano.md",
"chars": 1490,
"preview": "---\ntitle: UFiber Nano\nhas_children: false\nlayout: default\nparent: UFiber\n---\n\n{% include alert.html content=\"This devic"
},
{
"path": "_ont/ont-ufiber-wave-fiber-onu.md",
"chars": 1359,
"preview": "---\ntitle: UFiber WaveFiber ONU\nhas_children: false\nlayout: default\nparent: UFiber\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-ufiber.md",
"chars": 57,
"preview": "---\ntitle: UFiber\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont/ont-uplink-gp502r.md",
"chars": 110,
"preview": "---\ntitle: Uplink GP502R\nhas_children: false\nredirect_to: /ont-vsol-v2802rh\nlayout: default\nparent: Uplink\n---"
},
{
"path": "_ont/ont-uplink.md",
"chars": 57,
"preview": "---\ntitle: Uplink \nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-vsol-v2801f.md",
"chars": 2201,
"preview": "---\ntitle: V-SOL V2801F\nhas_children: false\nlayout: default\nparent: V-SOL\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-vsol-v2801q.md",
"chars": 1446,
"preview": "---\ntitle: V-SOL V2802Q\nhas_children: false\nlayout: default\nparent: V-SOL\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-vsol-v2802rh.md",
"chars": 1922,
"preview": "---\ntitle: V-SOL V2802RH\nhas_children: false\nlayout: default\nparent: V-SOL\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-vsol.md",
"chars": 56,
"preview": "---\ntitle: V-SOL\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont/ont-yotc-m2-2050-g40.md",
"chars": 7343,
"preview": "---\ntitle: YOTC M2-2050-G40\nhas_children: false\nlayout: default\nparent: YOTC\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-yotc.md",
"chars": 57,
"preview": "---\ntitle: YOTC\nhas_children: true\nlayout: default\n---\n\n\n"
},
{
"path": "_ont/ont-zisa-op151s.md",
"chars": 2979,
"preview": "---\ntitle: Zisa OP151S\nhas_children: false\nlayout: default\nparent: Zisa\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zisa.md",
"chars": 54,
"preview": "---\ntitle: Zisa\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-zte-f6005.md",
"chars": 8259,
"preview": "---\ntitle: ZTE F6005 \nhas_children: false\nlayout: default\nparent: ZTE\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zte-f6005v3.md",
"chars": 12997,
"preview": "---\ntitle: ZTE F6005v3 \nhas_children: false\nlayout: default\nparent: ZTE\n---\n\n# Hardware Specifications\n\n| |"
},
{
"path": "_ont/ont-zte-f601.md",
"chars": 20293,
"preview": "---\ntitle: ZTE F601 \nhas_children: false\nlayout: default\nparent: ZTE\n---\n\n# Hardware Specifications\n\n| | "
},
{
"path": "_ont/ont-zte.md",
"chars": 53,
"preview": "---\ntitle: ZTE\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/ont-zyxel-pmg1005-t20b.md",
"chars": 1252,
"preview": "---\ntitle: Zyxel PMG1005-T20B\nhas_children: false\nlayout: default\nparent: Zyxel\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zyxel-pmg3000-d20b.md",
"chars": 29338,
"preview": "---\ntitle: Zyxel PMG3000-D20B\nhas_children: false\nlayout: default\nparent: Zyxel\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zyxel-pmg3100-t0.md",
"chars": 670,
"preview": "---\ntitle: Zyxel PM3100-T0 \nhas_children: false\nlayout: default\nparent: Zyxel\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zyxel-pmg5100-t0.md",
"chars": 1413,
"preview": "---\ntitle: Zyxel PM5100-T0 \nhas_children: false\nlayout: default\nparent: Zyxel\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zyxel-pmg5318.md",
"chars": 1225,
"preview": "---\ntitle: Zyxel PMG5318\nhas_children: false\nlayout: default\nparent: Zyxel\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont/ont-zyxel.md",
"chars": 55,
"preview": "---\ntitle: Zyxel\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont/serial_dump/fg1000b-11_boot_cfe.txt",
"chars": 21242,
"preview": "D%G----\nBTRM\nV1.0\nR1.0\nL1CD\nMMUI\nMMU9\nDATA\nZBBS\nMAIN\nOTP?\nOTPP\nUSBT\nNAND\nIMG?\nIMGL\nUHD?\nUHDP\nRLO?\nRLOP\nUBI?\nUBIP\nPASS\n--"
},
{
"path": "_ont/serial_dump/fs-com-onu1710-1g/bootlog.txt",
"chars": 11655,
"preview": "9601D\nPRELOADER Bismarck 3.5\nII: PLR:c988baff, Build_date:24082711, Toolkit:rsdk-1.5.6-5281-EB-2.6.30-0.9.30.3-131105\nII"
},
{
"path": "_ont/serial_dump/fs-com-onu1710-1g/uboot-env.txt",
"chars": 3579,
"preview": "b0=setenv bootargs ${bootargs_base} ${mtdparts0} ${rst2dfl_flg}; bootm ${img0_kernel}\nb1=setenv bootargs ${bootargs_base"
},
{
"path": "_ont/serial_dump/ma5671a_minishell.txt",
"chars": 1516,
"preview": "otop\r\ngtop\r\ndmesg\r\ncapture_omci_message\r\narp\r\ncapture_gtop_log\r\nget_gtop_log\r\npasswd\r\nreboot\r\nlanpsg\r\nget_vlanA\r\nget_vla"
},
{
"path": "_ont_epon/bcctv.md",
"chars": 622,
"preview": "---\ntitle: BCCTV\nhas_children: true\nlayout: default\n---\n\n# BCCTV network\n\nBCCTV (Philippines) is a local Internet Servic"
},
{
"path": "_ont_epon/bcctv_PNC11C.md",
"chars": 1690,
"preview": "---\ntitle: BCCTV PNC11C\nhas_children: false\nlayout: default\nparent: BCCTV\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont_epon/free_iliad.md",
"chars": 1087,
"preview": "---\ntitle: Free/Iliad\nhas_children: true\nlayout: default\n---\n\n# Free/Iliad network\n\nIliad's (Italy) PON network is deliv"
},
{
"path": "_ont_epon/free_iliad_F-MDCONU3A.md",
"chars": 24106,
"preview": "---\ntitle: Free/Iliad F-MDCONU3A (v1)\nhas_children: false\nlayout: default\nparent: Free/Iliad\n---\n\n# Hardware Specificati"
},
{
"path": "_ont_epon/free_iliad_F-MDCONU5A.md",
"chars": 963,
"preview": "---\ntitle: Free/Iliad F-MDCONU5A (v2)\nhas_children: false\nlayout: default\nparent: Free/Iliad\n---\n\n# Hardware Specificati"
},
{
"path": "_ont_epon/free_iliad_P-MDONU4B.md",
"chars": 1158,
"preview": "---\ntitle: Free/Iliad P-MDONU4B (pro)\nhas_children: false\nlayout: default\nparent: Free/Iliad\n---\n\n# Hardware Specificati"
},
{
"path": "_ont_xgs/ont-ALL-BM410-XGSPON-GBIC.md",
"chars": 4930,
"preview": "---\ntitle: ALLNET ALL-BM410-XGSPON-GBIC\nhas_children: false\nlayout: default\nparent: ALLNET\n---\n\n# Hardware Specification"
},
{
"path": "_ont_xgs/ont-ECIN-EN-XGSFPP-OMAC-v1.md",
"chars": 149,
"preview": "---\ntitle: E.C.I. Networks EN-XGSFPP-OMAC v1\nhas_children: false\nredirect_to: /xgs/ont-fs-XGS-ONU-25-20NI\nlayout: defaul"
},
{
"path": "_ont_xgs/ont-allnet.md",
"chars": 57,
"preview": "---\ntitle: ALLNET\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont_xgs/ont-cig-XG-99S.md",
"chars": 114,
"preview": "---\ntitle: CIG XG-99S\nhas_children: false\nredirect_to: /xgs/ont-fs-XGS-ONU-25-20NI\nlayout: default\nparent: CIG\n---"
},
{
"path": "_ont_xgs/ont-cig.md",
"chars": 54,
"preview": "---\ntitle: CIG\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont_xgs/ont-ecin.md",
"chars": 66,
"preview": "---\ntitle: E.C.I. Networks\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont_xgs/ont-fs-XGS-ONU-25-20NI-cli.md",
"chars": 529,
"preview": "---\ntitle: CLI command tree (XGS-ONU-25-20NI)\nhas_children: false\nlayout: default\nparent: FS.com Generic Compatible XGSP"
},
{
"path": "_ont_xgs/ont-fs-XGS-ONU-25-20NI.md",
"chars": 19838,
"preview": "---\ntitle: FS.com Generic Compatible XGSPON Stick ONU with MAC SFP+ (XGS-ONU-25-20NI)\nhas_children: true\nlayout: default"
},
{
"path": "_ont_xgs/ont-fs-com.md",
"chars": 57,
"preview": "---\ntitle: FS.com\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont_xgs/ont-hisense-ltf7267-bha+.md",
"chars": 15146,
"preview": "---\ntitle: HiSense LTF7267-BHA+\nhas_children: false\nlayout: default\nparent: HiSense\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont_xgs/ont-hisense.md",
"chars": 57,
"preview": "---\ntitle: HiSense\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont_xgs/ont-huawei-hn8010ts.md",
"chars": 2424,
"preview": "---\ntitle: Huawei HN8010Ts\nhas_children: false\nlayout: default\nparent: Huawei\n---\n\n# Hardware Specifications\n\n| --------"
},
{
"path": "_ont_xgs/ont-huawei-useful-command.md",
"chars": 4783,
"preview": "## Enabling telnet\n\nWe need access to a specific shell and in order to get it enabling telnet is required. On the ONT, t"
},
{
"path": "_ont_xgs/ont-huawei.md",
"chars": 56,
"preview": "---\ntitle: Huawei\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont_xgs/ont-nokia-use.md",
"chars": 588,
"preview": "# Usage\n## Login and enable\n\n\nOnce you're logged in, a custom menu will be shown and you'll be able to access the linux "
},
{
"path": "_ont_xgs/ont-nokia-useful-command.md",
"chars": 2828,
"preview": "# GPON ONU status\n\n## Getting the operational status of the ONU\n```sh\n#ONT>traffic\n#ONT/system>pon\n#ONT/system/pon>show "
},
{
"path": "_ont_xgs/ont-nokia-xs-010s-q.md",
"chars": 3054,
"preview": "---\ntitle: Nokia XS-010S-Q\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont_xgs/ont-nokia-xs-010x-q.md",
"chars": 6025,
"preview": "---\ntitle: Nokia XS-010X-Q\nhas_children: false\nlayout: default\nparent: Nokia\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont_xgs/ont-nokia.md",
"chars": 55,
"preview": "---\ntitle: Nokia\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont_xgs/ont-zte-f2801s.md",
"chars": 8316,
"preview": "---\ntitle: ZTE F2801S \nhas_children: false\nlayout: default\nparent: ZTE\n---\n\n# Hardware Specifications\n\n| | "
},
{
"path": "_ont_xgs/ont-zte.md",
"chars": 53,
"preview": "---\ntitle: ZTE\nhas_children: true\nlayout: default\n---"
},
{
"path": "_ont_xgs/ont-zyxel-pm7300-t0.md",
"chars": 3198,
"preview": "---\ntitle: Zyxel PM7300-T0\nhas_children: false\nlayout: default\nparent: Zyxel\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_ont_xgs/ont-zyxel.md",
"chars": 56,
"preview": "---\ntitle: Zyxel\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_ont_xgs/serial_dump/fs-XGS-ONU-25-20NI_minishell.txt",
"chars": 11625,
"preview": "+traffic Service CLI menu\n\t+ces CES CLI menu (empty)\n\t+pon PON CLI menu\n\t\t+d"
},
{
"path": "_router_pon/avm.md",
"chars": 54,
"preview": "---\ntitle: AVM\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_router_pon/avm_fritzbox.md",
"chars": 1200,
"preview": "## SFP Whitelist\n\n- FRITZ!SFP AON (IEEE 802.3ah-2004 1000BASE-BX10, TX 1310 nm, RX 1480 to 1580 nm, LC/APC 8°, 10 km)[^a"
},
{
"path": "_router_pon/avm_fritzbox_5530.md",
"chars": 2428,
"preview": "---\ntitle: AVM FRITZ!Box 5530\nhas_children: false\nlayout: default\nparent: AVM\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_router_pon/avm_fritzbox_5590.md",
"chars": 2428,
"preview": "---\ntitle: AVM FRITZ!Box 5590\nhas_children: false\nlayout: default\nparent: AVM\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_router_pon/free_iliad.md",
"chars": 1087,
"preview": "---\ntitle: Free/Iliad\nhas_children: true\nlayout: default\n---\n\n# Free/Iliad network\n\nIliad's (Italy) PON network is deliv"
},
{
"path": "_router_pon/free_iliad_box_pop.md",
"chars": 3755,
"preview": "---\ntitle: FreeBox Pop/IliadBox\nhas_children: false\nlayout: default\nparent: Free/Iliad\n---\n\n# Hardware Specifications\n\n|"
},
{
"path": "_router_pon/ont-zte-f6645p.md",
"chars": 5222,
"preview": "---\ntitle: ZTE F6645P \nhas_children: false\nlayout: default\nparent: ZTE\n---\n\n# Hardware Specifications\n\n| | "
},
{
"path": "_router_pon/ont-zte.md",
"chars": 53,
"preview": "---\ntitle: ZTE\nhas_children: true\nlayout: default\n---"
},
{
"path": "_router_pon/tp_link.md",
"chars": 58,
"preview": "---\ntitle: TP-Link\nhas_children: true\nlayout: default\n---\n"
},
{
"path": "_router_pon/tp_link_xb432v.md",
"chars": 1781,
"preview": "---\ntitle: TP-Link XB432V \nhas_children: false\nlayout: default\nparent: TP-Link\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_router_pon/tp_link_xx800v.md",
"chars": 1773,
"preview": "---\ntitle: TP-Link XX800V \nhas_children: false\nlayout: default\nparent: TP-Link\n---\n\n# Hardware Specifications\n\n| "
},
{
"path": "_sass/custom/custom.scss",
"chars": 4909,
"preview": ".page-header {\n\n .github-edit {\n color: $nav-child-link-color;\n float: right;\n \n &:hover "
},
{
"path": "_sfp/bosa-tosa-rosa.md",
"chars": 1625,
"preview": "---\ntitle: \"BOSA, TOSA and ROSA: the conversion from optical to electrical\"\nhas_children: false\nnav_order: 3\nlayout: def"
},
{
"path": "_sfp/ont-wo-mac.md",
"chars": 6298,
"preview": "---\ntitle: SFP with PON MAC and w/o PON MAC\nhas_children: false\nnav_order: 2\nlayout: default\n---\n\nPON technologies, unli"
},
{
"path": "_sfp/sfp-standard.md",
"chars": 6205,
"preview": "---\ntitle: SFP standard and ONT\nhas_children: false\nnav_order: 1\nlayout: default\n---\n\n\nThe organisation that developed S"
},
{
"path": "_sfp_cage/banana-pi.md",
"chars": 2280,
"preview": "---\ntitle: Banana Pi\nhas_children: false\nlayout: default\n---\n\n# Hardware Specifications\n\n| | BPI-R3 "
},
{
"path": "_sfp_cage/broadcom-57810s.md",
"chars": 2484,
"preview": "---\ntitle: Broadcom 57810S\nhas_children: false\nalias: HPE 530SFP+, DELL N20KJ\nlayout: default\n---\n\n# Hardware Specificat"
}
]
// ... and 40 more files (download for full content)
About this extraction
This page contains the full source code of the hack-gpon/hack-gpon.github.io GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 240 files (1.0 MB), approximately 255.7k tokens, and a symbol index with 46 extracted functions, classes, methods, constants, and types. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.
Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.