/was-110-guide

MIT LicenseMIT

Bell Gigahub XGS-PON Bypass w/ WAS-110

Table of Contents

Disclaimer: Liability and No-Responsibility Notice

The information provided in this guide is intended for educational and informational purposes only. Users are solely responsible for the application and implementation of the steps outlined in the guide. The authors, contributors, and distributors of this guide, including but not limited to those credited, manufacturers, and the 8311 Discord Community, hereby declare that they are not liable for any direct, indirect, incidental, consequential, or special damages, losses, or expenses arising from the use or misuse of the information provided.

The guide includes details about modifying hardware, upgrading firmware, and configuring network settings, which may involve risks and potential hazards. Users are strongly advised to exercise caution, adhere to safety guidelines, and seek professional assistance if needed. The authors do not guarantee the accuracy, completeness, or suitability of the information provided, and users acknowledge that they are using the guide at their own risk.

Furthermore, the authors and contributors expressly disclaim any responsibility for the consequences of actions taken based on the information presented in this guide. Users are encouraged to seek assistance from the 8311 Discord Community or other relevant support channels if they encounter issues during the process.

The mention of specific individuals, manufacturers, or entities in the credits and acknowledgments section does not imply endorsement or warranty of their products, services, or contributions. The guide is provided "as is," and no warranties, either express or implied, are made regarding its contents.

By proceeding with the use of this guide, users acknowledge and agree to release the authors, contributors, and distributors from any liability, claims, or damages that may arise in connection with the use of the information provided.

Credits

None of this would’ve been possible if it wasn’t for the hard-working individuals over at the 8311 Discord Community (link).

Special thanks:

  • up-n-atom (Github)
  • djGrrr (Github)
    • Original author for the WAS-110 custom firmware
    • The latest custom firmware can be found over at djGrrr's Github releases page (link)
  • Miguel R.
    • Trusted distributor of the WAS-110 module

Manufacturers

The WAS-110 is an Azores XGS-PON ONT SFP module (link). Some manufacturers have rebadged the Azores XGS-PON modules, such as:

  • ECIN EN-XGSFPP-OMAC-V2 (link)

Gathering Gigahub Modem Attributes (DM#, SMB#, SGC#)

  1. Grab your device DM## and SMB## values from the back of your Gigahub modem:

    Gigahub Modem Back Shot

  2. Identify the firmware version your Gigahub is currently running

    1. Log into your Gigahub and find your Firmware version (accessing your Gigahub Web UI):

      (Image Credit: districtdogz)

      Gigahub Modem Locate Firmware Version

    2. Match your firmware version to the relative SGC# in the 8311 Discord channel (link)

      • Known firmware versions and their corresponding SGC#:
        Device Version SGC#
        Home Hub 4000 1.7.2 SGC821011A
        Home Hub 4000 1.7.8.1 SGC8210140
        Home Hub 4000 1.7.11 SGC8210154
        Giga Hub 1.16.3 SGC830006E
        Giga Hub 1.16.5 SGC830007C
        Giga Hub 1.19.5.1 SGC83000C8
        Giga Hub 1.19.5.4 SGC83000D0
        Giga Hub 1.19.6 SGC83000DC

Connecting the WAS-110

Directly into SFP NIC Method

Plug the WAS-110 directly into your SFP NIC (e.g. Intel X520-DA2, Mellanox ConnectX-3, etc.) and set the host IP to 192.168.11.100/24.

SFP Switch Method

Accessing the WAS-110 via a switch is possible if you have a 10G switch ready to go.

WAS-110 Connectivity via Switch

Some switches require you to have the fibre connected to establish a link. After you have the custom firmware, you can setup the WAS-110 to link without fibre connected (see FAQ).

Media Converter Method

If you don’t have a switch or the switch is not linking with your WAS-110, a media converter will work instead.

WAS-110 Connectivity via Media Converter

Accessing the WAS-110

  1. Confirm you can access the WAS-110 by pinging it from your client device/virtual machine:

    WAS-110 Access Ping Confirmation

  2. Go to http://192.168.11.1 login with admin and password QsCg@7249#5281:

    WAS-110 Access Web UI

  3. Go to the Service tab and tick the box on SSH:

    WAS-110 Access Web UI SSH

  4. Start up a terminal and SSH into the WAS-110 with login root and password QpZm@4246#5753:

    • Linux
      • ssh -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedKeyTypes=+ssh-rsa root@192.168.11.1
    • Windows 11
      • ssh root@192.168.11.1
    WAS-110 Access Web UI SSH
    • If you had logged into the stick and it rebooted on you, you’ll have to clear your known_hosts file otherwise you’ll get an error since the WAS-110’s SSH RSA fingerprint key changes after every reboot.

Checking for WAS-110 issues

Check for issues on the WAS-110 by running the command below and ensuring that it returns nothing:

VOLS="kernelA bootcoreA rootfsA kernelB bootcoreB rootfsB rootfs_data ptconf" ; i=0; for VOL in $VOLS; do VOLID=$(ubinfo /dev/ubi0 -N "$VOL" 2>/dev/null | grep 'Volume ID:' | awk '{print $3}'); [ -z "$VOLID" ] && echo "Volume $VOL missing" || [ "$VOLID" -eq "$i" ] 2>/dev/null || echo "Volume $VOL misplaced (should be ID $i, not $VOLID)"; i=$((i+1)); done
WAS-110 Checking for Issues

If you run into issues, seek support from the 8311 Discord community (link).

Setting WAS-110 Firmware Variables

PPTP or VEIP

You need to know if you're on PPTP or VEIP. Check up-n-atom's guide on Discord (link).

Applying the Variables

  1. Ensure no issues are coming up with the WAS-110 (see here)

  2. Issue the following commands while SSHed into the WAS-110 (replace your DM## , SMB##, and SGC## where applicable:

    # mib_file
fw_setenv mib_file
fw_setenv mib_file

# 8311_device_sn
# Replace DM############# with your DM## value from the back of your modem
fw_setenv 8311_device_sn DM#############
fw_setenv 8311_device_sn DM#############

# 8311_gpon_sn
# Replace SMB######### with your SMB## value from the back of your modem
fw_setenv 8311_gpon_sn SMB#########
fw_setenv 8311_gpon_sn SMB#########

# 8311_equipment_id
# Replace 56## with the corresponding id for your modem
#    5689 is for the Home Hub 4000
#    5690 is for the Giga Hub
fw_setenv 8311_equipment_id 56##
fw_setenv 8311_equipment_id 56##

# 8311_hw_ver
# Replace Fast56####### with the corresponding hardware version for your modem
#   Fast5689Bell  is for the Home Hub 4000
#   Fast5689EBell is for the Giga Hub
fw_setenv 8311_hw_ver Fast56#######
fw_setenv 8311_hw_ver Fast56#######

# 8311_reg_id_hex
fw_setenv 8311_reg_id_hex 00
fw_setenv 8311_reg_id_hex 00

# 8311_sw_verA
# Replace SGC####### with your SGC## value from the back of your modem
fw_setenv 8311_sw_verA SGC#######
fw_setenv 8311_sw_verA SGC#######

# 8311_sw_verB
# Replace SGC####### with your SGC## value from the back of your modem
fw_setenv 8311_sw_verB SGC#######
fw_setenv 8311_sw_verB SGC#######

# 8311_mib_file
# VEIP = /etc/mibs/prx300_1V.ini
# PPTP = /etc/mibs/prx300_1U.ini
# Check up-n-atom's guide on Discord for more info on the XOM API CLI
fw_setenv 8311_mib_file /etc/mibs/prx300_1V.ini
fw_setenv 8311_mib_file /etc/mibs/prx300_1V.ini

# 8311_cp_hw_ver
fw_setenv 8311_cp_hw_ver_sync 1
fw_setenv 8311_cp_hw_ver_sync 1

    Note: Duplication of the commands are intentional

    Screenshot of applying the variables:

    WAS-110 Applying Firmware Environment Variables

Upgrading the WAS-110 to Custom Firmware

  1. Ensure no issues are coming up with the WAS-110 (see here)

  2. Download the latest firmware from djGrrr's Github releases page (link)

  3. Extract local-upgrade.img from the archive file you just downloaded

  4. On the WAS-110’s WEB UI:

    • Upgrade to the custom firmware (note: you have to do this twice):

      • Select browse and select the local-upgrade.img file
      • Select Upgrade
      • Module will reboot
      WAS-110 Firmware Upgrade Web UI

    • After the module comes back up, ensure there are no issues (see here)

    • Add the failsafe file to the module to ensure we can recover it if something goes wrong:

      touch /ptconf/.failsafe

    • Repeat the firmware upgrade from the previous step (yes, you must do this twice)

    • After the module comes back up a second time, ensure there are no issues (see here)

  5. Leave the WAS-110 plugged in and ensure it stays up for 5 minutes without rebooting, you can spam pings to 192.168.11.1 to see if the device stays up.

  6. If all is good, you can remove the failsafe and reboot the stick:

    rm -f /ptconf/.failsafe
reboot

Fibre Connectivity to WAS-110

  1. Plug the fibre into your WAS-110
  2. In the WAS-110’s Web UI at Status → PON, ensure it shows an ONU State of O5.
    • If it’s not showing O5, either:
      • Your fibre isn't connected properly
      • Your firmware variables are incorrect
WAS-110 Fibre Connectivity Web UI

PPPoE via the WAS-110

Using your choice of router (i.e. OPNSense, PFSense, Ubiquiti Dream Machine, etc.), setup PPPoE (b1id/password) like you normally would’ve done with the Gigahub.

Frequently Asked Questions (FAQ)

Internet VLAN - Untagged vs Tagged VLAN

The custom firmware will default to untagging the Internet VLAN for PPPoE.

If you still wish to have the Internet Service VLAN tagged to 35, check the djGrrr’s docs on Github (link)

No WAS-110 link to Switch with Custom Firmware and Fibre Disconnected

The WAS-110 asserts RX_LOS which some switches (e.g. Mikrotik) monitor to establish a link. You need to disable this.

  1. Re-establish connectivity from the device that you previously SSHed the WAS-110 from
  2. Issue the following SSH commands to update the 8311_rx_los variable to a value of 0 
    fw_setenv 8311_rx_los 0
fw_setenv 8311_rx_los 0
  3. Reconnect the WAS-110 into the switch, you should now get a link even with the fibre disconnected

Downloading the Custom Firmware

The latest WAS-110 custom firmware can be obtained from djGrrr's github releases (link).

WAS-110 Group Buy

If you’re interested in obtaining one through a group buy, check out the 8311 Discord Buy and Sell channel (link).