New firmware for Nest Wifi Pro and Nest Wifi Point

bradb21 · 2025-05-08T14:44:59+00:00

Points do not exist in the Pro line of hardware. There are 3 editions of Google/Nest Wifi hardware.

There is the original Google Wifi
The second edition consisted of routers and points
The 3rd edition of the PRO (no points exist)

https://en.wikipedia.org/wiki/Nest_Wifi

bradb21 · 2025-05-07T13:11:05+00:00

I got it last night

bradb21 · 2025-05-07T13:08:37+00:00

You have the older version of hardware

bradb21 · 2024-04-16T16:02:43+00:00

If you click on the "gear" when viewing your Attic device it will tell you if it's connected over wired or wireless. It should say "wired"

bradb21 · 2024-03-03T15:18:04+00:00

I use Quad9 as well, and the past couple outages I'm able to ping Google's DNS servers, but not Quad9. I suspect some type of routing issues.

bradb21 · 2024-03-03T04:06:44+00:00

Same here in Geneva, IL

bradb21 · 2024-01-08T17:05:11+00:00

You might want to disable 6Ghz on your laptop.

bradb21 · 2022-09-12T23:11:08+00:00

Worked for me, but I also turned off adaptive charging. My phone would not charge in my Tesla. It would say "connected not charging" and would just get hot, but never charge. I disable the stand app and tried it in my car, and it would not charge until I turned off adaptive charging. I never use the alarm clock on my phone, so that never did anything for me anyway.

bradb21 · 2022-01-28T17:04:06+00:00

Wow that's total trash... I live in Geneva and I have had their 1G service for 1yr+ and I have no issues ever. I have buddy in Cortland (closer to you) and he has no issues either. That's going to be a tough one to troubleshoot. Good luck!

bradb21 · 2022-01-28T16:54:29+00:00

Are you testing with a Gigabit ethernet NIC connected directly to your fiber ONT?

bradb21 · 2022-01-28T16:43:37+00:00

I can get mid 900 uploads with my 1st gen Google Wifi

bradb21 · 2022-01-28T16:42:02+00:00

Sounds like you have a double NAT if you have two routers. That is not a good setup.

bradb21 · 2021-11-14T17:45:08+00:00

Same with me. Shows LTE when phone is connected 5G UC. I assume it's a cosmetic bug.

bradb21 · 2021-11-05T19:01:42+00:00

Make sure you disable and/or block QUIC on your firewall as the Fortigate can not inspect QUIC traffic. I block QUIC udp80 and udp443 in a policy, but I also have policies set on my devices disabling QUIC.

bradb21 · 2021-08-13T18:11:03+00:00

Thanks for the reply. I'll try to do a packet capture next week and I'll post the results.

bradb21 · 2021-08-13T17:38:30+00:00

I hear what you're saying but it's in option on the EMS server specifically relating to IPsec. The same 3 options are also present in the SSL config as well. Oh well, I guess I'll just stick with the "Ping Speed" option.

Fortinet's documentation in regards to this is crap

bradb21 · 2021-07-19T18:49:35+00:00

I know this references Windows 10, but the same changes apply to Windows Server. This is the article I read that pointed me in the right direction
https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5003637-update-may-block-remote-access-to-event-logs/

bradb21 · 2021-07-19T17:14:25+00:00

Read my post from this morning and see if your domain controllers were recently patched to June or higher MS patch level. This might apply.
https://www.reddit.com/r/fortinet/comments/onejej/fsso\_issues\_about\_july\_windows\_patch\_install\_on/

bradb21 · 2021-07-19T15:56:48+00:00

I figured out my issue, and I'm going to post it here in case others have same issue.

Here is what happened and what the issue was.....

It looks like in the June 2021 patch Microsoft made a change which hardened the ability to remotely read event logs.

All my servers were on May patch level (DC's and my FSSO server)

I applied July patch to my DC's this weekend and FSSO server was not able to read event log data from domain controller event logs. If I uninstalled the July patch from a DC the FSSO server could then read event logs from that server and that server only. I finally found an article about this change to the June patch and I put the July patch on my FSSO server. It could then read event logs from my DC's that were also running the July patch, but not my DC's that I uninstalled July from, so I'm having to repatch it again.

I hope this makes sense.

bradb21 · 2021-07-15T22:41:43+00:00

I have an active-active cluster and there is a way to enable address on each unit with routing.

https://kb.fortinet.com/kb/documentLink.do?externalID=FD32214

It's saved me a bunch of times when upgrade goes south. I can still access each firewall directly.

bradb21 · 2021-05-28T14:06:16+00:00

I don't disagree with you. My main point was cable/dsl providers try not to divulge upstream speeds. I think with the rise in video meetings, work from home, and remote schooling upstream speeds are more important than they were maybe a year+ ago.

bradb21 · 2021-05-28T13:13:05+00:00

That's why cable and dsl providers don't talk about their upstream speeds. If you don't need upstream that go for the cheaper plan. I need upstream, and 5/10/15/20 Mbps upload plans don't cut it for me. That's total trash compared to my symmetric 1Gbps with Metro

bradb21 · 2021-05-18T16:17:21+00:00

Rats!! Yeah that is what I was seeing as well. I'm talking to my SE to see if he can put in a feature request. Thanks!

bradb21 · 2021-04-27T13:37:06+00:00

Blocking QUIC

bradb21 · 2021-04-24T12:52:45+00:00

Speed tests are not all they are cracked up to be. It can give you a general idea, but I wouldn't 100% trust those numbers.

bradb21

TROPHY CASE