NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R9000 X10 - 160MHz doesn't work. Also, what SFP part required for 10G port?
I bought the AP in the US, and it seems like 160MHz doesn't work / isn't available. What gives? It looks like there are not enough channels allowed - which is the probably reason for it not working....
Here's the conclusion to my original posting (to summarize everything).
For 160MHz support - indeed there is no DFS channel support (North America) in current FW (1.0.1.36). Therefore, contiguous 160MHz bandwidth is not currently possible. 80+80 MHz support is possbile and seems to work fine. (lower channels 36,40,44,48 bonded with upper channels 149,153,157,161). However, I'm not sure what Wi-Fi clients out there have any support for 80+80.
Regarding 10G port/connectivity - I have been able to connect the R9000's 10G port (via fiber cable with Cisco SFP-10G-SR SFP+ transceivers) to a Netgear ProSafe M4200 switch. That connection is 10Gbps so that's awesome :). From there, you can connect other multi-gig devices (desktops, servers, etc) via either:
- the remaining 10G fiber/SFP port on the switch
- the 5Gbps / 2.5 Gbps LAN ports on the switchAnd voila, that gives you a multi-gig (up to 5Gbps in this setup) Wi-Fi network that's ready for future technologies - 160MHz, MU-MIMO, 11ax (with a different AP).
For now, this is a very expensive setup, without much gain in Wi-Fi speeds. When 160MHz support matures, we can expect a maximum throughput (goodput) of about 1300 Mbps in real life.
WiFi-Geek wrote:
Also - I can't find anywhere in the AP documentation or online what kind of 10G SFP would work to plug into the R9000 for 10G connectivity.
Start here -> https://kb.netgear.com/31408/What-SFP-modules-are-compatible-with-my-Nighthawk-X10-R9000-router?cid=wmt_netgear_organic
I've challengd the Netgear product manager if the X10/R9000 SFP+ interface is limited to some makes/brands and models SFP(+) modules, which would allow only thse accepted for operation. Awaiting the answer any time.
WiFi-Geek wrote:I bought the AP in the US, and it seems like 160MHz doesn't work / isn't available. What gives?
It looks like there are not enough channels allowed - which is the probably reason for it not working. (only 4 channels available on low band, 4 channels on high band).
Typical issue operating a WiFi AP in a foreign legislation. Cause: Some more "sophistcated" WiFi clients (ie. Android) with location services recognize and allow only channels permitted at the current location. In fact, the channels are in the air, but the clients won't see them.
Give me and idea of your locaiton ... I have a US-R9000 here in Switzerland for a test.
Update:
The 5 GHz band channels offer here on this US model only Ch. 36..48 and Ch. 149..165 - while there is no Auto/DFS selection.
These two frequency ranges would - at least in theory - permit a Wave 2 MU-MIMO on 2*80 MHz.
But then, reading some reference documents does list CH. 50 and 114 for a continuous 160 MHz MU-MIMO block - these are partially or complete in the channel block requiring DFS.
Challenged the Netgear PM, too.
But then, reading some reference documents does list CH. 50 and 114 for a continuous 160 MHz MU-MIMO block - these are partially or complete in the channel block requiring DFS.
Challenged the Netgear PM, too.
Thanks for some good info!
Regarding SFP+ : based on your search is there an SFP+ for ethernet cables? I looked up most of these and they are fiber/optic. (I have a 10G LAN/ethernet network card on my desktop).
For 160MHz, I'm using it in the US. It almost seems like this AP has not been certified to use more than channels 36,40,44,48 in the US. (Those are the only available ones in the list). For 160MHz, we would need 36,40,44,48,52,56,60,64.
WiFi-Geek wrote:Thanks for some good info!
Regarding SFP+ : based on your search is there an SFP+ for ethernet cables? I looked up most of these and they are fiber/optic. (I have a 10G LAN/ethernet network card on my desktop).
For 160MHz, I'm using it in the US. It almost seems like this AP has not been certified to use more than channels 36,40,44,48 in the US. (Those are the only available ones in the list). For 160MHz, we would need 36,40,44,48,52,56,60,64.
It will have to support the SFP+ standard to work.
I would think that the 10Gb connection would be best used for a NAS.
WiFi-Geek wrote:For 160MHz, I'm using it in the US. It almost seems like this AP has not been certified to use more than channels 36,40,44,48 in the US. (Those are the only available ones in the list). For 160MHz, we would need 36,40,44,48,52,56,60,64.
Yes - I've just updared my post above, let's copy it to here, too:
The 5 GHz band channels offer here on this US model only Ch. 36..48 and CH. 149..165 - while there is no Auto/DFS selection.These two frequency ranges would - at least in theory - permit a Wave 2 MU-MIMO on 2*80 MHz.
But then, reading some reference documents does list CH. 50 and 114 for a continuous 160 MHz MU-MIMO block - these are partially or complete in the channel block requiring DFS.
No obvious DFS support I'd say, indeed.Regarding SFP+ : based on your search is there an SFP+ for ethernet cables? I looked up most of these and they are fiber/optic. (I have a 10G LAN/ethernet network card on my desktop).
SFP+ 10 GbE 10GBASE-T transceivers exist - but unpayable. What is available in the free market (HP, Dell, Cisco, ProLabs, ...) is about US$600 - or about 1.5 times the R9000 street price and the supported reach is limited, as there is not enough power available per the SFP+ specs to drive the ~100 meters.
Consider adding a Netgear XS708Ev2 (about the same price tag like the transceiver above!) or a XS716E as a starting point, connected by a Netgear AXC7xx DAC (Direct Attach Cable) if the distance X10<->XS7xxE is not to long.FWIW - this is what happens when plugging 1.25 or 2.5 G SFP modules - appears the X10 (resp the AnnapurnaLabs platform) does check for 1 G and 10 G only:
root@R9000:/# dmesg
[1864067.698681] al_eth_sfp_detect: unknown SFP inserted. eeprom content: 10G compliance 0x0, 1G compliance 0x0, sfp+cable 0x0. default to AL_ETH_LM_MODE_10G_DA
...
[1864076.808678] al_eth_sfp_detect: unknown SFP inserted. eeprom content: 10G compliance 0x0, 1G compliance 0x0, sfp+cable 0x0. default to AL_ETH_LM_MODE_10G_DA
...
[1864095.918676] al_eth_sfp_detect: unknown SFP inserted. eeprom content: 10G compliance 0x0, 1G compliance 0x0, sfp+cable 0x0. default to AL_ETH_LM_MODE_10G_DA
Kind of good news: There is no indications of non-matching manufacturer/model information.
