Google Fiber Partial Jack Bypass

Written 2020-10-26

About four years ago, using help from the internet, I was able to bypass the Google Fiber Box and connect a Debian-based router to my GFLT110 Google Fiber Jack. In this post, we explore bypassing the GFLT110 as well.

Main Requirement - GPON SFP Module

This document references a Nokia g-010s-a, so some steps may need to be changed for other modules. This module actually doesn't support standard SFP module detection but can be fixed with a bit of solder or conductive paint as shows in another post. This module also does have a similar default VLAN mapping to the JACK, though we'll cover that later.

GPON network terminology

A bit about the g-010s-a GPON SFP Module

The SFP module contains a fairly complex 3-port switch. One port is connected to the SFP/SFP+ interface. Another port is connected to the GPON subsystem which is connected to the TX laser and RX photodiode. A third port is connected to a small Linux-based management engine with a web and SSH server located at or This means that while configuring the SFP module, you must be on the same subnet. I suspect this means you should not use the same subnet for your home network.

Configuring the g-010s-a GPON SFP Module


Locating the needed GPON Parameters

Most of the parameters are on the back of the GFLT110 fiber jack. One must be extracted from the firmware.


Start with everything powered down, fiber unplugged. Connect the SFP module to a router or computer - I used an SFP-RJ45 media converter. Do not connect the fiber at this time. Power the media converter or boot the computer with SFP NIC. The SFP should boot and linkup within a few minutes. Configure your IP to Ping If does not repond, reconfigure IP to, then try to ping Once a response is received, use that IP for the below steps.

Logging into SSH on the SFP

$ sshpass -p 'SUGAR2A041' ssh ONTUSER@

Backing up the current configuration

Save the output of the following command:
ONTUSER@SFP:/rom# ritool dump

Programming the MFR ID

ONTUSER@SFP:/rom# ritool set MfrID JAAG

Programming the Serial Number

ONTUSER@SFP:/rom# ritool set G984Serial 12345678

Programming the MAC address

ONTUSER@SFP:/rom# ritool set MACAddress 12:34:56:78:9a:bc

Programming the GPON password / SLID

Visit in a web browser. Log in with adminadmin/ALC#FGU. I've noticed that the webserver may error out unless you wait a few minute for the module to fully boot up.

Next click on "SLID Configuration", then "Enter New SLID" textbox. In HEX-mode, enter 31323334353637383930 then save.

GPON ONU Startup

At this point, we have the g-010s-a configured to connect to Google Fiber and emulate the GPON configuration of the jack. We can power down the unit, connect the fiber, and power it back up.

We should also monitor our end of the system. Once the SFP module has booted, again SSH into it. Run the following command:

onu ploamsg
This should print the GPON state - it should be in state 5 (also known as O5) or transition to state 5 quickly. If it does not, you may wish to review this document. You can also use:
omcli omciMgr showRSSI
to print the RSSI. If the SFP is in state 5, GPON is up and OMCI configuration should occur soon after. However, there is an issue.

The VLAN Issue

At this point I tried requesting a DHCP lease from my computer, but received no response.

A few hours of confusion later, on a whim, I tried tagging my outbound traffic with VLAN2, as was required 4 years ago with Google Fiber in another neighborhood. Strangely, I recieved a DHCP offer, but it was untagged, so my DHCP client didn't see it.

This means the VLAN mapping from ethernet to GPON or back again on the SFP module is not correct. This mapping is used to prioritize GPON traffic to ensure things like voice-calling don't drop out when the GPON tree is saturated with non-prioritized traffic. This is supposed to be managed by the ISP over OMCI, but it's possible that Google's OMCI configuration is incomplete and assumes the ONU has some defaults in place that the g-010s-a does not.

At least on Linux, we can rewrite incoming untagged packets to VLAN2 with the following steps(enp0s25 is my interface name):

sudo tc qdisc del dev enp0s25 ingress
sudo tc qdisc add dev enp0s25 handle ffff: ingress
sudo tc filter add dev enp0s25 parent ffff: protocol all basic match 'not meta(protocol eq 0x8100)' action vlan push id 2
sudo ip link add enp0s25.2 type vlan id 2
sudo ip link add link enp0s25 name enp0s25.2 type vlan id 2
sudo ip link set enp0s25.2 up
sudo dhclient enp0s25.2


With the SFP+ module linked at 1gbps, I got about 800mbps/900mbps on With the original GFLT110, I got about 940mbps/940mbps on I'm uncertain why - it could be the case that the extra VLAN tagging needed to work around the g-010s-a's VLAN tagging/untagging could be slowing downloads. Also, it should be possible to linkup at 2.5gbps by connecting the g-010s-a directly to an SFP+ NIC, though some users attempting this with other ISPs have found that uploads need to be throttled/shaped by a router, or else the router may transmit at 2.5gbps when the GPON upload speed is at most 1.244gpbs, and likely throttled depending on the ISP plan. This can cause excess packet drop on upload.