More specifically behind a FIOS firewall but really much of the information below applies to any firewall you might put Google Wifi behind. I’ll dig into what you need to know and how to make some key services work while buried in a double-NAT, double firewall deployment.
Google Wifi (gWifi) is a relatively new mesh networking solution from Google that has a simple goal: Provide stupid easy, crazy fast, blanketed wifi coverage for your entire house regardless of size. This is done via very small (4.17” diameter) but very aesthetically pleasing Wifi “Points”, as Google calls them, that you place in key areas of your home to provide coverage. One Wifi Point will act as primary and connect via a BaseT Ethernet cable to your existing modem or router. The other Points will connect to the primary wirelessly and expand the signal of a single Wireless LAN (WLAN). The gWifi solution operates on both the 2.4GHz and 5GHz bands but unlike most other wireless routers, gWifi enables seamless and automatic switching between the bands as required, using a single SSID. Every client available today is supported here: 802.11a/b/g/n/ac. No need to set up and manually switch between discrete SSIDs for each band. gWifi will place your device on the best possible band given its capabilities and proximity to the gWifi Points.
With the primary router cabled to the FIOS router, there is one additional switched Ethernet port available on that device and two ports available in each secondary mesh Point for wired Ethernet clients. Need more coverage? Add more gWifi Points. Unlike most routers there is no web interface here to access for management, you must use the gWifi app installed on your mobile device. The available features are intentionally limited to keep ease of use high, so those looking for advanced features like VPN may not find what they need here. Luckily, everything I need appears to be intact: custom DNS, DHCP reservations and port forwarding. Another important callout is that you cannot currently change the IP range that gWifi uses for DHCP assignment, it is and always will be 192.168.86.0/24. If this range is already in use on your network for some reason, gWifi will shift to 192.168.85.0/24. **Update - Google has now made it possible to change both the router LAN address as well as the DHCP pool range, so .86 is no longer required. If you don't care or have a good reason to change, honestly, just leave the default.

General setup is fairly simple: Connect an Ethernet cable to the WAN port of your primary gWifi Point from the switch side of your modem or firewall and power on. Download the gWifi app to your phone or tablet, find the device and follow the prompts to configure. Additional Points are easily added through the setup process which will help to ensure ideal placement for maximum coverage. Connect your wireless clients to the new network like normal and you’re done. The rest of this post will dig into more advanced topics around presenting services connected to the gWifi network out to the internet, or to clients connected to the FIOS network.

Network Architecture

In Google’s Wifi documentation, the clear preferred deployment model is the Google router connected directly to a broadband modem. This enables Google Wifi to be the primary router, AP and firewall of the house brokering all connections to the internet. Well, what if you don’t have a cable modem because you have FIOS or similar service? Or don’t really want gWifi as your barrier to the big bad web? In my particular case I use FIOS for internet access only, my TV service is provided via PlayStation Vue so I have no Set Top Boxes (STB) and my phone service is provided by Ooma. For those of us with FIOS, we have ONT boxes in our garages that connect to a router inside the house. If you have speeds >100Mbps this connection is made using a Cat5e cable instead of coax for lower speeds. I’ve read that while it appears possible to successfully replace the FIOS router with gWifi, there are some mixed results doing this. Really, this should only be considered if you are an internet-only customer in my view. If you have STBs, this won’t work as you need a coax connection between them and the router to complete the MoCa network. The easiest thing to do is simply leave the FIOS router in place as is and install the gWifi pieces behind it.
What this will create, is 2 stateful firewalls, directly connected LAN to WAN, each with their own separate subnets, with the Google device having a leg in both networks. Leave DHCP enabled on the FIOS router to serve the clients directly connected via the Ethernet switch, including the WAN port of the Google router. There is no way currently to manually specify a static IP address for the gWifi router, so it must receive via DHCP. **Update - you can now set a static IP for the WAN side of the primary gWifi router if you wish! 
Important to note that the gWifi router can be put into bridge mode, thus making your FIOS router ‘primary’ but doing so will disable the mesh capabilities of the gWifi system. Only do this if you have a single gWifi router or knowingly want to disable mesh (why buy gWifi??).

The diagram below displays my home network and how I installed the gWifi system. The FIOS router is still my primary firewall and gateway to the internet, everything ultimately connects behind this device. I have a few devices that connect directly to the FIOS network and a 1Gb run that goes between floors that feeds the primary gWifi router from the FIOS router. The only device I have currently hard wired to the gWifi network is my media server (Plex/ NAS). This gives me 1Gb wired end to end from my PC to my NAS downstairs. All other devices like my PS4, Smart TVs, kid and Chromecast devices connect via wifi. The gWifi devices are depicted as G1, G2 and G3 below.


You’ll notice that the G1 router depicted above, has two IP addresses, 192.168.1.22 on the WAN side and 192.168.86.1 on the LAN side. The .22 address was assigned via DHCP from the FIOS router which I reserved so the G1 device will always receive this IP. This is important as we will configure an upstream static routing rule later that will point to this address, so we need it to not change. The gWifi routers will assign all IPs to all clients they service directly, wired or wireless. The G2 and G3 routers simply serve as extensions of G1 and will serve any clients that connect via proximity. By default, any device attached to the FIOS network (192.168.1.0) will have no knowledge of the .86 network, nor how to get to anything that lives there. So we have to tell the FIOS router how to find the .86 network, if I ever want my PC to connect to file shares hosted my my NAS, for example.

The main configuration activities I’ll cover here are:

• Reserving IP addresses
• Routing between networks
• Port Forwarding key services
• Configuring the Windows Firewall
• Plex remote access

Reserving IP Addresses

In FIOS

First, find the IP assigned to the WAN side of the Google router via the gWifi app under Network Device Settings: Settings > Network & general > wifi points > [primary device] :

Login to the FIOS router and navigate to: Advanced > IP Address Distribution, then click the “Connection List” button. Find the gWifi WAN IP assignment in the connection list, click the pencil to edit and check the box to set the “Static Lease type”. This will ensure that the Google WAN port will always receive this IP.

In gWifi

Port forwarding rules can only be applied to reserved IP addresses, so lock in any PCs or Servers you intend to be configured with rules. To reserve an IP address assigned to any client on the gWifi network, open the app and navigate to: Network & general > Advanced networking > DHCP IP reservations and tap the green + button in the lower corner. Select the chosen device in the list and tap next. The MAC address and type of device is displayed, along with the gWifi Point to which the device is attached. Accept the current IP assignment or change it to suit your needs and tap next to save. 

Routing

As the network exists right now, my PC can’t reach my media server on the .86 network as it doesn’t know how to get there. I could add a persistent route on my PC which would solve the problem for my PC, but a better option would be to configure a global routing rule on the FIOS router. This will enable any client on the FIOS network to be able to connect to the hosts or clients on the gWifi network. Let the router do its job: route traffic. The WAN port of the gWifi router is the gateway for any traffic destined to the .86 network. All traffic in or out of the .86 network will pass through this port. So my routing rule needs to send all traffic from the 192.168.1.0/24 network destined for the 192.168.86.0/24 network to 192.168.1.22. To illustrate this further, the image below depicts the connection from my PC to the the media server and associated hops along the way:
On the FIOS router, navigate to Advanced > Routing and click the “New Route” link in red. Enter the pertinent details and click apply. Traffic is now flowing in the right directions.

Port Forwarding

All network-accessible services, running on a PC or server, listen for connections via network ports, opened within those applications. TCP and UDP protocols with specific port numbers are assigned to applications and made available for access, such as HTTP (web server) listening on TCP 80. For my scenario, I have several ports that I need to open from my media server to make accessible to my PC. Per the diagram below, TCP 445 = SMB (file services), TCP 3389 = RDP and TCP 32400 = Plex server. Anything on the gWifi network that you wish to expose to the internet will need to be port forwarded on both the gWifi and FIOS routers, unless it advertises itself as a UPnP (Universal Plug and Play) capable service that can set its own rule on the router, which gWifi will allow. Plex happens to be one of those services, so TCP 32400 is automatically opened through the gWifi router. Currently there is no way to view or control UPnP-configured rules in the gWifi app, so you could have a slew of ports opened and not even know it. The only option at the moment is to disable UPnP entirely within the gWifi app. Hopefully Google will fix this in the near future.

The other two ports to be opened are done so with manual port forwarding rules in the gWifi app. Navigate to: Network & general > Advanced networking > Port forwarding and tap the green + button. Choose a device to forward a port from, which will only be possible if you reserved the IP address on that device. Select TCP, UDP or both as well as the internal and external ports. Both are required here. Tapping done will create the rule and set it as active.  

After this step all required rules are in place on both the FIOS and gWifi router and the media server is accessible from the FIOS network. The image below shows everything configured so far along with the traffic flow.

Windows Firewall

Because my media server is a Windows box, if you need to access resources connected to the gWifi network such as NAS or Plex, you must allow these connections through the Windows firewall. By default, the Windows Firewall blocks all inbound connections unless a specific rule exists otherwise. Create a new custom firewall rule on the PC or server allowing traffic from the gateway of the FIOS network: 192.168.1.1/24. This will treat all traffic sourced from the FIOS network as trusted. Remember this entire network segment is already behind a firewall to the internet, the FIOS router. So you can safely port forward hosts on the gWifi network to the inside of the FIOS network.  The new rule should be custom allowing all programs and all ports when applied to the remote IP address of the FIOS router. If you want to get more granular and only allow access to the specific ports you are exposing, that is an option as well.

Plex Remote Access

One additional step is required if you want to configure Plex with remote access. An additional port must be forwarded out from the FIOS router to allow an internal connection to TCP 32400. Log into the FIOS router and navigate to Firewall Settings > Port Forwarding. Add a new rule and make sure to click the Advanced button. Enter the IP addresses, ports and dropdowns per the screenshot below. Choose specify IP, enter the IP address of the Plex server, forward to port 32400. For the destination port, which is what will be exposed to the internet, you can either custom create the number or match the random 5-digit port generated in the Plex settings. Either way, these port numbers must match between the Plex server and the FIOS router. It’s probably best to not expose TCP 32400 directly to the internet. I don’t know of a Plex specific exploit but the service behind this port is well known so best not to advertise what it is.
Once the rule is in place and active, the Plex service should report as fully accessible. If the following dialog reports any issues, try specifying a manual public port and recreate the port forwarding rule on the FIOS router.

The diagram below depicts the remote access connection originating on the public internet, forwarding to the Plex service inside through both routers. Now your Plex server is accessible from anywhere on the internet. Remember that the public port can be any number you want.

Final Thoughts

Overall my experience with the gWifi system has been quite good. Elegant, unobtrusive, high performance and so simple. There’s a lot of high-end competition in the mesh wifi business right now and Google does a really good job, assuming you don’t require too many advanced features. Google also includes some decent performance testing tools in the gWifi app so you can gauge the performance of the speed to the internet, the wifi clients and the mesh itself as well as figure out where any problems might lie.
   

You can view a device’s network consumption real time and shut down any client you choose or give that device network priority for up to 4 hours. Being able to group and schedule internet access for particular devices is especially useful as a parent. If you have Sonos in the house, make sure to setup all devices using Standard mode connected to the new gWifi network. Boost mode will still work if required, but make sure to keep all devices on the same network for ease of interoperability. It appears problematic to have a controller on the other side of a firewall with all the Sonos devices behind it, due to the number of ports and connections required.

Rumors on the future of Google Voice (gVoice) have been abound for well over a year now, with most indications pointing to an eventual consolidation with the G+ Hangouts app, that could be announced at Google I/O soon. As of yesterday 5/15/14, the long awaited closing of the gVoice API (XMPP) to 3rd parties has happened or soon will in the next few days. snrb Labs, creators of Android VOIP stalwart app GrooVe IP, has been warning about this shift for a long time and as of yesterday no longer supports gVoice users. GrooVe IP formerly integrated with the gVoice service via XMPP allowing users to make outbound voice calls over cellular data plans or wifi service using gVoice phone numbers, thus conserving cellular minutes. This is appealing for obvious reasons and delivers on the core value proposition of VOIP. There is also the slightly more complicated SIP client method that requires a bit more setup and has more moving parts on the backend. Any XMPP integration is now dead there too, however.

gVoice has had a good run

Despite the ability to make free calls over VOIP via 3rd-party app integration, gVoice in its current state has a host of other useful features, albeit mostly for inbound calls.

• Cellular voicemail integration/ replacement – in my phone, instead of using Verizon for vmail service, gVoice captures the messages which are then (somewhat poorly) transcripted to text and emailed to me along with a flash audio file. I can play any message from my phone via the voice app, via email or /voice site on any PC. No dialing into a legacy central voicemail service to get messages.

• Multi-ring – gVoice allows users to specify multiple end points to route incoming calls. I could have my cell, my wife’s cell and the house phone all ring when anyone calls my gVoice number.

• Call screening/ blocking – gVoice provides a great buffer and allows you to obfuscate your “real” phone number. Any caller that comes in via my gVoice number must first announce themselves, then I have the option to accept the call, send them straight to vmail, or listen to them live while they leave a message and pick up during if I choose. Just like old-school answering machine screening. You can also permanently block any caller that comes in via the service through a few creative means (not in service message).

• SMS consolidation – gVoice supports in/outbound text messaging too which comes with the same benefits as voice calls in that they show up on your phone and in email. With gmail integration, you can simply reply to a gVoice text message from email and the recipient will get the text message on their device.
• Caller Rules – Another great feature of gVoice allows users to specify calling rules based on the caller profile. If they’re in your contacts list you could: ring all phones, use a personal greeting and don’t screen. If anonymous: ring only mobile, use a generic greeting and screen. Lots of options and customizable possibilities here.

This is the end

Is the end near for gVoice? I certainly hope not, as outbound VOIP calling was far from one of the most useful features I enjoy. Google is an advertising company, first and foremost, and people forget that. Yes they are extremely profitable and lead some of the best innovation of the day, but you have to consider why Google invests in the technology it does. gVoice came out before Google’s speech-to-text initiative, which clearly benefitted from the work done and data collected in gVoice. It was possibly why gVoice was created in the first place! Google invests in technologies to bolster its core search business or related offerings. Once that pipeline runs dry it might kill the initiative or integrate it into something else. gVoice fed the core search business helping to bring voice to that space, which is now a core feature in Android fed Google searches (“Ok, Google”). gVoice has served its purpose for Google. The lack of development effort or improvement to gVoice is pretty glaring at this point. The last update to the Android app was almost 8 months ago and google.com/voice hasn’t changed in a very long time.

Google is still betting big on Google+ and the more it can do to attract and retain users in that ecosphere the better. I use Hangouts on my Android devices but I’m still one of the early Google adopter hold-outs who still does not have a G+ profile. I’ll hold out as long as I can but Google is trying very hard to close the loop and slowly force everyone into G+. At some point, if you want to be social at all in any capacity in the Google universe, you will have to have a G+ profile. Why? Laser focused and relevant advertising based on a wide spectrum view of all of your data. Period. The data Google amasses on its users is extremely valuable to advertisers.

So, what is next?

The future of gVoice and its current features is uncertain. A voice-enabled Hangouts app seems inevitable and a logical step for Google to make. Will most of the features I currently use in gVoice disappear at some point? Probably. With XMPP access gone, apps like GrooVe IP have had to find other means to provide their services. GrooVe IP has partnered with ring.to (backed by bandwidth.com) to carry this torch forward. This will require porting your gVoice number to ring.to or generating a new number via GrooVe IP. SMS is not currently supported with the new solution which is a bummer, but GrooVe says it’s coming. The good news is that you can still make free calls using VOIP on your Android device using your gVoice number if you wish. The bad news is that all of the gVoice integration goodness is gone and it will take the 3rd parties a while to get their solutions up to par.