Firewalla Gold SE + GFiber Wi-Fi 6E Router (GR6EXX0C) + Mesh Extender (GE6E220C) — multi-subnet setup confirmed?Firewalla Gold SE + GFiber Wi-Fi 6E Router (GR6EXX0C) + Mesh Extender (GE6E220C) — multi-subnet setup confirmed?

Follow

Daniel

• May 27, 2026 05:04
• Edited

Hi Firewalla community,

Before I pull the trigger on a Gold SE, I want to confirm my proposed setup will work — specifically around Wi-Fi coverage with the GFiber mesh.

**My hardware:**
- Google Fiber Jack (ONT)
- GFiber Wi-Fi 6E Router (GR6EXX0C) + GFiber Wi-Fi 6E Mesh Extender (GE6E220C) — currently running as a mesh pair
- Firewalla Gold SE (planning to purchase)
- TP-Link TL-SG108E managed switch (already purchased)

**Proposed architecture:**
Based on the Gold SE + Google Wifi multi-subnet guide, I'm planning:

- Fiber Jack → Firewalla Port 4 (WAN)
- Firewalla Port 3 → GFiber router WAN port (192.168.200.x isolated subnet, /30)
- Firewalla Port 1 → TL-SG108E managed switch → all wired devices (192.168.151.x)
- GFiber mesh (router + extender) handles Wi-Fi, with DHCP pool restricted to mesh Points only so all client devices get IPs from Firewalla

**My questions:**

1. Has anyone done this with the GR6EXX0C router and GE6E220C extender specifically? The multi-subnet guide was written for older Google Wifi/Nest Wifi hardware and I want to confirm the behavior is the same with the current GFiber Wi-Fi 6E gear.

2. The step I'm most uncertain about is getting the GE6E220C extender to take a 192.168.86.x IP from the GFiber router rather than a 192.168.151.x IP from Firewalla. Will the "Do not allocate" fix in the Firewalla app work the same way for this extender model?

3. Are there any known quirks with the GR6EXX0C or GE6E220C that I should be aware of before starting — MAC address remapping, DHCP pool restrictions in the Google Home app, anything else?

**Context:** I'm running this as a home business network. The Gold SE is specifically for VLAN isolation between a business machine (AI agents) and personal machines, plus outbound traffic monitoring. My partner also works from home and needs reliable Wi-Fi coverage throughout — so getting the mesh working correctly behind the Firewalla is critical.

Any guidance from people who've done something similar with current GFiber hardware would be hugely appreciated. 

Thanks

0

• 

  FirewallaSupportDesk

  • May 27, 2026 06:02

  Google Wifi or Nest Wifi Mesh network with Gold Series (Beta) – Firewalla applies to Google WiFi 6E as well, because when it's in bridge/AP mode, it doesn't support WiFi mesh. Hence method introduced in this document can be used as a workaround. 
  
  Are you following solution 1 or 2 mentioned in the guide? In your Proposed architecture, I don't see how Google WiFi's LAN port is connected. 
  
  Make sure you follow Step 2: Set up a Google Wifi Mesh network with a limited DHCP address range, and only leave the needed number of IP addresses available for your extenders. While configuring, better let no other devices connecting to Google WiFi to avoid them taking the limited IP addresses available. 
  
  
  

  0

  Comment actions Permalink
• 

  Daniel

  • May 27, 2026 06:11

  Thanks for the quick response and for confirming the guide applies to the GFiber Wi-Fi 6E hardware.

  I'll be following Solution 2, since I have a TP-Link TL-SG108E managed switch. Based on your guidance, here's my updated understanding of the architecture:

  - Fiber Jack → Firewalla Port 4 (WAN)
  - Firewalla Port 3 → GFiber router WAN port (globe icon) — isolated 192.168.200.x /30 subnet
  - Firewalla Port 2 → TL-SG108E managed switch
    - Switch port → GFiber router LAN port
    - Switch ports → all wired client devices

  For the DHCP step, I have one extender (GE6E220C), so I'll set the GFiber router's DHCP pool to 192.168.86.2–192.168.86.3 and add the extender on its own before allowing any other devices to connect to the Wi-Fi. I'll widen the range to 192.168.86.2–192.168.86.4 if the extender needs two addresses.

  Two follow-up questions:

  1. For Solution 2 with the TL-SG108E, does the GFiber router's LAN port need to be on a specific VLAN on the managed switch, or does it just plug into any untagged port alongside the other client devices?

  2. Any known quirks specific to the GR6EXX0C or GE6E220C we should watch for that differ from older Google Wifi/Nest Wifi hardware?

  Thanks again!

  0

  Comment actions Permalink
• 

  FirewallaSupportDesk

  • May 27, 2026 07:57

  The architecture looks good to me. 
  1. Using untagged port should just be fine, as long as they first get an IP from Gfiber router. Don't connect the switch to Firewalla port 2 until all extenders are connected. 

  2. None that I'm aware of

  0

  Comment actions Permalink

Please sign in to leave a comment.