Custom firmware build for R9000/R8900 v. 1.0.3.12HF/1.0.3.12HF-HW

[Voxel]

Continuation of:

https://www.snbforums.com/threads/custom-firmware-build-for-r9000.40125/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-41hf-1-0-2-41hf-hw.40481/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-42hf-1-0-2-42hf-hw.40688/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-43hf-1-0-2-43hf-hw.41167/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-44hf-1-0-2-44hf-hw.41301/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-45hf-1-0-2-45hf-hw.41820/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-46hf-1-0-2-46hf-hw.42223/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-47hf-1-0-2-47hf-hw.42721/
hhttps://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-54hf-1-0-2-54hf-hw-1-0-3-7hf-1-0-3-7hf-hw.43854/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-3-8hf-1-0-3-8hf-hw.44204/
https://www.snbforums.com/threads/c...r9000-r8900-v-1-0-3-11hf-1-0-3-11hf-hw.45070/

New version of my custom firmware build: 1.0.3.12HF/1.0.3.12HF-HW.

Changes (vs 1.0.3.11HF):

1. Some yet another minor NG bugs are corrected.
2. OpenSSL is upgraded 1.0.2n->1.0.2o.
3. curl package is upgraded 7.58.0->7.59.0.
4. ffmpeg package is upgraded 3.2.9->3.2.10.
5. libubox package is upgraded 2018-02-08->2018-03-21.
6. uci package is upgraded 2018-01-01->2018-03-24.
7. ncurses package is upgraded 6.0->6.1.
8. util-linux package is upgraded 2.31.1-2.32.
9. libxml2 package is upgraded 2.9.7->2.9.8.
10. iperf3 package is upgraded 3.4->3.5.
11. Host tools: three components are upgraded.
12. Toolchain: binutils version is upgraded to 2.30

The link is:

https://www.voxel-firmware.com (thanks to vladlenas for his help with hosting).

No reset to factory is needed after flasing from 1.0.3.11HF/1.0.3.11HF-HW.

Difference 1.0.3.12HF-HW vs 1.0.3.12HF: “HW” version means hardware acceleration of OpenSSL.

P.S. It is recommended to disable Router Auto Firmware Update. Otherwise your router might be upgraded suddenly by stock version.

Voxel.

 

[D3FenD3r]

I have R9000-V1.0.3.12HF-HW on netgear r9000
I removed the provider's router and put a mediaconverter fiber Gpon
the provider releases the ip via dhcp.
via dhcpc option -v(vendor class) by hand works,
with an 8-hour lease, then it falls.

---> udhcpc -i brwan -V "askey_HW_ES1_SW_0.00.67 / dslforum.org"

where can I insert it starting alone and renew the lease?

ciao mario

 

[tech960]

This might be on my side, but I have having a hard time getting to my USB 16TB drive. The 4TB is working just fine. I can see it connecting in logs, etc.

This build and the last it's been doing this. I have some long cables on order so I can do some testing on this end.

[USB device attached] The USB storage device WD My Book Duo 0A10(16 is attached to the router, Thursday, April 05, 2018 17:27:40

Thanks for the new build Voxel, much appreciated! This router still sits atop my GT5300 as king.

 

[tech960]

I noticed it shows the drive connected on GUI Media Server / Plex:

USB Device for Plex Data Directory

Multiple USBs Available Change Current USB Device
Current USB Device: USB2 , My Book Duo 0A10 , Total space: M , Free space: 16 TB USB RAID

But it doesn't list on the display under Readyshare/Advanced.. if that helps.

 

[Ethan Garner]

Thank you so much for making these (much) superior builds for the R9000.
Without them, this router would be useless!

So please keep on them, and I'd be happy to contribute to keep the development going!

 

[Voxel]

I have R9000-V1.0.3.12HF-HW on netgear r9000
I removed the provider's router and put a mediaconverter fiber Gpon
the provider releases the ip via dhcp.
via dhcpc option -v(vendor class) by hand works,
with an 8-hour lease, then it falls.

---> udhcpc -i brwan -V "askey_HW_ES1_SW_0.00.67 / dslforum.org"

where can I insert it starting alone and renew the lease?

ciao mario

Sorry I did not quite understand you. Could you point your instruction on your ISP?

Voxel.

 

[Voxel]

This might be on my side, but I have having a hard time getting to my USB 16TB drive. The 4TB is working just fine. I can see it connecting in logs, etc.

I am not sure. There could be somewhere limitation on the size of USB HDD. I met some issues alarmed by NG routers owners... I'll check.

Voxel.

 

[Voxel]

Thank you so much for making these (much) superior builds for the R9000.
Without them, this router would be useless!

So please keep on them, and I'd be happy to contribute to keep the development going!

Voxel.

 

[tech960]

I am not sure. There could be somewhere limitation on the size of USB HDD. I met some issues alarmed by NG routers owners... I'll check.

Voxel.

Keep in mind it worked perfectly on older builds and stock builds.

 

[Voxel]

Keep in mind it worked perfectly on older builds and stock builds.

There should not be changes 11HF(-HW) vs 12HF(-HW) what could influence to USB attached to router. Neither kernel level nor samba etc. So maybe reset to factory settings is needed, if you played with stock<->my build. Reset is a must when changing stock->my build.

Voxel.

 

[Dodge DeBoulet]

There should not be changes 11HF(-HW) vs 12HF(-HW) what could influence to USB attached to router. Neither kernel level nor samba etc. So maybe reset to factory settings is needed, if you played with stock<->my build. Reset is a must when changing stock->my build.

Voxel.

Hi Voxel,

If a reset really is required when upgrading from stock to your build, I would respectfully suggest that you update your initial R9000 announcement post. It clearly states that "It could be flashed from WebGUI of your stock firmware and all your settings should be kept."

I assumed that I did not need to reset to factory settings with my recent update to your latest version from an earlier NetGear release, and so far I've experienced no issues. But now I'm worried

Thank you so much for these builds!

 

[Voxel]

If a reset really is required when upgrading from stock to your build, I would respectfully suggest that you update your initial R9000 announcement post. It clearly states that "It could be flashed from WebGUI of your stock firmware and all your settings should be kept."

Well, I assume that people should read concrete post for concrete version of my firmware. Reset was not needed for very first release and several next versions. But later (December or January) NG changed their stock version upgrading drivers and as it was reported in their release notes, it required reset. Changes in nand ram layout.

I assumed that I did not need to reset to factory settings with my recent update to your latest version from an earlier NetGear release, and so far I've experienced no issues. But now I'm worried

Most probably everything is working except AD band . BTW, you can do reset right now, using my version. This should recover AD if it is not working for you now.

If everything is OK including AD, just use it. It depends on what version of stock you had before flashing my build. As far as I remember if 1.0.3.06/1.0.3.10 then reset. Flashing my build and reset.

Thank you so much for these builds!

Voxel.

 

[Dodge DeBoulet]

Well, I assume that people should read concrete post for concrete version of my firmware. Reset was not needed for very first release and several next versions. But later (December or January) NG changed their stock version upgrading drivers and as it was reported in their release notes, it required reset. Changes in nand ram layout.

Voxel, please don't take my request as a criticism; you're doing us R9000 owners a tremendous service by providing these firmware releases. I simply thought that including instructions to restore factory settings when coming from stock would eliminate some of the problems and resulting support requests that you get from clueless folks like me

I did read all of the posts in this thread, and the first time I saw an indication to reset to factory defaults when coming from the stock firmware was the post to which I replied previously. There was a mention of not needing to reset when coming from the previous Voxel-enhanced version, but nothing specific regarding the factory firmware.

Most probably everything is working except AD band . BTW, you can do reset right now, using my version. This should recover AD if it is not working for you now.

Thanks. I have some DHCP reservations, port forwards and other configuration values that I will need to re-enter, unless a configuration backup/restore will work. One of the reasons I was excited to find your firmware build is that it looked like it was a fairly painless install. Given your improvements, I will happily admit that some pain is acceptable

If everything is OK including AD, just use it. It depends on what version of stock you had before flashing my build. As far as I remember if 1.0.3.06/1.0.3.10 then reset. Flashing my build and reset.

I was previously running NetGear's 1.0.3.10 release, and I have the AD/60GHz radio disabled since I have nothing that will communicate with it. Regardless, it sounds like a reset to factory defaults is in order and I will do that as soon as I can get my father-in-law to stop watching Netflix long enough to reconfigure

 

[tech960]

Ok I Flashed the HW build this time. Before I was trying the other build for the first time.

After a reset, (I reset after the other build as well though) I think I figured out the issue, I think. For some odd reason, the router wants to name the Drive USB_Storage. It runs into some sort of conflict when it tries to use that name for both drives. As of now I can see my 16TB just fine. So it's either 1 drive or the other at the same time. I will plug the smaller drive into the back of the 16TB raid-0 drive, as it has 2 usb 3.0 slots in the rear and see if the router sees it. When both were connected a few builds ago it named the 2nd drive T_Drive.

 

[tech960]

There should not be changes 11HF(-HW) vs 12HF(-HW) what could influence to USB attached to router. Neither kernel level nor samba etc. So maybe reset to factory settings is needed, if you played with stock<->my build. Reset is a must when changing stock->my build.

Voxel.

It last worked under 09 build. 11 and 12 were the same,both trying to mount it as the same drive name, I'm guessing. Maybe the bug is in the stock firmware as well I will test.

 

[Voxel]

It last worked under 09 build. 11 and 12 were the same,both trying to mount it as the same drive name, I'm guessing. Maybe the bug is in the stock firmware as well I will test

OK, please share your testing results.

Voxel.