Notification

Our software update is being released in phases. New features will gradually roll out across all regions. Stay tuned for updates.

A página que você solicitou não está disponível no seu idioma atualmente. Com o recurso de tradução integrado ao Google Chrome, você pode traduzir instantaneamente qualquer página da Web para o idioma que quiser.
BenS, of the Nebraska Bens
Original Poster
Sep 29, 2023

Multiple Pixel phones disconnect/reconnect to WiFi - other devices continue working fine...

Our family have 4 Pixels - a P7 Pro, two P6a and a P6 Pro.  They've been working fine with our ASUS RT-AC68U since we got them, until about two weeks ago.  Over a 24-hour period, one after another, each phone began a disconnect/reconnect pattern, on both 2.5 and 5GHz bands.

I've updated firmware on the router, updated and rebooted all phones, and tried creating a new network on the router.  My phone remains connected to the WiFi at the local library and other locations, as does my wife's.   A person on the ASUS router forum reports that his P6a still works on his RT-AC68U, FWIW... 

Note that our router does not auto-update firmware, or auto-reboot, it had an uptime of over 2 months around the time this symptom started.  And all other devices in the house - laptops, IoT, streaming boxes - are still behaving normally.  

I've got an old router plugged in via Ethernet, putting out an alternate WiFi network, which we've been using for the phones over the past couple weeks.  It's slower due to the dual-NAT but works as you'd expect.  (it's also an ASUS FWIW)  

I've got another RT-AC68U on order but I have no confidence it'll fix things, or if it does, that I'll ever learn what's gone wrong!  I was in I.T. for decades and even have some network credentials, I'm used to being able to figure out what's going on, but... I'm at a loss.

Here's a snippet of the router's system log while my phone is trying to connect: 
Sep 29 01:35:03 syslog: wlceventd_proc_event(511): eth1: Disassoc F8:1A:2B:F5:68:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-43 
Sep 29 01:35:06 syslog: wlceventd_proc_event(530): eth1: Auth F8:1A:2B:F5:68:91, status: Successful (0), rssi:0 
Sep 29 01:35:06 syslog: wlceventd_proc_event(559): eth1: Assoc F8:1A:2B:F5:68:91, status: Successful (0), rssi:0 
Sep 29 01:35:09 syslog: wlceventd_proc_event(511): eth1: Disassoc F8:1A:2B:F5:68:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-41
Sep 29 01:35:11 syslog: wlceventd_proc_event(530): eth1: Auth F8:1A:2B:F5:68:91, status: Successful (0), rssi:0
Sep 29 01:35:11 syslog: wlceventd_proc_event(559): eth1: Assoc F8:1A:2B:F5:68:91, status: Successful (0), rssi:0
Sep 29 01:35:14 syslog: wlceventd_proc_event(511): eth1: Disassoc F8:1A:2B:F5:68:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-41

...and, here's a bit of Android's log (obtained over adb shell) during the same period:
(apparently that makes the message too long, I'll try to post Android log in a reply)


Why only Pixel phones?  Why did it happen to each phone in turn, roughly 6-8 hours apart?  I'm willing to believe it's the router but... I mean, how??
Details
Connectivity, Network, Bluetooth,Google Pixel 7 Pro
Locked
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Recommended Answer
BenS, of the Nebraska Bens
Original Poster
Oct 17, 2023
A list of devices, I could provide.  A diagram...?  I learned about network diagrams in the classroom, for 3-layer enterprise topologies at a level I never approached in I.T.  In fact by the time I finished my network credentials I'd moved away from IT to documentation and content development.  ($10k wasted but hey, the market changed)  Anyhow, once again, I literally do not know what could be diagrammed about a home network like mine.

Anyhow - can now confirm the offending item was the Firewalla.  Have not had time to figure out why it suddenly began doing that, as I rarely get time to myself here, but will definitely be investigating the next chance I get.

Thanks once again to all the helpful replies!  Sorry about the oversight.  In my defense, the Firewalla box has its power indicator on the TOP, and it's placed well above my eyeline, but it has an identical-looking hole in the FRONT next to the logo, which is actually a reset button, and always showed dark as if there was no power going to the unit...
Diamond Product Expert Detlef M. recommended this
Helpful?
All Replies (4)
BenS, of the Nebraska Bens
Original Poster
Sep 29, 2023
OK here's the Android log:

09-29 00:24:32.747 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=04:42:1a:19:f3:14 reason=3 locally_generated=1
09-29 00:24:32.822 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
09-29 00:24:32.831 1947 1947 I wpa_supplicant: [DHD]<29631.126858> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:16 status:0x0 reason:2
09-29 00:24:32.965 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=AU
09-29 00:24:32.977 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
09-29 00:24:32.995 1947 1947 I wpa_supplicant: wlan0: PMKSA-CACHE-REMOVED 04:42:1a:19:f3:14 0
09-29 00:24:35.279 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
09-29 00:24:35.295 1947 1947 I wpa_supplicant: wlan0: WPA: Updating to KEY_MGMT SAE+PSK for seamless roaming
09-29 00:24:35.295 1947 1947 I wpa_supplicant: wlan0: Trying to associate with SSID 'Headroom2'
09-29 00:24:35.297 1947 1947 I wpa_supplicant: nl80211: key_mgmt_suites=0x402
09-29 00:24:35.381 1947 1947 I wpa_supplicant: [DHD]<29633.809324> wl_cfgvendor_send_supp_eventstring: [wlan0] Connecting with ff:xx:xx:xx:xf:ff ssid "Headroom2",chan_cnt:1
09-29 00:24:35.510 1947 1947 I wpa_supplicant: [DHD]<29633.938816> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:3 status:0x0 reason:0
09-29 00:24:35.514 1947 1947 I wpa_supplicant: [DHD]<29633.942285> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:88 status:0x0 reason:0
09-29 00:24:35.519 1947 1947 I wpa_supplicant: [DHD]<29633.942537> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:16 status:0x0 reason:0
09-29 00:24:35.528 1947 1947 I wpa_supplicant: wlan0: PMKSA-CACHE-ADDED 04:42:1a:19:f3:14 0
09-29 00:24:35.531 1947 1947 I wpa_supplicant: nl80211: key_mgmt_set_key with key_len 32
09-29 00:24:35.545 1947 1947 I wpa_supplicant: wlan0: Associated with 04:42:1a:19:f3:14
09-29 00:24:35.547 1947 1947 I wpa_supplicant: wlan0: WPA: RX message 1 of 4-Way Handshake from 04:42:1a:19:f3:14 (ver=2)
09-29 00:24:35.548 1947 1947 I wpa_supplicant: wlan0: WPA: Sending EAPOL-Key 2/4
09-29 00:24:35.548 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
09-29 00:24:35.555 1947 1947 I wpa_supplicant: [DHD]<29633.984878> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:7 status:0x0 reason:0
09-29 00:24:35.557 1947 1947 I wpa_supplicant: [DHD]<29633.984989> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:1 status:0x0 reason:0
09-29 00:24:35.559 1947 1947 I wpa_supplicant: [DHD]<29633.985035> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:0 status:0x0 reason:0
09-29 00:24:35.559 1947 1947 I wpa_supplicant: wlan0: WPA: RX message 3 of 4-Way Handshake from 04:42:1a:19:f3:14 (ver=2)
09-29 00:24:35.559 1947 1947 I wpa_supplicant: wlan0: WPA: Sending EAPOL-Key 4/4
09-29 00:24:35.606 1947 1947 I wpa_supplicant: wlan0: WPA: Key negotiation completed with 04:42:1a:19:f3:14 [PTK=CCMP GTK=CCMP]
09-29 00:24:35.607 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED – Connection to 04:42:1a:19:f3:14 completed [id=0 id_str=%7B%22configKey%22%3A%22%5C%22Headroom2%5C%22WPA_PSK%22%2C%22creatorUid%22%3A%221000%22%7D]
09-29 00:24:35.610 1947 1947 I wpa_supplicant: WNM: BTM offload enabled. Notify status and return
09-29 00:24:35.617 1391 1861 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{network{195} handle{840924319757} ni{WIFI CONNECTING extra: } created=2023-09-28T14:24:35.617Z Score(Policies : IS_UNMETERED&EVER_USER_SELECTED ; KeepConnected : 0) explicitlySelected lp{{InterfaceName: wlan0 LinkAddresses: [ ] DnsAddresses: [ ] Domains: null MTU: 0 Routes: [ ]}} nc{[ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=400000Kbps LinkDnBandwidth>=400000Kbps Specifier: <WifiNetworkAgentSpecifier [WifiConfiguration=, SSID="Headroom2", BSSID=04:42:1a:19:f3:14, band=2, mMatchLocalOnlySpecifiers=false]> TransportInfo: <SSID: "Headroom2", BSSID: 04:42:1a:19:f3:14, MAC: f8:1a:2b:f5:68:91, IP: null, Security type: 2, Supplicant state: GROUP_HANDSHAKE, Wi-Fi standard: 5, RSSI: -127, Link speed: -1Mbps, Tx Link speed: -1Mbps, Max Supported Tx Link speed: 400Mbps, Rx Link speed: -1Mbps, Max Supported Rx Link speed: 400Mbps, Frequency: 5200MHz, Net ID: 19, Metered hint: false, score: 0, isUsable: true, CarrierMerged: false, SubscriptionId: -1, IsPrimary: 1, Trusted: true, Restricted: false, Ephemeral: false, OEM paid: false, OEM private: false, OSU AP: false, FQDN: <none>, Provider friendly name: <none>, Requesting package name: <none>"Headroom2"wpa2-pskMLO Information: , Is TID-To-Link negotiation supported by the AP: false, AP MLD Address: <none>, AP MLO Link Id: <none>, AP MLO Affiliated links: <none>> AllowedUids: <{1000}> OwnerUid: 1000 AdminUids: [1000] SSID: "Headroom2" UnderlyingNetworks: Null]} factorySerialNumber=7}
09-29 00:24:36.127 1391 1869 D ConnectivityService: Switching to new default network for: uid/pid:1000/1391 activeRequest: 1 callbackRequest: 1 [NetworkRequest [ REQUEST id=1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_VCN_MANAGED RequestorUid: 1000 RequestorPkg: android UnderlyingNetworks: Null] ]] callback flags: 1 order: 2147483647 using NetworkAgentInfo{network{195} handle{840924319757} ni{WIFI CONNECTED extra: } created=2023-09-28T14:24:35.617Z Score(Policies : TRANSPORT_PRIMARY&EVER_EVALUATED&IS_UNMETERED&EVER_USER_SELECTED&EVER_VALIDATED&IS_VALIDATED ; KeepConnected : 0) created 84562174 firstValidated 84562368 lastValidated 84562368 explicitlySelected lp{{InterfaceName: wlan0 LinkAddresses: [ fe80::22d6:b336:8633:5976/64,192.168.0.224/24 ] DnsAddresses: [ /192.168.0.1 ] Domains: null MTU: 0 ServerAddress: /192.168.0.1 TcpBufferSizes: 524288,2097152,8388608,262144,524288,4194304 Routes: [ fe80::/64 -> :: wlan0 mtu 0,192.168.0.0/24 -> 0.0.0.0 wlan0 mtu 0,0.0.0.0/0 -> 192.168.0.1 wlan0 mtu 0 ]}} nc{[ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=13034Kbps LinkDnBandwidth>=35806Kbps Specifier: <WifiNetworkAgentSpecifier [WifiConfiguration=, SSID="Headroom2", BSSID=04:42:1a:19:f3:14, band=2, mMatchLocalOnlySpecifiers=false]> TransportInfo: <SSID: "Headroom2", BSSID: 04:42:1a:19:f3:14, MAC: f8:1a:2b:f5:68:91, IP: /192.168.0.224, Security type: 2, Supplicant state: COMPLETED, Wi-Fi standard: 5, RSSI: -58, Link speed: 400Mbps, Tx Link speed: 400Mbps, Max Supported Tx Link speed: 400Mbps, Rx Link speed: 6Mbps, Max Supported Rx Link speed: 400Mbps, Frequency: 5200MHz, Net ID: 19, Metered hint: false, score: 60, isUsable: true, CarrierMerged: false, SubscriptionId: -1, IsPrimary: 1, Trusted: true, Restricted: false, Ephemeral: false, OEM paid: false, OEM private: false, OSU AP: false, FQDN: <none>, Provider friendly name: <none>, Requesting package name: <none>"Headroom2"wpa2-pskMLO Information: , Is TID-To-Link negotiation supported by the AP: false, AP MLD Address: <none>, AP MLO Link Id: <none>, AP MLO Affiliated links: <none>> SignalStrength: -58 OwnerUid: 1000 AdminUids: [1000] SSID: "Headroom2" UnderlyingNetworks: Null]} factorySerialNumber=7}
09-29 00:24:37.539 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=04:42:1a:19:f3:14 reason=3 locally_generated=1
09-29 00:24:37.596 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
09-29 00:24:37.630 1947 1947 I wpa_supplicant: [DHD]<29635.921602> wl_cfgvendor_send_supp_eventstring: [wlan0] Mode:0 event:16 status:0x0 reason:2
09-29 00:24:37.717 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=AU
09-29 00:24:37.734 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
09-29 00:24:37.745 1947 1947 I wpa_supplicant: wlan0: PMKSA-CACHE-REMOVED 04:42:1a:19:f3:14 0
09-29 00:24:37.770 1947 1947 I wpa_supplicant: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Penelope R.
Diamond Product Expert
Pixel, Android and Accounts.
Sep 29, 2023
Hi BenS, of the Nebraska Bens.  If your Internet Service Provider is unable to suggest a solution to your connectivity issue and you have tried the general WiFi troubleshooting suggestions in the Help Centre HERE don't resolve the problem, you can speak with a Google Support agent using the Contact Us link at the bottom of the Help Centre page who should be able to take a closer look at the problem with you on a 1:1 basis.

Regards, Penny.

BenS, of the Nebraska Bens
Original Poster
Oct 1, 2023
Hey Penelope R., can you un-mark Jim's stock troubleshooting tips as "Recommended Answer" so this thread may potentially attract more replies?  As noted below his initial response, I noted his FAQ some while before I posted here and the issue I'm facing is beyond the scope of his suggestions.  *(I can mark it as "Not Helpful" but I'm not sure if that means I'm knocking points off his reputation or just saying it's not the answer needed...)
Jim Dantin
Diamond Product Expert
I'm a volunteer Mr. Fixit who uses Sherlock Holmes diagnostic techniques.
Oct 1, 2023
I unmarked my reply as being Recommended . No problem.
Last edited Oct 1, 2023
Detlef M.
Diamond Product Expert
I read manuals and void warranties
Sep 30, 2023
Hi BenS, of the Nebraska Bens,

On a hunch -- try: have the phone forget the Wi-Fi network in question, enable airplane mode, then Settings > Apps > See all .. apps > Google Wi-Fi Provisioner > Force stop > Storage & cache > Clear cache, restart the phone, disable airplane mode again then re-add your Wi-Fi.

If that doesn't work, try Settings > Apps > See all .. apps > Google Wi-Fi Provisioner > three dots menu > Uninstall updates instead of clearing the cache above.

Edited for adding forgetting network.
Last edited Sep 30, 2023
Jim Dantin
Diamond Product Expert
I'm a volunteer Mr. Fixit who uses Sherlock Holmes diagnostic techniques.
Oct 1, 2023
User 9199892965697609599 

Your reported symptoms are different from what is being dealt with here. It is quite rude to hijack someone else's thread. Use your own threads for followup comments.
User 9199892965697609599
Oct 1, 2023
I have expressed my view only I didn't hijak anyone thread,how you people comment for solution for every thread,I have given my real time example

I problem expressed by me is same as title of the thread the way expression of problem is different

You mentioned yourself as expected can't you understand that both are facing disconnect issue with wifi.

If I hurt your feelings sorry I want to express it I expressed it since is open for all to comment 

My only point is my user of pixel are facing wifi disconnect issue from past 1 to 2 months no one is focusing on that particular point

Note:I have also posted  thread in this community you have given same reply related to touble shooting (first reply in this thread) none has worked 

If you want really help the community people to come out of the issue please focus on it please don't downgrade your self since you are expert in community 
Detlef M.
Diamond Product Expert
I read manuals and void warranties
Oct 4, 2023
All,

This problem is under investigation by the Pixel team and they are asking anyone affected to contact Google support so they can gather more information.
BenS, of the Nebraska Bens
Original Poster
Recommended Answer
Oct 17, 2023
A list of devices, I could provide.  A diagram...?  I learned about network diagrams in the classroom, for 3-layer enterprise topologies at a level I never approached in I.T.  In fact by the time I finished my network credentials I'd moved away from IT to documentation and content development.  ($10k wasted but hey, the market changed)  Anyhow, once again, I literally do not know what could be diagrammed about a home network like mine.

Anyhow - can now confirm the offending item was the Firewalla.  Have not had time to figure out why it suddenly began doing that, as I rarely get time to myself here, but will definitely be investigating the next chance I get.

Thanks once again to all the helpful replies!  Sorry about the oversight.  In my defense, the Firewalla box has its power indicator on the TOP, and it's placed well above my eyeline, but it has an identical-looking hole in the FRONT next to the logo, which is actually a reset button, and always showed dark as if there was no power going to the unit...
Diamond Product Expert Detlef M. recommended this
Shandra Norman
Oct 17, 2023
As an aside, do you find tech documentation a viable and enjoyable field these days? I did tech pubs for some time a couple decades ago - at a loss for direction right now so just wondering. 
false
8023209808992196062
true
Search Help Center
true
true
true
true
true
1634144
false
Search
Clear search
Close search
Main menu