Estimated reading time: 3 minutes

I recently bought myself a telephone: the new Google Pixel 10 Pro. Slit, configuro, I transfer data from my old and trusty Huawei P30 Pro e… the time comes to connect it to your home Wi-Fi.

I have a network managed by a FRITZ!Box 7530 AX (principal) and a 4020 as a wired repeater upstairs. I'm going to connect to my main network (tammazzo) and, to my enormous amazement, here's the joke: “Connected, no internet”.

The absurd thing? If I tried to connect to the guest network (tammazzo-lospite), the Pixel was a pleasure to navigate. But on the Guest no NAS, no local services, no home automation. For days I went with a ridiculous workaround: connected to the main Wi-Fi and VPN always active to route packets. Madness.

Since I'm a guy who likes to go by exclusion, I started investigating. Here is the whole story of my attempts, from the holes in the water to the definitive solution.

The first attempts (The great classics that didn't work)

Before touching the highest systems, I tried to clear the field of the most banal suspicions:

1. The name of the device: The Pixel had its neat name (pixel-10-pro) registered in the router. No orphaned legacy from Huawei.
2. Static IPs: On Wi-Fi I had no conflicts because I use DHCP for mobile devices.
3. Forget network: Deleting and re-entering the password had no effect.
4. The Random MAC: It is a security measure of Android. Even turning it off had no effect, but I wanted to give up the random MAC, so I turned it back on right after.

The false clue: The Radio Channels and the DFS

Looking at the FRITZ logs!Box, I noticed that the router kept switching channels on the A band 5 GHz (passing from 36 to the 52 and then to 128) to optimize the network.

Intuition: The upper channels of 5 GHz use the protocol DFS (Dynamic Frequency Selection). If the router detects weather or military radar, ago “radio silence” for a few minutes. The Pixel 10 The Pro saw the Wi-Fi carrier but received no data, branding the network as “without internet” and getting stuck in an infinite loop.

What did I do: I temporarily separated the networks 2.4 and 5 GHz.

• I manually set the channel 36 (which is free of DFS and is always on).
• I even turned off my robot vacuum cleaner which from the logs seemed to be going crazy connecting and disconnecting every time 7 minutes on 2.4 GHz.

It worked for a few hours. I put the Wi-Fi back on 6, I combined the SSIDs under one name… and after two days we were all over again. The Pixel refused to navigate tammazzo.

The turning point: IP and identity issue

If the radio worked on the Guest but not on the main, the problem wasn't the Wi-Fi. It was the routing. Connecting to the main, I could even type the router's IP into the Pixel's browser and see the FRITZ interface!Box. So the phone was talking to the router, but the router prohibited him from going out on the Internet!

I tried setting a Static IP directly on the Pixel (this is. .210), bypassing the FRITZ's DHCP! which perhaps was wrapped with the random MAC of the phone. The situation has improved, but it was not yet the definitive solution and “clean” that I wanted.

The definitive solution: The firewall is a global filter

Exasperated, I went to look through the section Internet > Filtri > Filtri globali from FRITZ!Box and I found some “Global Filters” active by default.

The Pixel 10 Pro makes heavy use of modern network protocols and IPv6 addressing to manage Google services. The FRITZ firewall!Box, Unfortunately, tends to see some of these requests as hostile if the filters are too stringent.

Here are the three combined moves that solved the problem once and for all:

1. Cleaning of devices “ghost”

In the FRITZ menu!Boxes were well there 3 old inactive recordings from previous Pixel attempts (maybe because of the random MAC). I deleted them all to clear the router's memory.

2. Disabling the Teredo filter

In the menu Internet > Filtri > Filtri globali from FRITZ!Box, I removed the check a “Teredo filter active” (Teredo filter). Teredo is an IPv6 tunneling protocol that Pixels often use and that FRITZ!Box was blocking on the main network, effectively denying internet access to the phone.

3. Bye bye IPv6 (The final blow)

My provider has not configured IPv6 addresses, therefore to prevent the phone from continuing to ask for an IPv6 DNS, I went up Internet > Dati di accesso > IPv6 yes to IPv6 support is completely disabled sul FRITZ!Box, forcing the whole thing to work on the old one, solid and well-tested IPv4.

4. Network reset on the Pixel

In the end, I reset the network on my phone “tammazzo” by deleting it and registering again, to erase all traces of the old corrupt handshake.

Conclusions

After turning off the Teredo filter, turned off IPv6 from the router and cleaned up the connections, my Pixel 10 Pro reconnected to tammazzo and since then he never missed a beat again. Navigation, access to your home NAS and no more VPNs turned on randomly on the couch.

If you also have a latest generation Pixel and a FRITZ!Box and you are going crazy behind the “Connected without internet”, leave the radio channels alone: go straight to the router's firewall filters.

And you? You had similar problems with the Android pairing / AVM? Let me know in the comments!