Firewalla Gold Tutorial: Google Wifi Mesh network with Gold (Beta)

Follow

Comments

10 comments

  • Avatar
    Quakewalla

    Thank you for this document, but does this scenario create a "double NAT" for the devices on the Mesh?

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    No, there is no double NAT ...   This special trick turns the Google wifi (which doesn't want to be an AP) into an AP

    0
    Comment actions Permalink
  • Avatar
    Chris Dillard

    How stable is this setup? I'm considering the Gold and currently running Google WiFi. I may end up going with different access points in the future but was hoping to run the Gold along with Google WiFi for a period.

    1
    Comment actions Permalink
  • Avatar
    Firewalla

    There are a few people using it, should be usable.    If you are going to a new mesh, avoid google/nest wifi, it is probably the only mesh out there refuse to support AP or bridge mode.   

    1
    Comment actions Permalink
  • Avatar
    Shawn Damon

    I must have done something wrong ... My entire wifi went down .... Tutorials like this ... If they are done using video ... That would be much easier...

    0
    Comment actions Permalink
  • Avatar
    Tyler Jones

    This guide worked well for me, but one thing to note:

    Using the Google Home App to add the router and points requires the mobile device to ALSO connect to the same WiFi network; I had to set aside some additional IP's to get the access points added to the mesh.

    A separate question I have: where can I add a switch in this setup for my other devices that also need to be on the same network?

    1
    Comment actions Permalink
  • Avatar
    John Lin

    Ah, I think I see. So, the idea is that 210 and Google WiFi router's .86 are going to broadcast in the same VLAN but since you're limited the DHCP range on the Nest WiFi, it's not to push address and default gateway to devices?

    0
    Comment actions Permalink
  • Avatar
    Chris Dillard

    I haven't gotten my gold yet, but here's my thoughts.

    @Tyler Jones - I'm going to need to add a switch as well. Hoping I can use the 4th port on the firewalla and share that interface with the .210 network in the above example to add additional switch ports to the setup.

    @John Lin - Seems that way to me and the idea of 2 DHCP servers broadcasting on the same Vlan seems less than ideal. Hoping it's stable though. Seems blocking the access points ability to pull IPs from the .210 segment after it happens the first time will keep it to a minimum though and you may just have to keep an eye out for any devices that inadvertently pull a .86 the first time they join the network, assuming there's an IP or 2 left open in the DHCP scope for device mgmt/additional Mac addresses on the access point network.

    0
    Comment actions Permalink
  • Avatar
    Hayden Stobbs

    FYI for anyone that’s interested I got this working although getting the mesh network stable proved tricky. All of the steps mentioned are relevant including the fix when the mesh network eventually moves over to the wrong subnet.

    One thing I’ve noticed is that google nest hub devices [just seems to be the display] does not seem to accept the DHCP relay request from Firewalla, it only likes the mesh subnet which is rather annoying...

    Any questions hit me up, I’m a Cisco engineer.

    0
    Comment actions Permalink
  • Avatar
    Powerland

    Was unable to setup my Google Wifi using this tutorial. I have 80+ devices and although I followed step by step I always have 1 or more AP going down. I'm so sad because right now my gold is sitting on my desk...

    1
    Comment actions Permalink

Please sign in to leave a comment.