01-18-2024 03:01 AM
While setting up Google Wifi, I was asked if I wanted to access the local network. I confirmed.
Despite that, all Wifi devices are getting IP 192.168.86.x I can connect to devices behind Google Wifi like 192.168.0.40.
If 192.168.0.40 is a printer, I can print on it on Windows devices when printing by TCP/IP, however the problem is starting when trying to access it from mobiles.
Airprint search will look for printers only in specified subnet, which by default will be 255.255.255.0.
The main router got subnet 255.255.0.0 however there is no way to change it to match on Google Wifi, as, according to specification, if subnet is in conflict, it will revert to default.
I tried to trick it, and set router to 10.0.0.1 and when Google Wifi connected with default subnet, I changed it to 255.255.0.0. Then I reverted router to 192.168.0.1/255.255.0.0 and Google Wifi remained in 192.168.86.1/255.255.0.0 however is not working at all. Local network, behind Google Wifi is not visible. No possible to ping any decived like 192.168.0.40.
To gain ability to see the deviced, I need to re-set 255.255.255.0 subnet.
The options for Google Wifi are very limited if is about accessing local network behind Google Wifi.
I believe that this is something that cannot be bypased.
I am thinking about getting rid of it and replace with Deco solution, which apparently allow Main point to act as a Assess point with DHCP from router behind it and still able to create mesh with more Deco devices.
Please correct me if I am wrong.
ps. connecting deviced that are wired to Google Wifi network with .86 IP is not an option.
01-25-2024 07:07 AM
The lack of response saying everything.
I decided to abandon the project with these devices and replace them with Deco products that have Access points with Mesh support, Fast Roaming and Beamforming. I could easily incorporate them into the current network without loosing Mesh funcionality and the main router is providing IP addresses. The Google Wifi is going back on eBay.
03-17-2024 04:54 PM
Hi dw-afast-uk,
That certainly isn’t the experience we want you to have, and we apologize for the delay.
You might have something going on here. The subnet mismatch between your Google Wifi network (192.168.86.x) and your existing network (192.168.0.x) is causing issues with local device discovery, particularly for mobile devices using AirPrint. Here's a breakdown of the situation and potential solutions:
Your Google Wifi is creating a separate network with a different subnet (192.168.86.x) compared to your main router's network (192.168.0.x). This segregation prevents devices on different subnets from easily communicating with each other, especially for functionalities like AirPrint that rely on subnet discovery. Google Wifi currently offers limited control over subnet configuration since it also depends on the functions of the ISP's modem/router. While you enabled local network access during setup, it might not translate to full subnet integration.
Potential Solutions:
Additional Considerations:
Here are some troubleshooting steps to try:
You may skip any step that you’ve done already.
Let us know how it goes.
Best,
Dan