Menu
What's new
By:
Filters Better Search

Custom firmware build for R7800 v. 1.0.2.30SF

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hmmm...wonder if it's RMA time, then? Don't know if you can still exchange your router by going to the retailer where you bought the router and getting it exchanged, or using the Netgear warranty? Unless there's something else going on with your home network that's broken, sounds like your router may not be working correctly. I think that I had one random reboot, then the router ran fine for a couple of weeks after that until I went back to the Orbi. And haven't experienced a reboot since...Anyways, I'd be looking into an RMA if I were you *smile*.
 
Hi Voxel:
Thanks for your work.
How to install your firmware from netgear stock firmware?
May I install 1.0.2.30SF thru netgear router webgui?

Thanks
Leo
Voxel said:
Continuation of

https://www.snbforums.com/threads/custom-firmware-build-for-r7800.36859/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-22sf.37222/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-23sf-v-1-0-2-24sf.37477/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-25sf-v-1-0-2-29sf.38032/

New version of my custom firmware build: 1.0.2.30SF.

Changes (vs 1.0.2.29SF):
1. Bridge mode is working now (bug in stock GPL source codes (git_home/qca-hostap.git).
2. OpenVPN is upgraded 2.4.0->2.4.1.
3. ethtool is upgraded 4.8->4.10.
4. Synchronization of other binaries with the stock firmware to avoid “bridge mode” bug.
5. OpenVPN init script is changed to avoid problems with some clients.
6. Some internal optimization.

Thanks to vladlenas and Csection for testing.

The links are:

https://www.mediafire.com/folder/tyj61i5uc610w/voxel-firmware

or

http://ownweb.eu/Downloads/

No reset is needed to upgrade from my previous versions.

Voxel.
Click to expand...
 
Just install via the router GUI.
 
I found these logs causing the instablity of the QOS function. As its broken when the client is offline for 5-10 hrs and try to resume the same closed session from browser.

it also reset the devices wise priority.

Memory: 49MB 436MB = 485MB total
Memory: 482500k/488644k available, 14140k reserved, 0K highmem
smem_find(137, 80): wrong size 72

sysinit: Retype password:Upload limit speed is 10 KB/s

sysinit: Download limit speed is 0 KB/s

PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [mem 0x08000000-0x0fefffff]
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI: bus1: Fast back to back transfers disabled




sysinit: streamboost: Automatic updates are disabled. Using existing files.
current version: V1.0.0.251; new version: V1.0.0.288
the above line repeated 30 times+ over and over again


sysinit: Could not connect to 127.0.0.1:9000


sysinit: streamboost: Automatic updates are disabled. Using existing files.

current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
vap-0: ieee80211_beacon_update: TIM updated, pending 1, off 0, len 1
vap-0: []ieee80211_beacon_update: TIM updated, pending 0, off 0, len 1
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
vap-0: []ieee80211_beacon_update: TIM updated, pending 1, off 0, len 1
vap-0: []ieee80211_beacon_update: TIM updated, pending 0, off 0, len 1
current version: V1.0.0.251; new version: V1.0.0.288
vap-0: []ieee80211_beacon_update: TIM updated, pending 1, off 0, len 1
vap-0: []ieee80211_beacon_update: TIM updated, pending 0, off 0, len 1
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
vap-0: []ieee80211_beacon_update: TIM updated, pending 1, off 0, len 1
vap-0: ]ieee80211_beacon_update: TIM updated, pending 0, off 0, len 1
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
current version: V1.0.0.251; new version: V1.0.0.288
sysinit: StreamBoost: Restarting

sysinit: streamboost: StreamBoost: Executing start all

current version: V1.0.0.251; new version: V1.0.0.288
sysinit: [ OK ] 60_ozker stop
sysinit: [ OK ] 52_p0f stop

sysinit: [ OK ] 50_drflocs stop

sysinit: [ OK ] 49_cape stop

sysinit: [ OK ] 45_flowman stop

sysinit: [ OK ] 44_overlord stop

sysinit: [ OK ] 43_flowmark stop

sysinit: [ OK ] 40_qdiscman stop

sysinit: Terminated

sysinit: Terminated

sysinit: Terminated

sysinit: Terminated
 
Last edited:
was the version it referring to is Language. If so my router says the current 288 why it is saying current as 251 instead of 288

why did the streamboost killed itself.
 
i did tried to reboot the streamboost.

following failed

oot@R7800:/# /bin/sh /etc/init.d/streamboost restart
StreamBoost: Restarting
streamboost: StreamBoost: Executing start all
[ OK ] 01_redis start
[ OK ] 10_policy-reader start
[ OK ] 11_sbsaved start
[ OK ] 12_settings-loader start
[ OK ] 13_prio-reader start
[ OK ] 25_sea start
[ OK ] 30_sbnoded start
[ OK ] 31_nodedetectd start
[ OK ] 32_sbnamed start
[ OK ] 33_sbmacouid start
[ OK ] 34_jigglyp0f start
[ OK ] 35_leash start
streamboost: Action
[ FAIL ] 40_qdiscman start
Setting up qdiscs on interface brwan
Setting up qdiscs on interface br0
RTNETLINK answers: Invalid argument
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
streamboost: StreamBoost: Executing stop all
streamboost: Automatic updates are disabled. Using existing files.
[ OK ] 60_ozker stop
[ OK ] 52_p0f stop
[ OK ] 50_drflocs stop
[ OK ] 49_cape stop
[ OK ] 45_flowman stop
[ OK ] 44_overlord stop
[ OK ] 43_flowmark stop
[ OK ] 40_qdiscman stop
[ OK ] 35_leash stop
[ OK ] 34_jigglyp0f stop
[ OK ] 33_sbmacouid stop
[ OK ] 32_sbnamed stop
[ OK ] 31_nodedetectd stop
[ OK ] 30_sbnoded stop
[ OK ] 25_sea stop
[ OK ] 13_prio-reader stop
[ OK ] 12_settings-loader stop
[ OK ] 11_sbsaved stop
[ OK ] 10_policy-reader stop
[ OK ] 01_redis stop
streamboost: flushing conntrack
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
killall: poll_set_priority: no process killed
root@R7800:/#
root@R7800:/#
 
QDISCS top
qdisc is short for 'queueing discipline' and it is elementary to
understanding traffic control. Whenever the kernel needs to send a
packet to an interface, it is enqueued to the qdisc configured for
that interface. Immediately afterwards, the kernel tries to get as
many packets as possible from the qdisc, for giving them to the
network adaptor driver.

A simple QDISC is the 'pfifo' one, which does no processing at all
and is a pure First In, First Out queue. It does however store
traffic when the network interface can't handle it momentarily.
 
Hi Voxel.

any help would be appreciated. Why the qdiscman is failed to start in the mid of operation of the router.

I did raised case.

Also i am not sure why the GUI language version keep on insisting old and says new eventhough it is in new version as per the current 1.0.2.28 the gui is 1.0.0.288 instead of 1.0.0.251
 
Hi Voxel,

Let me know if this could be hardware bug. As i was so far not able to resolve the issue even after re-flashing twice the QOS is broken easily and it doesnt hold the priority and at time wireless client facing internet disconnect issues.

Also i cant see why the logs says gui version .

Let me know your thoughts.
 
But so far wired clients not much affected. No slow internet. Any clients wired or wireless cant demand 90% all the time of my 100Mbps. The max i see for wireless on AC band with 586Mbps can reach 75Mbps of Internet speed. But i can play 4k with minimal bufferring as possible. But when a heavy download is happening in the destop the streaming is keep on buffering and sometimes the app exit the streaming and go back to home screen.

I am sure the QOS is broken . I dont know if this was after the database update . or its hardware fault or firmware. No idea.


I think i am cursed with this model. 2nd router i am facing issues with no piece of mind.

I did used a good amount of Internet but no piece of mind for it to work without flaws.

I didnt do much of forwarding or not all of my 14 clients consume bandwidth for it to crash . It just a disconnected idle client re-connecting the router gui making it to crash offten. I have to reboot to make it work And it will again crash no matter.
 
ulaganath said:
i did tried to reboot the streamboost.

following failed

oot@R7800:/# /bin/sh /etc/init.d/streamboost restart
StreamBoost: Restarting
streamboost: StreamBoost: Executing start all
[ OK ] 01_redis start
[ OK ] 10_policy-reader start
[ OK ] 11_sbsaved start
[ OK ] 12_settings-loader start
[ OK ] 13_prio-reader start
[ OK ] 25_sea start
[ OK ] 30_sbnoded start
[ OK ] 31_nodedetectd start
[ OK ] 32_sbnamed start
[ OK ] 33_sbmacouid start
[ OK ] 34_jigglyp0f start
[ OK ] 35_leash start
streamboost: Action
[ FAIL ] 40_qdiscman start
Setting up qdiscs on interface brwan
Setting up qdiscs on interface br0
RTNETLINK answers: Invalid argument
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
streamboost: StreamBoost: Executing stop all
streamboost: Automatic updates are disabled. Using existing files.
[ OK ] 60_ozker stop
[ OK ] 52_p0f stop
[ OK ] 50_drflocs stop
[ OK ] 49_cape stop
[ OK ] 45_flowman stop
[ OK ] 44_overlord stop
[ OK ] 43_flowmark stop
[ OK ] 40_qdiscman stop
[ OK ] 35_leash stop
[ OK ] 34_jigglyp0f stop
[ OK ] 33_sbmacouid stop
[ OK ] 32_sbnamed stop
[ OK ] 31_nodedetectd stop
[ OK ] 30_sbnoded stop
[ OK ] 25_sea stop
[ OK ] 13_prio-reader stop
[ OK ] 12_settings-loader stop
[ OK ] 11_sbsaved stop
[ OK ] 10_policy-reader stop
[ OK ] 01_redis stop
streamboost: flushing conntrack
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
killall: poll_set_priority: no process killed
root@R7800:/#
root@R7800:/#
Click to expand...

I am back after my short vacations.

Regarding your problems: as far as I understand you use stock firmware. So why do you ask in this thread? This thread is related to my custom build of firmware. For me it is troublesome to process stock firmware problems: I am using my own.

Anyway, as far as I remember there were some bugs in streamboost in the stock firmware and I had to correct them in my version. At least checked right now:

Code: 
root@nighthawk:~$ /etc/init.d/streamboost restart
StreamBoost: Restarting
streamboost: StreamBoost: Executing start all
 [  OK  ] 60_ozker stop
 [  OK  ] 52_p0f stop
 [  OK  ] 50_drflocs stop
 [  OK  ] 49_cape stop
 [  OK  ] 45_flowman stop
 [  OK  ] 44_overlord stop
 [  OK  ] 43_flowmark stop
 [  OK  ] 40_qdiscman stop
 [  OK  ] 35_leash stop
 [  OK  ] 34_jigglyp0f stop
 [  OK  ] 33_sbmacouid stop
 [  OK  ] 32_sbnamed stop
 [  OK  ] 31_nodedetectd stop
 [  OK  ] 30_sbnoded stop
 [  OK  ] 25_sea stop
 [  OK  ] 13_prio-reader stop
 [  OK  ] 12_settings-loader stop
 [  OK  ] 11_sbsaved stop
 [  OK  ] 10_policy-reader stop
 [  OK  ] 01_redis stop
streamboost: flushing conntrack
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
killall: poll_set_priority: no process killed
streamboost: StreamBoost: Executing start all
 [  OK  ] 01_redis start
 [  OK  ] 10_policy-reader start
 [  OK  ] 11_sbsaved start
 [  OK  ] 12_settings-loader start
 [  OK  ] 13_prio-reader start
 [  OK  ] 25_sea start
 [  OK  ] 30_sbnoded start
 [  OK  ] 31_nodedetectd start
 [  OK  ] 32_sbnamed start
 [  OK  ] 33_sbmacouid start
 [  OK  ] 34_jigglyp0f start
 [  OK  ] 35_leash start
 [  OK  ] 40_qdiscman start
 [  OK  ] 43_flowmark start
 [  OK  ] 44_overlord start
 [  OK  ] 45_flowman start
 [  OK  ] 49_cape start
 [  OK  ] 50_drflocs start
 [  OK  ] 52_p0f start
 [  OK  ] 60_ozker start
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
streamboost: streamboost update
Downloading https://updates.r7800.netgear.streamboost.yeti.bigfootnetworks.com/banana/packages-2/Packages.gz.
Updated list of available packages in /var/opkg-lists/streamboost.
streamboost: [  OK  ] Everything is up-to-date.

Messages related to iptables are related to NETGEAR's own firewall and might be ignored.

Voxel.
 
Last edited:
Wurstcase said:
Hey guys, maybe someone here can help me.
I'm currently running this version of the firmware and i keep getting random restarts on a nearly daily basis and have no clue why this is happening. Log File only states that firmware is initialized after the reboot so i can't check what happened before the reboot.

Any of you guys has any idea what i can do to fix those random restarts ?
Click to expand...

I agree with RogerSC that maybe it is RMA case. I use my own build of course :) and currently my router works almost 15 days w/o any reboots:

Code: 
root@nighthawk:~$ uptime
 19:12:25 up 14 days, 22:44,  load average: 4.03, 4.04, 4.04

Anyway, IMO you have to try 30/30/30 reset.

Voxel.
 
Hi Voxel
thanks for your development
I had ur firmware for 3days
it very stable than stock FW
thanks



Voxel said:
Continuation of

https://www.snbforums.com/threads/custom-firmware-build-for-r7800.36859/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-22sf.37222/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-23sf-v-1-0-2-24sf.37477/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-25sf-v-1-0-2-29sf.38032/

New version of my custom firmware build: 1.0.2.30SF.

Changes (vs 1.0.2.29SF):
1. Bridge mode is working now (bug in stock GPL source codes (git_home/qca-hostap.git).
2. OpenVPN is upgraded 2.4.0->2.4.1.
3. ethtool is upgraded 4.8->4.10.
4. Synchronization of other binaries with the stock firmware to avoid “bridge mode” bug.
5. OpenVPN init script is changed to avoid problems with some clients.
6. Some internal optimization.

Thanks to vladlenas and Csection for testing.

The links are:

https://www.mediafire.com/folder/tyj61i5uc610w/voxel-firmware

or

http://ownweb.eu/Downloads/

No reset is needed to upgrade from my previous versions.

Voxel.
Click to expand...
 
I had flashed your firmware as well still the streamboost didnt work as expected. All was due the latest database update which i checked yesterday. it brokes very easily and quickly as i can see -ve data transfer and not realtime live bandwidth thought the live bandwidth is little delayed updated but it still shows the peak consuming bandwidth devices of top 5 or all.
 
ulaganath said:
Hi Voxel.

any help would be appreciated. Why the qdiscman is failed to start in the mid of operation of the router.

I did raised case.

Also i am not sure why the GUI language version keep on insisting old and says new eventhough it is in new version as per the current 1.0.2.28 the gui is 1.0.0.288 instead of 1.0.0.251
Click to expand...
Current version is 1.0.0.288 as far as I am aware. Also did you hard reset after re-installing the Netgear firmware and did you re enter all your settings manually. I'm not having the issues you are either with Streamboost, its all working as it should pretty much and I get less bandwidth than you at 57Mbps. It sounds like your firmware is corrupt possibly, I would reset the router, reload the routers firmware, reset it again using the small pinhole on the back for each reset, then enter your settings by hand.
 
Last edited:
I finally did that resetting the router doesnt work. I have to downgrade to 0.20 and then come back to 2.28 for the database to be reverted to 2016

it was working fine and never almost unbreakable. All works and hardly i see any wifi clients disconnected net issues.

But when the moment i update the database the router all started acting wiered. I did reseted to full 30/30/30 but no luck the qos is broken again easily

I have to again go back to old firmware and then back to 2.28 and disable the auto update feature.
 
ulaganath said:
I finally did that resetting the router doesnt work. I have to downgrade to 0.20 and then come back to 2.28 for the database to be reverted to 2016

it was working fine and never almost unbreakable. All works and hardly i see any wifi clients disconnected net issues.

But when the moment i update the database the router all started acting wiered. I did reseted to full 30/30/30 but no luck the qos is broken again easily

I have to again go back to old firmware and then back to 2.28 and disable the auto update feature.
Click to expand...
Mine updated fine on its own, and QoS seems to be doing its thing happily. Sometimes I have had issues where the database didn't update straight away after a firmware update but it would after a while (30/30/30 I think is unneeded personally) Netgear on the forums recommended with the r7000 to hold the reset button for I believe twenty seconds, that's all. and that seems fine on the R7800 too.
I tried a 30/30/30 and that caused issues with DHCP requests in the router logs no showing up, a normal 20 second hard reset and I had no issues whatsoever after. This may be a quirk of 1.0.2.28 or maybe the firmware just does not need such a complicated reset tbh and that it actually causes more harm than good. I have not seen anyone else yet with this issue with the new database but that's not to say it does not exist. When you say "started acting all weird" what do you mean? :)
 
original
original
original
original


i mean the QOS is getting broken i see -ve traffic and no live bandwidth monitoring on the attached devices as well the priorities are getting reset to low for all wired and wireless and at times the wireless clients getting disconnected from Internet and Local Intranet for streaming and other web activities.

All a mess overall. But Internet works ok for Wired devices but the traffic seems to not using the full bandwidth even though i dont have much activity of internet usage it should give full bandwidth to download but instead it only gives 20-40% of the bandwidth and never goes up even when all the wireless clients are disconnected.
 
You must log in or register to reply here.

Similar threads

Voxel
Voxel Custom firmware build for R7800 v. 1.0.2.107SF
Replies
10
Views
748
HELLO_wORLD
HELLO_wORLD
Voxel
Voxel Custom firmware build for R7800 v. 1.0.2.106SF
2
Replies
26
Views
3K
spocko
S
Voxel
Voxel Custom firmware build for R9000/R8900 v. 1.0.4.73HF
Replies
3
Views
271
Kitsap
K
Voxel
Voxel Custom firmware build for Orbi LBR20 v. 9.2.5.2.42SF-HW
Replies
2
Views
508
nordicboy
N
Voxel
Voxel Custom firmware build for Orbi LBR20 v. 9.2.5.2.43SF-HW
Replies
1
Views
226
Lbrfan
L
Similar threads
Thread starter Title Forum Replies Date
Voxel Voxel Custom firmware build for Orbi LBR20 v. 9.2.5.2.43SF-HW NETGEAR AC Wireless (Wi-Fi 5) 1
Voxel Voxel Custom firmware build for Orbi RBK50/RBK53 (RBR50, RBS50) v. 9.2.5.2.33SF-HW NETGEAR AC Wireless (Wi-Fi 5) 6
Voxel Voxel Custom firmware build for R9000/R8900 v. 1.0.4.73HF NETGEAR AC Wireless (Wi-Fi 5) 3
Voxel Voxel Custom firmware build for R7800 v. 1.0.2.107SF NETGEAR AC Wireless (Wi-Fi 5) 10
Voxel Voxel Custom firmware build for Orbi LBR20 v. 9.2.5.2.42SF-HW NETGEAR AC Wireless (Wi-Fi 5) 2
Voxel Voxel Custom firmware build for Orbi RBK50/RBK53 (RBR50, RBS50) v. 9.2.5.2.32SF-HW NETGEAR AC Wireless (Wi-Fi 5) 12
Voxel Voxel Custom firmware build for R9000/R8900 v. 1.0.4.72HF NETGEAR AC Wireless (Wi-Fi 5) 13
Voxel Voxel Custom firmware build for R7800 v. 1.0.2.106SF NETGEAR AC Wireless (Wi-Fi 5) 26
Voxel Voxel Custom firmware build for Orbi LBR20 v. 9.2.5.2.41SF-HW NETGEAR AC Wireless (Wi-Fi 5) 2
Voxel Voxel Custom firmware build for Orbi RBK50/RBK53 (RBR50, RBS50) v. 9.2.5.2.31SF-HW NETGEAR AC Wireless (Wi-Fi 5) 18

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 794 (members: 24, guests: 770)
Top