From 092142b6566e781b9c0959fd3244b999753a99e9 Mon Sep 17 00:00:00 2001 From: Andrea Greco <11886092+Andreag00@users.noreply.github.com> Date: Mon, 8 Aug 2022 01:02:13 +0200 Subject: Corrected the grammar of the content of the website, changed some expressions and titles, fixed some consistency issues as well. --- ont-technicolor-afm0002.md | 52 ++++++++++++++++++++++++---------------------- 1 file changed, 27 insertions(+), 25 deletions(-) (limited to 'ont-technicolor-afm0002.md') diff --git a/ont-technicolor-afm0002.md b/ont-technicolor-afm0002.md index 4512a1d..97ba48b 100644 --- a/ont-technicolor-afm0002.md +++ b/ont-technicolor-afm0002.md @@ -25,14 +25,14 @@ parent: ONT {% include image.html file="afm0002tim.jpg" alt="AFM0002TIM" caption="AFM0002TIM" %} -# Hardware revision +# Hardware Revisions - AFM0002TIM (IP address: 192.168.2.1) - AFM0002FWB (IP address: 169.0.0.1) - AFM0002WND -{% include warning.html content="On this page we discuss AFM0002TIM" %} -{% include info.html content="The AFM0002FWB can be transformed into AFM0002TIM. The AFM0002FWB has an older sw version." %} +{% include warning.html content="The version used to obtain the info shown on this page is the AFM0002TIM" %} +{% include info.html content="The AFM0002FWB can be transformed into AFM0002TIM. The AFM0002FWB has an older software version." %} # List of software versions @@ -63,9 +63,9 @@ parent: ONT This stick supports dual boot. -`k0` and `r0` contains respectively the kernel and firmware of the first image, `k1` and `r1` of the second one +`k0` and `r0` respectively contain the kernel and firmware of the first image, `k1` and `r1` the kernel and the firmware of the second one -# List of firmware and files +# List of firmwares and files ## Useful files - `/var/config/lastgood.xml` - Contains the user portion of the configuration - `/var/config/lastgood-hs.xml` - Contains the "hardware" configuration (i.e. that _should_ not be changed) @@ -79,18 +79,18 @@ This stick supports dual boot. - `omci_app` - The OMCI daemon - `diag` - Used to run low-level diagnostics commands on the stick -# Useful commands +# Useful Commands -## Get/Set the ONT S/N +## Getting/Setting the ONT's S/N ```sh # /etc/scripts/bin flash get GPON_SN GPON_SN=TMBB00000000 # /etc/scripts/bin flash set GPON_SN TMBB0A1B2C3D ``` -## Get/Set the ONT PLOAM password +## Getting/Setting the ONT's PLOAM password -{% include info.html content="The PLOAM password is in ASCII format" %} +{% include info.html content="The PLOAM password is stored in ASCII format" %} ```sh # /etc/scripts/bin flash get GPON_PLOAM_PASSWD @@ -98,12 +98,12 @@ GPON_PLOAM_PASSWD=AAAAAAAAAA # /etc/scripts/bin flash set GPON_PLOAM_PASSWD AAAAAAAAAA ``` -## Enable the Web UI +## Enabling the Web UI ```sh # /bin/iptables -D INPUT -p tcp --dport 80 -j DROP ``` -## Check the currently active image +## Checking the currently active image ```sh # nv getenv sw_active sw_activ=1 @@ -113,23 +113,23 @@ sw_version0=V1_7_8_210412 sw_version1=V1_7_8_210412 ``` -## Boot to a different image +## Booting to a different image ```sh # nv setenv sw_commit 0|1 # reboot ``` -## Query a particular OMCI ME +## Querying a particular OMCI ME ```sh # omcicli mib get MIB_IDX ``` -# Low level modding +# Low Level Modding -{% include warning.html content="This section is based on version `V1_7_8_210412` of the stick" %} +{% include warning.html content="This section is based on `V1_7_8_210412` firmware version of the stick" %} -## Trasnfer files from/to the stick +## Trasnfering files from/to the stick Works with binary files too, just run md5sum on source and destination to make sure you are not corrupting anything... From the stick to the PC: ```sh @@ -140,16 +140,16 @@ From the PC to the stick # cat lastgood.xml | ssh admin@192.168.2.1 "cat > /var/config/lastgood.xml" ``` -{% include warning.html content="on windows replace type with cat and run the commands from cmd (not powershell)" %} +{% include warning.html content="If a Windows system is used replace type with cat and run the commands from cmd (not Powershell)" %} -## Extract and repack the rootfs +## Extracting and repacking the rootfs ```sh # unsquashfs mtd5.bin # mksquashfs squashfs-root rootfs -b 131072 -comp lzma -no-recovery ``` -## Flash a new rootfs +## Flashing a new rootfs -{% include info.html content="you can only flash the inactive image" %} +{% include info.html content="Only the inactive image can be flashed" %} So mtd4/5 if you are on image1, mtd6/7 if you are on image0. @@ -160,8 +160,8 @@ The follwing examples flashes a new rootfs to image1 and boots to it # nv setenv sw_commit=1 # reboot ``` -## Add support to configurable SW and HW versions, VENDOR ID and much more -We can patch `/etc/scripts/flash` in order to add support for some variables implemented in `omci_app` but removed from `xmlconfig`. The patch is below (change the values to suit your needs) +## Adding support to configurable SW and HW versions, VENDOR ID and much more +`/etc/scripts/flash` can be flashed in order to add support for some variables implemented in `omci_app` but removed from `xmlconfig`. The patch is below (change the values to suit your needs) ```patch --- squashfs-root/etc/scripts/flash 2021-09-28 10:38:52.000000000 +0200 +++ squashfs-root.new/etc/scripts/flash 2022-08-04 00:00:29.769605000 +0200 @@ -194,7 +194,7 @@ We can patch `/etc/scripts/flash` in order to add support for some variables imp if [ "$?" = "0" ]; then exit 0 ``` -## Increase the length of the software version from 13 to 14 characters +## Increasing the length of the software version from 13 to 14 characters `omci_app` has an hard-coded limit of 13 characters for the software version, which is too low. We can binary patch it to increase it to 14 (or more, if you dare/need) ``` JVhEWjAwNCUAAAAIAAgACAAAAAAAAAAAAAAAAAAAAABvbWNpX2FwcG9tY2lfYXBwH4sIAAAAAAAA @@ -218,7 +218,7 @@ For reference, the patch changes the follwing section of the omci_app: The original file md5sum is: `4aea2f72bacc11256b7e2c1583d2ad4f` The patched file md5sum is: `da20327c4c002e4c27f82f6ee63dbc1a` -## Enable PLOAM logging +## Enabling PLOAM logging ```sh /etc/scripts/bin flash set OMCI_DBGLVL 1 /etc/scripts/bin flash set OMCI_DBGLOGFILE 1 @@ -227,10 +227,12 @@ reboot ``` 1. The binary log will be placed inside: `/tmp/omcilog` 2. You can convert it into .pcap using https://github.com/ADeltaX/omcilog2pcap -3. You can then open it into wireshark by installing the OMCI plugin from https://wiki.wireshark.org/Contrib.md +3. You can then open it with Wireshark by installing the OMCI plugin from https://wiki.wireshark.org/Contrib.md If you want to log everything since the stick boots, you can create a custom rootfs. Place the last command inside `etc/runomci.sh` as the last line of the file +# Known Bugs + # Miscellaneous Links - [omcilog2pcap](https://github.com/ADeltaX/omcilog2pcap) \ No newline at end of file -- cgit v1.2.3