Skip to content

Masquerade as the Frontier Communications Inc. FOX222 or FRX523 with the WAS-110

Bypass family

MoCA

The FRX523 must be provisioned by Frontier to use the 10 GbE LAN port. The WAS-110 will not successfully operate in masquerade mode if the FRX523 is provisioned to use the MoCA LAN port.

Purchase a WAS-110

Note

The WAS-110 is NOT a substitute for a layer 7 router; It is an ONT, and its ONLY function is to convert Ethernet to PON over fiber medium. Additional hardware and software are required to access the Internet.

The WAS-110 is available from select resellers worldwide.

Install community firmware

As a prerequisite to masquerading with the WAS-110, the community firmware is necessary; follow the steps outlined in the community firmware installation guide: Install the 8311 community firmware on the WAS-110.

WAS-110 masquerade setup

To successfully masquerade on XGS-PON, the original ONT serial number is mandatory. It, along with other key identifiers are available on the back label of the FOX222 or FRX523, color-coordinated in the following depiction:

FOX222 label

FRX523 label

from the web UI recommended

As of version 2.4.0 https:// is supported and enabled by default

All http:// URLs will redirect to https:// unless the 8311_https_redirect environment variable is set to 0 or false.

WAS-110 login

WAS-110 8311 configuration

WAS-110 8311 reboot

  1. Within a web browser, navigate to https://192.168.11.1/cgi-bin/luci/admin/8311/config and, if asked, input your root password.

  2. From the 8311 Configuration page, on the PON tab, fill in the configuration with the following values:

    Reminder

    Replace the 🔵 PON Serial Number with the provisioned value on the bottom label of the FOX222 or FRX523.

    All attributes below are mandatory to achieve O5 operation state

    Attribute Value Remarks
    PON Serial Number (ONT ID) FTRO… 🔵 S/N on label
    Equipment ID FOX222
    Hardware Version FOX222
    Sync Circuit Pack Version ✔
    Software Version A R4.4.08.030 Version listing listing maybe dated
    Software Version B R4.4.08.030 Version listing listing maybe dated
    Firmware Version Match ^(R\d+(?:\.\d+){3})$ Community FW v2.5.0+
    Override active firmware bank A OLT inits a reboot if on bank B
    Override committed firmware bank A OLT inits a reboot if on bank B
    Registration ID (HEX) 44454641554c54 DEFAULT in hex
    MIB File /etc/mibs/prx300_1U.ini PPTP i.e. default value
    Pon Slot 10
    Attribute Value Remarks
    PON Serial Number (ONT ID) FTRO… 🔵 S/N on label
    Equipment ID FRX523
    Hardware Version FRX523
    Sync Circuit Pack Version ✔
    Software Version A R4.4.13.067 Version listing listing maybe dated
    Software Version B R4.4.13.067 Version listing listing maybe dated
    Firmware Version Match ^(R\d+(?:\.\d+){3})$ Community FW v2.5.0+
    Override active firmware bank A OLT inits a reboot if on bank B
    Override committed firmware bank A OLT inits a reboot if on bank B
    Registration ID (HEX) 44454641554c54 DEFAULT in hex
    MIB File /etc/mibs/prx300_1U.ini PPTP i.e. default value
    Pon Slot 10

    FRX523v2 Software Versions

    Some users have reported that they are stuck in the O5.1 "fake" state. While some have had success using the downgraded version R4.4.13.067, others have not. Your mileage may vary.

    Registration ID fallback

    Some OLTs reject the DEFAULT Registration ID and the ONT will reach O5.1 but fail to authenticate (no OMCI MIB upload, no T-CONTs or GEM ports provisioned). If this occurs, try an all-zeros Registration ID instead — 22 bytes of 0x00, i.e. 00000000000000000000000000000000000000000000. Note that ONU Authentication Status may continue to display as 0 even when authentication succeeds; verify by actual throughput rather than the status field.

  3. Save changes and reboot from the System menu.

from the shell

  1. Login over secure shell (SSH).

    ssh root@192.168.11.1
    
  2. Configure the 8311 U-Boot environment.

    Reminder

    Replace the 🔵 8311_gpon_sn with the provisioned value on the bottom label of the FOX222 or FRX523.

    All attributes below are mandatory to achieve O5 operation state

    fwenv_set -8 gpon_sn FTRO... # (1)!
    fwenv_set -8 equipment_id FOX222
    fwenv_set -8 hw_ver FOX222
    fwenv_set -8 cp_hw_ver_sync 1
    fwenv_set -8 sw_verA R4.4.08.030 # (2)!
    fwenv_set -8 sw_verB R4.4.08.030
    fwenv_set -8 -b fw_match '^(R\d+(?:\.\d+){3})$'
    fwenv_set -8 override_active A
    fwenv_set -8 override_commit A
    fwenv_set -8 pon_slot 10
    fwenv_set -8 reg_id_hex 44454641554c54
    
    1. 🔵 S/N
    2. Version listing
    fwenv_set -8 gpon_sn FTRO... # (1)!
    fwenv_set -8 equipment_id FRX523
    fwenv_set -8 hw_ver FRX523
    fwenv_set -8 cp_hw_ver_sync 1
    fwenv_set -8 sw_verA R4.4.13.067 # (2)!
    fwenv_set -8 sw_verB R4.4.13.067
    fwenv_set -b 8311_fw_match '^(R\d+(?:\.\d+){3})$'
    fwenv_set -8 override_active A
    fwenv_set -8 override_commit A
    fwenv_set -8 pon_slot 10
    fwenv_set -8 reg_id_hex 44454641554c54
    
    1. 🔵 S/N
    2. Version listing

    Registration ID fallback

    Some OLTs reject the DEFAULT Registration ID and the ONT will reach O5.1 but fail to authenticate (no OMCI MIB upload, no T-CONTs or GEM ports provisioned). If this occurs, try an all-zeros Registration ID instead — 22 bytes of 0x00:

    fwenv_set -8 reg_id_hex 00000000000000000000000000000000000000000000
    

    Note that ONU Authentication Status may continue to display as 0 even when authentication succeeds; verify by actual throughput rather than the status field.

  3. Verify the 8311 U-boot environment and reboot.

    fw_printenv | grep ^8311
    reboot
    

After rebooting the WAS-110, safely remove the SC/APC cable from either the FOX222 or FRX523 and connect it to the WAS-110. If all previous steps were followed correctly, the WAS-110 should operate with O5.1 PLOAM status. For troubleshooting, please read the Troubleshoot connectivity issues with the WAS-110 guide before seeking help on the 8311 Discord community server.

The WAS-110 may reboot after a FOX222 or FRX523 firmware upgrade is pushed over OMCI

The software version will also automatically update and keep in sync to maintain its OLT status.

Software versions

Automatic software version updates since 8311 community firmware version(s) 2.5.0+

Firmware upgrades sent over OMCI will be compared against the Firmware Version Match pattern and automatically update the Software Version A/B attributes if there is a match.

Firmware images are stored in /tmp/firmware.img if further analysis is required.

The software version is used as a provisioning attribute by the OLT and must be kept up-to-date with the latest version. Otherwise, upon a reboot, the WAS-110 will operate in a fake O5 state until corrected.

Software Version
R4.4.08.030
R4.4.08.025
Software Version
R4.4.37.019
R4.4.13.067
R4.4.13.064
R4.4.13.061
R4.4.13.057
R4.4.13.051
R4.4.13.041

Please help us by contributing new versions via the 8311 Discord community server or submitting a Pull Request on GitHub.

Serial access

The version can be extracted by means of the internal TTL UART header and a 3.3V USB to TTL UART adapter.

Serial pinout

Pin IO
2 Rx
4 Tx

Serial setup

Value
Speed 15200
Parity None
Data-bits 8
Stop-bits 1

Shell commands

enable
ontver