Outbound traffic to Amazon space
"Owner Name: Shell Internet (Beijing) Security Technology Co. Ltd." Gee wonder what kind of data mining here collecting. Scary. 
@CrimpOn wrote:Alas, my impression is that Netgear engineers are not assigned to monitor the dozens of community forums. Those of us who do are simply customers who are too cheap to pay for GearHead support (and who also find that members of the community often have more nuanced insight than the "GearHeads"). So, this is my initial impression
I had always thought that Netgear hosted Orbi firmware on "Netgear".
Here are the links I find in the Orbi parameters:
x_advisor_url=https://advisor.ngxcld.com/advisor/direct
x_claimed_url=https://registration.ngxcld.com/registration/status
x_discovery_url=https://presence.ngxcld.com/presence/presence
base_upgrade_url=https://http.fw.updates1.netgear.com/rbr50
fw_download_url=https://http.fw.updates1.netgear.com/rbr50/ww
genie_remote_url=https://genieremote.netgear.com/genie-remote/claimDevice
last_fw_upgrade_url=https://http.fw.updates1.netgear.com/rbr50/V2.3.5/ww
leafp2p_remote_url=http://peernetwork.netgear.com/peernetwork/services/LeafNetsWebServiceV2
leafp2p_replication_hook_url=https://readyshare.netgear.com/device/hook
leafp2p_replication_url=https://readyshare.netgear.com/device/entry
readycloud_fetch_url=https://readycloud.netgear.com/device/entry
readycloud_hook_url=https://readycloud.netgear.com/device/hook
readycloud_upload_url=https://readycloud.netgear.com/directio
Firmware updates seem to be hosted at Netgear.com.
None of these screams out "Amazon Cloud" directly, but the "ngxcld" appears to be in connection with Arlo cameras.
The Arin link seems to be pointing at "security":
WHOIS Source: ARIN
IP Address: 52.0.0.0
Country: usUSA - Washington
Network Name: AWS-SHELL-INTERNET
Owner Name: Shell Internet (Beijing) Security Technology Co. Ltd.I also think it's weird that Orbi has all these links to readycloud when that feature is not implemented on the Orbi platform.
@FURRYe38 wrote:"Owner Name: Shell Internet (Beijing) Security Technology Co. Ltd." Gee wonder what kind of data mining here collecting. Scary.
It's part of Amazon Web Services (the "AWS" part at the front). This is a useful discussion for me. I had assumed that once in Access Point mode, the Orbi reverted to a dumb WiFi AP. Now that I have the occasion to reflect, it is pretty obvious that the Orbi is still going to to "maintenance things" that are not "routing", such as looking for firmware updates, managing Arlo cameras, supporting ReadyShare (Ha!), sending log files(?).
It would be interesting to look at the DNS requests that led to the Orbi wanting to connect to 52.0.0.0.
I wonder if this is something that Voxel might be able to tune up or tune out. I know he's removed some packages from the base file and set them aside for use later of if users want them. Something to ask him about and see. Though this maybe core code which he can't change. 
I know NG and other Mfrs are using Amazon as a platform for there cloud services these days. Been like this for a while now.
Ya I kinda presumed that when in AP mode that analytics would be turned off. I guess not.
@CrimpOn wrote:
@FURRYe38 wrote:"Owner Name: Shell Internet (Beijing) Security Technology Co. Ltd." Gee wonder what kind of data mining here collecting. Scary.
It's part of Amazon Web Services (the "AWS" part at the front). This is a useful discussion for me. I had assumed that once in Access Point mode, the Orbi reverted to a dumb WiFi AP. Now that I have the occasion to reflect, it is pretty obvious that the Orbi is still going to to "maintenance things" that are not "routing", such as looking for firmware updates, managing Arlo cameras, supporting ReadyShare (Ha!), sending log files(?).
It would be interesting to look at the DNS requests that led to the Orbi wanting to connect to 52.0.0.0.
I would think that checking for updates should be only a thing done if a user logs into the UI or then goes tot he FW update section in the UI and selects check for FW updates from the server. Why is this a contant even happening.
Wondering if this is why some users post about there data plans being used up prematurely after Orbi was installed.
@FURRYe38 wrote:I would think that checking for updates should be only a thing done if a user logs into the UI or then goes tot he FW update section in the UI and selects check for FW updates from the server. Why is this a contant even happening.
I agree this seems inefficient (checking frequently for months rather than when the user logs in). It may be a hold-over from the days when Netgear would silently push firmware updates to Orbi. And, since they (apparently) intend to do an auto push for "major" firmware updates (whatever that is, and if they EVER happen), then the Orbi has to check and not wait for the user to log in. I would think "once a week" would be plenty often, unless the firmware was an "urgent fix" to some zero day exploit.
Wondering if this is why some users post about there data plans being used up prematurely after Orbi was installed.
This one I doubt. Doing one http: "get" is at most a few hundred characters. Even a thousand times a day would not create gigabytes of data.
Maybe this is something that we can bring to the attention of the moderators to push to engineering. Would be nice if this could be reviewed and tuned to be less active. 
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more