NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RBR850 / RBS850 Firmware Version v4.6.7.5 Released
No Release Notes at this time. I'll see if I can get some.
Download Link:
https://ntgr.my.salesforce.com/sfc/p/#300000000xsV/a/8b000000saFy/gnaaQgriSv_NWgvrN.dvn786cl4eG45R2.62LEI3edU
F...
>> What is the size of your home? Sq Ft?
>> What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between RBR and RBS📡
>> to begin with depending upon building materials when wirelessly connected.
>> I ran 13 days with zero issues with v5 and RBS flasing anything.
>> Manual channels 1 and 40, 40Mhz only. CTS 64, RBS wireless and wired. 50% Transmit power on the RBR.
>> Traffic Meter enabled set to no limit.
Not sure about the sq-footage, it's a rental. It's an "L" shape though, with the head of the L about 12-15m away from the heel, and the toe about 5m away from that.
All the radios are at 100%, the CTS is 64, it is 20/40 mixed. Most everything is default. I have traffic metering on, and all the logs are also on.
I've taken a debug capture of the network when the problem occurred. Maybe it would help if I sent this to someone?
There were interesting messages in a file called "critical_attach_log_tmp" at the time the satellites went down:
[deleteSatelliteDeviceInfo 5575] satellite-device 542A1BC262E0 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device C4B301DAC0E3 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 2A622873ACC7 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E83A868 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E83C08A disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E63BE1A disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E435216 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 5CAAFDF32AA4 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 542A1BC262E0 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device F8FFC20E85F5 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device C22F97844EAC disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 2CDB0715FBB7 disconnected, delete it
I'm not sure if this is related to the problem or not, but it seems odd.
The rest of the logs don't really make sense to me.
FURRYe38 - can you suggest someone that I might send the debug logs to?
The issue with my wife's Chromebook is still occurring, and still reproducible. It only occurs with the new .5 FW.
Many thanks in advance.
nexus_orbi wrote:>> What is the size of your home? Sq Ft?
>> What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between RBR and RBS📡>> to begin with depending upon building materials when wirelessly connected.
>> I ran 13 days with zero issues with v5 and RBS flasing anything.
>> Manual channels 1 and 40, 40Mhz only. CTS 64, RBS wireless and wired. 50% Transmit power on the RBR.
>> Traffic Meter enabled set to no limit.
Not sure about the sq-footage, it's a rental. It's an "L" shape though, with the head of the L about 12-15m away from the heel, and the toe about 5m away from that.
All the radios are at 100%, the CTS is 64, it is 20/40 mixed. Most everything is default. I have traffic metering on, and all the logs are also on.
I've taken a debug capture of the network when the problem occurred. Maybe it would help if I sent this to someone?
There were interesting messages in a file called "critical_attach_log_tmp" at the time the satellites went down:
[deleteSatelliteDeviceInfo 5575] satellite-device 542A1BC262E0 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device C4B301DAC0E3 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 2A622873ACC7 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E83A868 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E83C08A disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E63BE1A disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E435216 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 5CAAFDF32AA4 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 542A1BC262E0 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device F8FFC20E85F5 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device C22F97844EAC disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 2CDB0715FBB7 disconnected, delete it
I'm not sure if this is related to the problem or not, but it seems odd.
The rest of the logs don't really make sense to me.
Yes, please post up on a site like dropbox and PM me a link to the URL to the log file.
Is AX mode disabled on the RBR?
nexus_orbi wrote:
can you suggest someone that I might send the debug logs to?
The issue with my wife's Chromebook is still occurring, and still reproducible. It only occurs with the new .5 FW.
Many thanks in advance.
nexus_orbi wrote:
>> What is the size of your home? Sq Ft?
>> What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between RBR and RBS📡>> to begin with depending upon building materials when wirelessly connected.
>> I ran 13 days with zero issues with v5 and RBS flasing anything.
>> Manual channels 1 and 40, 40Mhz only. CTS 64, RBS wireless and wired. 50% Transmit power on the RBR.
>> Traffic Meter enabled set to no limit.
Not sure about the sq-footage, it's a rental. It's an "L" shape though, with the head of the L about 12-15m away from the heel, and the toe about 5m away from that.
All the radios are at 100%, the CTS is 64, it is 20/40 mixed. Most everything is default. I have traffic metering on, and all the logs are also on.
I've taken a debug capture of the network when the problem occurred. Maybe it would help if I sent this to someone?
There were interesting messages in a file called "critical_attach_log_tmp" at the time the satellites went down:
[deleteSatelliteDeviceInfo 5575] satellite-device 542A1BC262E0 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device C4B301DAC0E3 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 2A622873ACC7 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E83A868 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E83C08A disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E63BE1A disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 949F3E435216 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 5CAAFDF32AA4 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 542A1BC262E0 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device F8FFC20E85F5 disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device C22F97844EAC disconnected, delete it
[deleteSatelliteDeviceInfo 5575] satellite-device 2CDB0715FBB7 disconnected, delete itI'm not sure if this is related to the problem or not, but it seems odd.
The rest of the logs don't really make sense to me.
- I've had my RTS/CTS set to 500 for a number of months now without issues and all devices running smoothly. I've also had firmware 4.6.7.5 running for approximately 4 weeks without issues any issuesđź‘Ť Love it!
- I haven’t had any issues with my satellite since I dropped (enabled) RTS / CTS to 2304.
I suspect the issue is something to do with setting (disabling) RTS/CTS to the maximum value and video calls.
