The Ubiquiti EdgeRouter Lite can replace the Google Fiber Network Box

Replace Your Google Fiber Network Box with a Ubiquiti EdgeRouter Lite or PoE 53


I’ve been a Google Fiber user (and fan) since the service first hit Provo, Utah. I have a vacation home there, so while I don’t get to benefit from the Gigabit speeds on a daily basis, I certainly take advantage of it while I’m there.

Because it’s a vacation home, I rely on a number of home-automation technologies to monitor and control the place when I’m gone. I use an ecobee remote thermostat to pre-heat or pre-cool the house before I arrive. I can send a text to turn the gas water heaters on and off via a water heater timer. I can watch exterior security cameras from my phone. And I can remotely monitor and arm/disarm the alarm system.

Why the Google Fiber Network Box is No Longer Cutting It

Some of the the home automation technologies I use rely on port-forwarding, which is how you “crack open” the network’s firewall just enough to access specific devices on the other side. In addition to remote control of smart devices, I also use port-forwarding to remotely access the desktop systems, servers, and network devices that stay online in the house while I’m away. Port forwarding worked great for the first couple years of Google Fiber’s service, until they recently “upgraded” the user interface of their Google Fiber Network Box (GFNB)…. and I hope the quotes around “upgraded” are enough for you to hear the sarcastic tone in my voice.

In what appears to be an effort to simplify the Google Fiber Network Box interface, they removed a number of features that advanced users rely on. The worst victim was port-forwarding. While it’s still technically allowed, Google Fiber restricts forwarding only to network devices with reserved DHCP address (meaning you can’t forward to any device with a static IP address), and they also opened a huge security hole by forcing you to forward FROM and TO the same port number. Not only does that limit you to accessing only one Windows Remote Desktop on port 3389, or only one device’s embedded web server on port 80, but those commonly-known port numbers are accessible from the WAN side of the network, meaning they’re much easier to scan and attack. This “upgrade” was unacceptable to me, and when Google Fiber’s support staff told me they couldn’t “downgrade” me back to the original interface, I decided to take matters into my own hands. Update: I’ve been told this has now been fixed, but I still like my EdgeRouter better than the Google Router.

Enter the Ubiquiti EdgeRouter Lite.

The Ubiquiti EdgeRouter Lite can replace the Google Fiber Network Box

The Ubiquiti EdgeRouter Lite can replace the Google Fiber Network Box

I was already a fan of Ubiquiti (UBNT) products. At our Eastern Washington cabin, I use their EdgeRouter-POE as a router, a UAP-PRO access point for indoor WiFi, and a NanoStation to blast WiFi into the back yard, out onto the beach, and half way across the lake. At our main house in Seattle, I use two UAP-AC-PRO access point to fill the house with a very strong WiFi signal (read about that here) as well as a secure guest network, with a UniFi Security Gateway (USG) as the house’s primary router. It’s fair to say I’m a UBNT fanboy.

So when I read in some Google Fiber Support threads (like this one) that it might be possible to replace the GFNB with a Ubiquiti EdgeRouter, I got excited. I picked up an EdgeRouter Lite on Amazon for less than $100, and looked forward to my next trip to Utah to set it up.

Before I go further, I need to repeat the warning I made in my article on installing the UAP-PRO access point: this is not a task for the casual geek. Configuring and tweaking a UBNT EdgeRouter to replace a Google Fiber Network Box requires a certain comfort level with networking, routers, and the Linux command line. This hack is unsupported by Google Fiber, so they won’t help you, and if you call them, they will tell you just to plug your GFNB back in. You can get some help in the UBNT EdgeMAX Forum, and possibly from non-Google employees in the Google Fiber Support Forum, but for the most part… you’re on your own. I chime in on those forums’ conversations from time to time, but I don’t answer support questions here on my blog or via email.

Before You Start

This guide assumes the following:

It’s also important to note that I do not use Google Fiber TV at my Provo House (I prefer DirecTV). From what I understand, it’s totally possible to use an EdgeRouter in place of the GFNB if you also have Google Fiber TV. I had previously included the necessary settings to support Google TV in my example config.boot files, but Google changed some of their settings and a few of us are still trying to figure out how to adjust for those new settings. Please stay tuned (I’ll announce on my Twitter feed when we get this figured out).

Upgrade the EdgeOS Firmware and Reset the Router

Before you disconnect your old Google Fiber Network Box and temporarily lose Internet service, download the latest firmware (I recommend 1.9 or higher) and install it on your new EdgeRouter. Make sure you also reset the router to factory defaults (either before or after the firmware upgrade).

Download a Default Google Fiber config.boot File

The fastest way to get my baseline Google Fiber configuration on your EdgeRouter is to simply copy one of my example config.boot files onto your router.

Unfortunately, you can’t simply upload a config.boot file by itself via the EdgeMAX UI (the UI actually expects a larger tar.gz file with config.boot and a bunch of other files compressed inside), but if you’re semi-comfortable with the vi editor and/or the EdgeRouter CLI, you can quickly copy my config.boot file onto the EdgeRouter directly, reboot the router, and be up and running within minutes.

I have three versions of my config.boot available:

This is a good time to thank Bryan Klinger for initially converting one of my early v1.7 Google Fiber ER-Lite configs to his ER-POE. My v1.9+ configs have evolved a lot since then, but he still gets credit for starting the ball rolling.

All of the above files will give you the same basic setup, with a few minor differences:

  1. All configurations use eth0 as the WAN port, but the POE version also powers the eth0 port with 48 volts. This allows you to power the Google Fiber Jack directly, so you won’t need to connect any external power supply to the jack.
  2. The POE and ERL versions have a “Local Config” port, which is always on eth1.
  3. The POE version and ERX versions take advantage of on-board hardware switching via ports. The POE version combines eth2, eth3, and eth4 combined in a single LAN switch while the ERX combines eth1, eth2, eth3, and eth4. The switch is referred to as switch0 in the configuration.

Assume the xxx in the examples below refers to the appropriate version of the config.boot file for your particular EdgeRouter. For example, on an EdgeRouter POE you’d use config.boot.poe.

Before you disconnect your Google Fiber box and temporarily lose your Internet connection, open up the appropriate example config.boot.xxx file for your EdgeRouter in a new browser tab on your system. Make sure to press the Raw button near the top right of the page, so when it comes time to copy and paste the contents you won’t copy any of the extra info (like line numbers). You can optionally copy and paste the config.boot.xxx into a text file on your local system, or just leave it in your browser tab to copy in a few moments.

What the Example config.boot Does

If you’re familiar with the EdgeRouter CLI and settings, you can read through any of the config.boot.xxx example files to see exactly what’s happening on the router. But in general terms, here’s what happens:

  • The WAN interface is configured on eth0 to connect to the Google Fiber Jack. On the POE, it’s powered with 48 volts to power the jack.
  • A LAN interface is configured to connect to LAN devices on the 192.168.1.1/24 network. If you prefer a different subnet (like 192.168.0.1 or 192.168.2.1), you can edit your new config.boot file before rebooting with it. I kept 192.168.1.1/24 network because it’s already the factory default.
  • A VLAN for the WAN port is configured as eth0.2. The settings for this interface make the true “secret sauce” as to why this works on the Google Fiber network. This VLAN applies the proper QoS settings and masquerading to the WAN to keep Google happy.
  • Multiple settings to enable both IPv4 and IPv6 are configured.
  • A local configuration port is enabled on eth1 on the ER-Lite and ER-POE. If anything goes wrong with your configuration, this port allows you to connect a laptop directly to the EdgeRouter via Ethernet without disconnecting anything, then access the EdgeRouter’s GUI or CLI via 192.168.99.1 to fix problems. Because the ER-L’s ports aren’t hardware switched like the ER-X’s and some of the ER-POE’s, I don’t recommend configuring eth1 as an additional LAN port on your ER-L’s primary subnet, which is why I decided to at give eth1 at least some useful function in this setup. You may never need to use it, but I figured why waste a perfectly good Ethernet port?
  • A basic firewall is configured that supports IPv4 and IPv6.
  • Basic settings for an isolated guest WiFi network VLAN and DHCP server are configured.
  • MSS clamping is enabled at 1460 (this number works great for me on the Google Fiber network, but you can play with different settings yourself).
  • Port forwarding is enabled and configured for the correct LAN and WAN ports for remote access to your router.
  • A DHCP server is enabled for the local network.
  • A local caching DNS forwarder is enabled.
  • UPnP is enabled in secure mode (using upnp2)
  • Timezone, system name servers, and the local hostname are set for Mountain Time (easy enough to change after you’re up and running)
  • Hardware offloading is enabled, which is required to reach speeds over the half-Gigabit(ish) level on the Google Fiber network.
  • Additional firewall and IGMP settings are configured to support Google TV service. I no longer recommend configuring Google TV options on the EdgeRouter. Instead, see below for simple instructions regarding splitting the Google TV and EdgeRouter traffic using a Gigabit switch.

Temporarily Connect eth0 on the EdgeRouter to your Computer or LAN

After you’ve got the appropriate config.boot.xxx file available on your local computer, temporarily disconnect your PC from any WiFi networks then connect an Ethernet cable from your computer (or from a LAN switch connected to your computer) to the EdgeRouter’s eth0 port, which is the only port that works on a factory-reset EdgeRouter.

By default, eth0 on the EdgeRouter is configured for the 192.168.1.1/24 network. Because the router doesn’t have an active DHCP server (yet), you’ll need to manually configure your computer with something like:

  • IP Address: 192.168.1.4
  • Netmask: 255.255.255.0
  • Gateway: 192.168.1.1

Once you can ping 192.168.1.1 from your computer, you’re good to go.

Connect to the EdgeRouter via Terminal

Using a terminal application, ssh to 192.168.1.1 (or [email protected] if on Linux or Mac). Both the default admin username and password are ubnt.

Configure your EdgeRouter Using the example config.boot File

Now we need to copy the config.boot.xxx file onto the EdgeRouter. There are a number of ways to do this. Linux users can simply use scp to copy the example config.boot.xxx file via ssh directly from another local Linux system. But for most users, the easiest way will be to use vi to create a new file on the EdgeRouter then paste the contents of your new config.boot.xxx

First, copy the raw contents of the appropriate config.boot.xxx file from your browser into your local clipboard. Then create a blank config.boot.xxx file in /home/ubnt with:

sudo vi /home/ubnt/config.boot.xxx

Once inside vi, turn off the auto-indenting feature before you paste by typing the following (including the colon):

:set noai

and pressing ENTER. If you’re not familiar with vi, make sure you type the “:” whenever they’re shown in this guide.

Now enter vi‘s insert mode by pressing lowercase i (you don’t need ENTER after the “i” command).

Paste the copied raw config.boot.xxx file from your local system’s clipboard using your terminal client’s Paste menu item or keyboard shortcut (usually CTRL-V on PC, Command-V on Mac, etc.).

Exit insert mode by pressing your keyboard’s ESC key.

Now write and quit the file by typing:

:wq

and then ENTER.

Now you’re ready to copy your new config.boot.xxx file over the EdgeRouter’s default config.boot file with:

sudo cp /home/ubnt/config.boot.xxx /config/config.boot

Reboot to Apply Changes

Now you’re ready to reboot the router to apply your changes with:

reboot

Your EdgeRouter will ask you to confirm.

IMPORTANT: If you’re using the config.boot.poe version of this configuration on an EdgeRouter PoE, make sure you disconnect the Ethernet cable connected to the eth0 port immediately after you confirm the reboot. Once the reboot is finished, the eth0 port will powered with 48v for the Google Fiber Jack and you shouldn’t have any non-PoE clients attached to that port when it’s powered.

You’re now ready to physically connect your EdgeRouter to your Google Fiber Jack and your LAN.

Connect your EdgeRouter to your Google Fiber Jack and LAN

While your EdgeRouter reboots (it should only take a couple minutes), you can change your computer’s TCP/IP settings back to DHCP and make the final physical connections between your EdgeRouter and your network.

Connect the eth0 port (which is now configured as the WAN port) to the Google Fiber Jack. If you’re using an ER-POE, you can unplug any external power injector from the fiber jack.

Connect your LAN clients (or any switch on your LAN) to any of your EdgeRouter’s LAN ports (such as eth2). Using my example configs, the port settings are:

EdgeRouter Lite:

  • eth0 = WAN (Google Fiber Jack)
  • eth1 = Local Config Port
  • eth2 = LAN

EdgeRouter X:

  • eth0 = WAN (Google Fiber Jack)
  • eth1, eth2, eth3, & eth4 = LAN (combined as switch0)

EdgeRouter POE:

  • eth0 = WAN (Google Fiber Jack) + 48v PoE
  • eth1 = Local Config Port
  • eth2, eth3,eth4 = LAN (combined as switch0)

Test Your Connection

Within a few minutes, your EdgeRouter should reboot and your computer should receive a DHCP address from the router and (fingers crossed!) be able to access the Internet. Perform a speed test to make sure you’re still seeing fast speeds.

This was my first test result after the changeover:

First speed test with EdgeRouter Lite replacing the Google Fiber Network Box

First speed test with EdgeRouter Lite replacing the Google Fiber Network Box

Congratulations! You’re up and running on the Google Fiber network with a Ubiquiti EdgeRouter!

Replacing the Google Fiber Network Box’s WiFi

One thing you lost when you unplugged your Google Fiber Network Box is a set of WiFi antennas to allow wireless clients to access your network. But that’s no big loss.. the GFNB WiFi antennas are notoriously lame. The cheapest way to replace them is to install DD-WRT on a wireless router you might already have, and configure it as a stand-alone access point.

Or, just purchase the best standalone WiFi access point on the market… which also happens to be a Ubiquiti device: the UAP-PRO (which does both 2.4Ghz and 5Ghz WiFi) or the UAP (2.4Ghz only).

For Google TV Users

If you also have Google TV service, you’ll still need to connect your DVR box to your local LAN, even if you have the 2nd generation box that combines the Google Fiber box and DVR. All the required settings to make Google TV work with an EdgeRouter are in the config.boot file.  You do not need to run any additional script.

My config.boot files used to include elements (inclduing igmp-proxy and multicast firewall settings) to enable Google TV on an EdgeRouter. However, Google had a terrible habit of changing the multicast addresses and settings without warning, thereby breaking Google TV service on the EdgeRouter. The Google TV settings are no longer part of my suggested configurations.

For Google TV users only, I now recommend installing a simple Gigabit switch, such as the NETGEAR GS105NA, “downstream” of the Google Fiber jack, then connecting both the Google Fiber TV box and the EdgeRouter’s WAN port to separate ports on the Gigabit switch. This separates the Google TV service from the EdgeRouter and will allow everything to function normally without having to chase down changing settings at Google’s whim.

You can then connect any set-top Google TV boxes in your house directly to your primary Google TV box.

 

A Word about Google Fiber IPv6 Addresses

Google might not allocate your IPv6 addresses immediately. You’ll likely have to wait until overnight until you see the IPv6 addresses for the WAN and LAN interfaces in the GUI. I’ve tried everything I can think of to kickstart the process, to no avail. You just have to wait.

Final Steps

Now that you’re online with an EdgeRouter instead of a Google Fiber Network Box, there are a few final steps you should take.

First, access the GUI via a web browser to https://192.168.1.1/. Use ubnt as the username and password to gain access.

Go to the Users tab, then fill in the info to add a new administrative user. Use something other than the obvious “admin” or “root.” Once that user is created, go to the top left corner of the GUI (where it says Welcome ubnt) and log out. Log back in as the newly created user, go back to the Users tab, and delete the ubnt user. Now you’re protected from default user and password access.

You can poke around inside the web interface a bit more, and see how all the command line changes you made look in the GUI. In the Wizards tab, you can tinker with the MSS clamping settings, and adjust them to your liking. In the Services / DNS tab, you can tweak the size of your DNS forwarding cache size (I’ve been using out 500 lately).

You can go to the Firewall/NAT tab and set up some port forwards, choosing any FROM and TO ports you want for any IP address on the LAN (which is what started me on this path in the first place).

Or you can just watch the Dashboard and monitor the Tx and Rx rates of each interface. Mine looks like this (my IPv4 and IPv6 WAN IP addresses are blacked out for security). Don’t be concerned that I’m using 192.168.0.1/24 and that my LAN is connected to eth0. Pretend it reads 192.168.1.1/24 on eth1 to match the config in this article:

Google Fiber EdgeRouter Lite GUI Dashboard

Google Fiber EdgeRouter Lite GUI Dashboard

But one thing you must do is wave “goodbye” to your sad little Google Fiber Network Box.

A sad, unplugged, Google Fiber Network Box that has been replaced by a UBNT EdgeRouter

A sad, unplugged, Google Fiber Network Box that has been replaced by a UBNT EdgeRouter

Congratulations! You’ve replaced your Google Fiber Network Box with a much more useful and flexible business-class router: the affordable, powerful, and downright lovable Ubiquiti EdgeRouter!

As always, I welcome your questions, comments, and feedback below!

Further Reading:

  • Ard Righ

    I am curious why eth0 is set as the local network and eth1 is the external network, which leaves odd numbering if you want to used eth2 locally.

    I guess it doesn’t matter too much at home, but it does seem odd to me if you use more ports.

    • Hi, Ard. I simply left eth0 as the local network since that’s how it’s already set up by default (192.168.1.1). But you can configure any interface to act as a LAN or WAN port. Totally up to you!

      However, to the best of my knowledge, the EdgeRouter Lite does NOT have hardware switched ports, so it’s not advisable to connect eth2 to the same subnet on the local network, because you’ll get sub-optimal switching. The EdgeRouter-POE-5 has eth2, 3, and 4 hardware switched, so it would make sense to just use any of those as additional LAN ports.

  • twillower

    Mr. Jenkins, thank you so much for this tutorial! I can’t stand the Network Box, especially since they did away with asymmetric port forwarding.

    One thing: I can’t get the config to save. I’m connecting via ssh and copying and pasting, but this error comes up at every “commit.” Here it is:

    [email protected]# commit

    [ interfaces ethernet eth1 vif 2 ]

    RTNETLINK answers: File exists

    Error creating VLAN device eth1.2

    [ service dhcp-server ]

    Warning: No DHCP start-stop range or active static-mapping set for subnet 192.168.1.0/24

    Conflicting subnet ranges: 192.168.1.0/24 overlaps 192.168.1.0/24

    Conflicting subnet ranges: 192.168.1.0/24 overlaps 192.168.1.0/24

    DHCP server configuration commit aborted due to error(s).

    Commit failed

    [edit]

    [email protected]# save

    Warning: you have uncommitted changes that will not be saved.

    Saving configuration to ‘/config/config.boot’…

    Done

    [edit]

    [email protected]#

    Any help on the issue would be much appreciated!

    • Hi, Twillower. It looks like the config file is “seeing” settings that already exist. Make sure you’re on current firmware, do a factory reset on the device, reboot, and you should be good to go.

  • Hi, Bryan. Great job modifying the config to work with the ER5-PoE and power the GF jack. And yes, the hardware-switched ports on the ER5-PoE are awesome. I run that same router at our main house in Seattle, but we have Comcast Cable rather than Google Fiber, so I run a more “vanilla” setup on it.

    Great catch on the DHCP-issued DNS servers. I’ve updated both the script and default config.boot Gists.

    I’ll also update the article today to link to your Gist for anyone using the PoE router. In fact, because it can power the GF jack, that’s probably the ideal setup.

    Thanks again and Happy New Year! 🙂

  • Pingback: Google Fiber with Ubiquity EdgeRouter PoE | overt.org()

  • Hi, Razz. I haven’t used OpenVPN with mine, so no… I haven’t written a tutorial for it. But if you come over to the UBNT Community forums, I’ll bet someone there has done it and can walk you through it.

  • Keith D Kaiser

    Thanks Steve for this promising solution to the Google port forwarding issue. One naive question however is about the Google TV service. We use the DVR extensively, can the old GFNB DVR combo be hung off the new EdgeRouter Lite to restore the ability to record?

    • Hi, Keith. I don’t use Google TV, so I can’t give you a first-hand answer. I’ve heard that others are doing it, and I’ll look into exactly how. 🙂

      • Keith D Kaiser

        This would be great. There are a few of us here in the Kansas City, MO area that really want to do this. I posted the Network+ Box (GFRG210) question below before realizing what they had done exactly. I applaud the one box concept but in this case I think its biting us in the butt.

        • Ryan Rainey

          Hey Keith, I am getting ready to implement the EdgeRouter in my KC home and also have the GFRG210 network box. I used to have the old network box but then just recently signed up to have GF TV. When they came to hook it up, they gave me the TV and Network all in 1 box. I see this being a real issue and will continue to pay attention to this blog until someone figures out a way to make it work.

          • Keith D Kaiser

            I have the EdgeRouter in hand but have not had the time to make the change yet. I hope to do this on Sunday based on some help a GF network expert gave me the other day. Where are you located? I’m in the Northland.

          • Adam

            Hey Guys,

            I just got GF on Thursday in Olathe, and also got the all in one unit. The tech that installed it said, they can’t do just the storage box, and network separate anymore. However I didn’t like that answer so I call the help desk. They told me I had to go to the Google Fiber Space off 1814 Westport Rd, Kansas City, MO 64111 and they could help me. I had to bring them the all in one box, but within a few min I walked out with the two apart. I got home and hooked them up and everything is working. Soon I will be working on switching the network box out for EdgeRouter

  • Hey, Adam. I don’t know… since I don’t have Google TV, I can’t verify personally. I’m hoping someone who does reads this comment and chimes in!

  • Hi, Adam. No, you can use the scripts as is, and then go into the web GUI of the EdgeRouter and forward any additional ports you want!

  • Thanks, Erik. I’ve HEARD that the hardware is similar (or perhaps the same?) on the Secure Gateway devices, but the software is different, and therefore this approach doesn’t work… but I haven’t tinkered with that hardware, so I can’t be certain. This might be a great question for the UBNT forums (which are excellent). If you find out one way or the other, please come back and comment again!

  • Liviu Stefan

    Hi Steve,
    What changes should be done for a PPOE connection with WLAN?

  • I haven’t upgraded to 1.8 yet, but I’ve read the release notes and don’t see anything that would break it! If you proceed, please let me know if it goes smoothly (as I imagine it will).

  • Nick

    I have combined the ER5-POE config from Bryan Klinger and added the extra Firewall settings from Steve’s TV config but just realized that I need a solution for having a working DVR. Has anyone worked this out yet? Or does anyone have any ideas how I might achieve this?

    • Jimi

      I’ve tried to do the same combining both scripts for ER5-POE. Internet is working fine. Google TV shows the guide but when I try to select a channel it says there is no DVR attached. Did you get further than that? Any chance you can share your scripts?

  • Hi, Mike. I have DHCP turned off on one of mine, as I handle DHCP and local DNS from a separate server on my network. But I’ve never tinkered with having another device do NAT. I’d jump in the UBNT forum and ask there. I’m sure someone will answer it quickly.

  • Great catch, Matthew. I’ve fixed the typo in the script, and moved the firewall stuff up top to avoid the undefined errors. Thanks!

  • Peter Benson

    Hi! I’ve been interested in getting rid of the Google Network box from the first day they installed it, and have followed the various remedies from the original thread using pfsense and a NetGear managed switch. Had a few issues with the switch getting an ip address from GF, and put everything on the back burner for a time. Finally got around to picking up an ERPOE-5, followed your article, (much more concise and easier to follow – kudos!) and have everything up and working as advertised. No problems getting 950+ up, but only around 600 down, but that’s with 2 TV boxes, 2 IP security cams, a web server, and 2-5 laptops & 2-3 phones (vonage & cells over ip) running at any given time.
    Thanks for your efforts in consolidating this info!
    Another happy camper in Kansas City!

  • Allan FOSKETT

    Hello Steve,
    Thank you for putting this guide together, I found it easier to follow than others.
    I have the 1.8.5 firmware installed as that was readily available on the Ubiquiti site and now have questions about IPv6 and was hoping you might look what I have over and make suggestions as appropriate.

    Based on the work of others I have the following which I hope will bring Google’s IPv6 into my network:

    configure
    edit interfaces ethernet eth1
    set dhcpv6-pd rapid-commit enable
    set dhcpv6-pd pd 1 prefix-length /56
    set dhcpv6-pd pd 1 interface eth1.2 service slaac
    set dhcpv6-pd pd 1 interface eth1.2 prefix-id 1
    set dhcpv6-pd pd 1 interface eth1.2 host-address ::1
    top

    edit interfaces ethernet eth0 vif 2
    set ipv6 dup-addr-detect-transmits 1
    set ipv6 router-advert cur-hop-limit 64
    set ipv6 router-advert link-mtu 0
    set ipv6 router-advert managed-flag false
    set ipv6 router-advert max-interval 600
    set ipv6 router-advert other-config-flag false
    set ipv6 router-advert prefix ::/64 autonomous-flag true
    set ipv6 router-advert prefix ::/64 on-link-flag true
    set ipv6 router-advert prefix ::/64 valid-lifetime 2592000
    set ipv6 router-advert reachable-time 0
    set ipv6 router-advert retrans-timer 0
    set ipv6 router-advert sent-advert true
    commit
    save
    exit

    I currently have a Microsoft 2008R2 server for DNS and DHCP for IPv4, but am willing to let Google operate my IPv6
    so what do you think?
    many thanks

    • Hi, Allan. You actually don’t need all those settings. I’ve updated my config.boot file with the necessary additions for IPv6 on Google, and it’s working for me on their Provo, UT network. Give it a shot!

      • Allan FOSKETT

        Hi Steve,
        Thank you for your response and update of the script!
        It took two days for an IPv6 address to attach to the router and devices on the internal network but I expected that based on previous testing with my Asus RT-N65 routers using Padavan firmware. Interestingly IPv6 test sites have not recognized the IPv6 address on the router, but maybe that is another two day wait also.
        I tried the TV script a couple of weeks ago and while everything worked including previously recorded content, the TV picture had tears and jaggies every few minutes so the Google box is currently in service. I chalked that up to the fact that I was using a 10 dot address space internally and elsewhere others report that Google uses similar subnets as part of the delivery of TV services. I have since migrated to a 172 dot subnet and will test TV again in a week or two.
        Thank you again for the excellent work.

        Allan

  • Billc108

    Hi Steve,

    Thanks for the walk through.

    FYI, I noticed that you repeat the DNS server entries, first in lines 190-194 and again in lines 215-219.

    The one piece I’m missing now is how to route the static addresses from Google through to eth2 (or eth0 if that makes more sense) so I can run some web servers off them.

    • Did you figure this out? I’m in the same boat.

  • Hi, Atomizer. Come over to the UBNT Community forums. Much better place to get help with this!

    • atomizer123

      Thanks for the suggestion, Steve. Will do.

  • Derp. My bad. Thanks for catching that. Should be fixed (and I confirmed the ER-L version didn’t suffer from the same fate). 🙂

  • Mike Wood

    Many thanks for posting this. I have been struggling for a while with pfSense and, although it handled the VLAN2 data side just fine, I could never get it to work with Google Fiber TV.

    Time to try an EdgeRouter Lite…

    I used your config.boot (modified to include all my static mappings and different networks) and then ran the tv script. All worked first time.

    I have the second generation Google TV Network + box where the network box and the DVR are combined, so you can’t just remove it completely. It’s now connected downstream, to the LAN output of the EdgeRouter, (which is where it should be) and it seems to be working fine. All channels are there I think, no freezing after a few seconds (which was always the problem with pfSense – IGMP just didn’t work right and I could never get a multicast subscription) and I’m getting ‘almost’ full speed data*. Huzzah and thanks again!!

    * I say ‘almost’ full speed as the speeds do seem to be slightly slower than they were using the Google router, perhaps by 50 Mbps. Still approaching 900 Mbps in both directions, so I’m fine with that. It could just be because it’s the weekend.

    • Hi, Mike. Glad to hear you’re up and running!

      FYI – I updated the config.boot files so they now include the Google TV settings (they don’t affect service for those not running Google TV, like me).

    • jack

      Mike is your Google Fiber TV service still working? Do you mind giving me a hand to copy over the config file to my edgerouter through Putty SSH on my Windows 10 machine?

  • Lee

    Could that have been my problem? I thought I was crazy!

  • jack

    Hi, I just order the edgerouter lite and I have a few questions.

    1. Do I have to also load a tv script to get the Google TV service to work or just load the config.boot.erl file to the edgerouter lite? If so where is the TV Script located?

    2. If I have two Xbox One on the same lan will I have any issues with them? Currently my setup I can only set one of them in a DMZ for the network to be open on the Xbox One Network Settings. I hate switching the DMZ to the other Xbox One when I play on the second one. I want both of them to have Network setting of ‘Open’.

    Steve if I need assistance if you have the time I am willing to pay you $50 to help me setup my edgerouter and network once I get the router next Monday.

    I have the new Google Fiber network box with DVR and Wifi in one. I also have Google TV Service and two Xbox Ones.
    Thanks

  • Lee

    Ok, I attempted the setup again using the newest version of the script and it’s working! Interestingly, when viewing the web interface, I am not getting stats at all or the lit up ports showing active. Also, in the list I’m not seeing an ip beside The fiber jack or wan entires. Says waiting or something similar, but I am connected.

    • Jake

      I had the same problem too. It’s likely you are using an unsupported browser. I was using Safari initially, but once I switched to google chrome, all the stats and ports showed up. Thanks!

  • Excellent question, Logan. They’re actually aliases, and they both do the same thing. I believe one was the older version of doing it (ipv6-icmp). But I appreciate the catch, and my OCD has caused me to update the files so it’s now consistent. Thanks!

  • Hi, Cole. The latest version of my scripts now have DPI disabled. I’ve been informed this helps with TV service.

  • Hi, Michael. I don’t have Google TV, so I’m not much help. There is a thread discussing this in the UBNT Community forums, tho. Come on over there and maybe we can figure it out!

  • Yep – they’re updated now! 🙂

  • Kenneth Clark Loggins

    I am getting really paltry speeds from KC fiber after doing this setup. 135Mbps or so, up and down. Ideas?

  • Kenneth Clark Loggins

    Turns out small business static environments don’t need the tagged VLAN.
    Can we generate a new script for this to save from having to make all the changes?
    eth0 set to DHCP and then switching all references in firewall, NAT, etc. to eth0 from eth0.2 got this going quickly.

  • Jake

    Are there any tutorials on getting L2TP VPN up and running with this configuration on the ERL? I’d love to be able to add this to my ERL. I did find this recent article but I am having a hard time since we have such a unique LAN WAN config. ( https://help.ubnt.com/hc/en-us/articles/204950294-EdgeRouter-L2TP-Server )

  • wesdrums

    I’m curious, with the network/dvr combine box do you have the router/wan port of this box plugged into the local lan on the edgerouter/local lan switch. Double nat? OR are you just using a regular port on the network box to a regular local lan port and the same with the tvs? I have mine setup currently the former. It works fine, but the google remote app doesn’t work because of the double nat. Anyone have any suggestion on how to have the app work?

  • Dan Garrison

    First off I would like to say thanks. Iv’e had Google fiber for 2 1/2 years with 4 TV boxes.The wifi and general performance has been sketchy at best since day one. But last week 3/30/2017 I followed this guide and replaced the network box with the Edge Router X along with a TP Link 16 port gigabit switch and a UAP-PRO access point. The hardest part was getting up the courage to do it. Every thing went good for the most part. The TV was flaky at first but straightened itself out after a few reboots and a couple days. I think that the bigest thing was the last time I rebooted everything I powered the router up first and let it get connected, then powered up the network storage box followed by the TV boxes and then everything else giving everything time to stabilize in between.
    After I had everything working I went in to the router and separated ETH3 and ETH4 out of the main internal switch on the router and assigned them there own sub nets. One for my son in law and his stuff and one for a computer running Ispy camera software and 3 cameras on a separate gigabit switch that was installed when Google fiber was initially installed.
    2 of the TV boxes are feed by the coax out of the network storage box and the other 2 out of the 16 port switch.
    Other then an occasional stutter on the TV everything is pretty solid with no wifi drops at all which was a constant problem before.

  • jeyyu2003

    Hey Folks, maybe I am missing something. I am following the instructions above but simply do not get any link light when I connect the fiber jack directly to ERL Lite after running the ERL script and hitting reboot. Needless to say, no link, no IP address. I am on the EdgeRouter Lite v1.9.0 Firmware. Thanks!

    • luikiedook

      You probably got it figured out by now, but most likely your fiber jack requires PoE. I’ve heard you can get a PoE injector from google for free. Otherwise, you can buy one or get an edge router that supports PoE. (obviously I would try to get one from google for free first)

  • Brian Graf

    Thank you sir! I’m a Provo fiber user as well and have wanted to do this exact thing for some time. I’m glad I came across your post. Let me know next time you’re out in Provo and I’d love to take you to lunch as a thank you 😀

  • Dan Garrison

    Steve, with the latest suggested way of dong the set up there’s a problem with trying to use the Google Fiber TV app. It won’t allow you to connect to the boxes from the app unless you are logged into the network on the original Google boxes. I was wondering if it might be possible to configure one of the ports on the EdgeRouter to the same sub net as the Google boxes and then set up port forwarding for the Google TV boxes. If so could some one give a general idea of what would have to be changed? With this method I would assume that the EdgeRouter port would have to be connected to one of the ports on the original Google network box.

  • Jeremy Johnson

    Thanks for the guide and the config files. Have this setup with GF in Ausitn, TX with an Edgerouter X. Its been a couple of days and I still only have link-local IPV6. Any additional stuff I need to do to get this IPV6 stuff going?

  • Keelan Johns

    This worked great for me except for one major issue: my Edgerouter POE’s CPU is maxing out to 100% because it is spawning many dhcpv6-pd-response.pl processes (ssh in, run “top”) upon the router connecting to Google fiber. My internet works but the router is having trouble resolving IPV6. This causes the box to heat up, waste electricity, the webserver (router gui) to run really slowly, decrease the lifespan of the box, etc.
    I am sure there is something silly I am missing but cannot figure it out. For now, I have just plugged my old Google Network box back in… eeek. I have outlined my symptoms and troubleshooting here:
    https://community.ubnt.com/t5/EdgeMAX/Edgerouter-POE-Spawinging-dhcpv6-pd-response-pl-100-CPU/m-p/1918835#U1918835

    Does anyone have any ideas about how to resolve this? Thanks!