Pixel 9 with WiFi7 not connecting at WiFi7 on NWA130be or the 6ghz Band at all.

jpblanch75

As the title states…. device will only connect to Wifi 6 and not Wifi 6ghz or Wifi 7,

Zyxel_Melen

Hi @jpblanch75,

We did a local test that Samsung S24 Ultra and Pixel 8 can connect to NWA130BE's Wi-Fi 7 SSID.

May I know if your NWA130be is in cloud mode or standalone mode?

If is cloud mode, could you enable Zyxel support so we can check? Also need your help to share the org name and pixel 9's MAC.

https://community.zyxel.com/en/discussion/14234/nebula-how-to-turn-on-zyxel-support-access

If it is standalone mode, could you help to collect the diagnostic info for us to check?

https://community.zyxel.com/en/discussion/18869/how-to-collect-the-standalone-ap-diagnostic-info-by-gui

Thanks.

jpblanch75

After toggling Network preference settings on the Pixel 9 i was able to get it connected at Wifi-7 on the 6-Ghz frequency. Doesn't work very well though. Wifi-6 mode on this frequency is Faster.

No Matter what I do it will not connect to Wifi-7 on the 5-Ghz frequency.

I'm currently in Standalone mode. I noticed in the log there are weird errors like Kernel Panics and errors they are going into limited power mode and slots being disabled. These are only happening on the two NWA130be APs and not the NWA50ax-pro AP connected to the same POE Switch.

This tells me it is an AP issue.

I will be going back to Nebula Cloud mode here shortly. I have also collected a log this morning on both of them before changing them.

I cannot upload the logs here because the file compressed the file to *.tar.bz2 which isn't supported here. Weird that a log made by your AP isn't supported.

EDIT: I compressed them to a ZIP.

LivAP-diaginfo-2024-11-29_11-42-45.tar.bz2.zip

BedAP-diaginfo-2024-11-29_11-42-34.tar.bz2.zip

jpblanch75

Moved everything over to Nebula again. Using my Pixel 9 which you don't have, it is not connecting at Wifi-7 on 5ghz. It does't connect at Wifi-6E either. It's only Wifi-6.

Zyxel_Melen

Hi @jpblanch75,

Thanks for your update. Can I add an NWA130BE to your site to reproduce this issue?

jpblanch75

https://community.zyxel.com/en/discussion/comment/72410#Comment_72410

I have two on my site already? Not sure what you mean.

If you're talking about adding your own for a different location sure do what you need to.

By the way, I have 4 Pixel 9 phones in my home.

Zyxel_Melen

Hi @jpblanch75,

Yes, I'm going to add my own for a different location. Thanks for your agreement. But I need your help to change the admin privilege of Zyxel support from read-only to full so I can add my device.

I also noticed that you have some Pixel9 that can have 802.11be but some can only have 802.11ax. We will also check this in the meantime.

Zyxel_Melen

Hi @jpblanch75,

After checking the beacon information that your NWA130BE broadcasts, we found the Wi-Fi capability information has Wi-Fi 7 info from both of your NWA130BE. Therefore, we need your help reconnecting your Pixel 9 to collect the packets when the Pixel 9 connects to the SSID. Before reconnecting, please help to set up remote capture. Here is the FAQ for you to reference:

How to Remote Capture Wireless Packets through an Access Point? — Zyxel Community

Please let me know if you need any help on this.

jpblanch75

https://community.zyxel.com/en/discussion/comment/72473#Comment_72473

I changed the access for you.

All my Pixel 9's are the same. As I said, I can now connect at 802.11be on 6ghz wifi but not at 5ghz which connects at 802.11ax. I have not tested more at 2.4ghz but currently it only connects at 802.11ax as well.

jpblanch75

I will look into doing this tonight when I get out of work.

jpblanch75

https://community.zyxel.com/en/discussion/comment/72480#Comment_72480

This isn't working. I get the following error every time.

The capture session could not be initiated on capture device "rpcap://192.168.5.6:2002/miireg".
(miireg: That device is not up)

I will say that only getting one reply from you while I'm sleeping every 24+ hours is painful.