Custom firmware build for R7800 v. 1.0.2.50SF

[Voxel]

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/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-30sf.38366/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-31sf.39142/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-32sf.39657/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-33sf.40198/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-34sf.40523/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-35sf.40794/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-36sf.41166/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-37sf.41317/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-38sf.41751/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-39sf.41945/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-40sf-1-0-2-41sf.42222/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-43sf.42683/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-44sf.42882/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-45sf.43853/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-47sf.44781/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-49sf.45296/

New version of my custom firmware build: 1.0.2.50SF.

Changes (vs 1.0.2.49SF):

1. OpenVPN client additional speed up (thanks to kamoj for his help).
2. WebGUI: syncronization of lang version with stock 1.0.2.46.
3. OpenSSL is upgraded 1.0.2n->1.0.2o.
4. curl package is upgraded 7.58.0->7.59.0.
5. ffmpeg package is upgraded 3.2.9->3.2.10.
6. libubox package is upgraded 2018-02-08->2018-03-21.
7. uci package is upgraded 2018-01-01->2018-03-24.
8. ncurses package is upgraded 6.0->6.1.
9. util-linux package is upgraded 2.31.1-2.32.
10. Toolchain: binutils version is upgraded to 2.30

The link is:

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

NOTE: Most probably no reset is needed to upgrade from my previous versions. But if you face problems it is better to perform reset.

Voxel.

 

[e38BimmerFN]

Any idea if AP mode feature is fixed in this?

Update, just tested. Setting a Static IP address still causes the router to become masked and not accessible with the assigned IP address given. However using a Dynamic IP address works. I can get an IP address from the main host router and connect to R7800s web page. Wireless Bridge mode is working fine.

Something is still broke with AP mode and Static IP address.

 

[Voxel]

Any idea if AP mode feature is fixed in this?

Update, just tested. Setting a Static IP address still causes the router to become masked and not accessible with the assigned IP address given. However using a Dynamic IP address works. I can get an IP address from the main host router and connect to R7800s web page. Wireless Bridge mode is working fine.

Something is still broke with AP mode and Static IP address.

Something should be left as "to-do" for NG developers

Voxel.

 

[e38BimmerFN]

Hope they will.

 

[RogerSC]

Doing well here, thanks Voxel!

 

[AntonK]

Firmware works like a charm for my network. Thank you!

 

[ulaganath]

Yes for now the QOS is live and active.

I face another issue recently. This may not be with the firmware may be with other router ie ea7500 in bridge DHCP mode

I am finding difficult to hit router through local ip. It only works when i connect to the router directly via wireless .

Previously also i have this setup . Not sure what changed

 

[e38BimmerFN]

Try resetting the 7500 then set back up in bridge mode and see.

I presume this is wireless bridge?

Yes for now the QOS is live and active.

I face another issue recently. This may not be with the firmware may be with other router ie ea7500 in bridge DHCP mode

I am finding difficult to hit router through local ip. It only works when i connect to the router directly via wireless .

Previously also i have this setup . Not sure what changed

 

[ulaganath]

No I set it up as DHCP. Setting as bridge will extend the network which i dont want. I wanted two different network.

Main router is R7800 connected to Internet.
2nd one is Ea7500 which is connecting my PC and NAS along with other clients.


I remember setting a static router but now it got reset on both router leading to not access the nighthawk. I totally lost on that.

 

[e38BimmerFN]

Then set up the EA7500 as a 2ndary router with a different IP address, 192.168.2.1. You can use the R7800's DMZ for the R7500 router if you want. Or set up the EA7500 as a LAN to LAP AP. Disable all DHCP on the EA router and just use it's wireless. Connect it via LAN to LAN with the R7800. Set the EA7500s IP address to 192.168.1.75.

 

[ulaganath]

I dont want to expose the ea7500 to outside local network. yes both the routers are wired but i connected to wan port of the ea7500 so that it is not an extended lan.

I believe some static routing is required. But i missed it. let me figure out

 

[e38BimmerFN]

Let us know how it turns out.

 

[gobble]

Probably a daft question... I could do with running iperf/iperf3 directly from my router to test some stuff. Can I simply telnet in and install (sudo apt-get install type thing) and run this?

 

[Voxel]

Probably a daft question... I could do with running iperf/iperf3 directly from my router to test some stuff. Can I simply telnet in and install (sudo apt-get install type thing) and run this?

You can play with Entware. Telnet login is enough. After installation just

/opt/bin/opkg install iperf3

It is installed to my router and I use it for testing.

Voxel.

 

[ulaganath]

Hi Voxel,

it seems the QOS again is not even loading . I dont see + sign and all the devices were in low priority

I recently changed from 100Mbps to 150Mbps line the Speed test reports 180mbps .

I know for this high speed its hard for qos/

But still almost 9-14 devices will be crunching for bandwidth atleast streaming devices needs to get highest priority. Which i believe this router chews it . Unfortunately i dont why the qos didnt works any more. I tried even re-installing the firmware twice.

Does reset is the only option here.

 

[e38BimmerFN]

Try a full factory reset then don't enable QoS or use the speed test on the QoS UI. Just leave it alone and see if anything different happens.

Hi Voxel,

it seems the QOS again is not even loading . I dont see + sign and all the devices were in low priority

I recently changed from 100Mbps to 150Mbps line the Speed test reports 180mbps .

I know for this high speed its hard for qos/

But still almost 9-14 devices will be crunching for bandwidth atleast streaming devices needs to get highest priority. Which i believe this router chews it . Unfortunately i dont why the qos didnt works any more. I tried even re-installing the firmware twice.

Does reset is the only option here.

 

[ulaganath]

Let us know how it turns out.

Now things are back to normal. My pc was set static ip with wrong subnet once set to automatic it was all working .

 

[e38BimmerFN]

Glad it was a simple fix.

Enjoy.

 

[Gouzmalix]

After checking Voxel's github page for his R7800 build, I noticed he changed Traffic Meter's max numerical value from 6 digits to 9. Unfortunately, it would appear that the Traffic Meter binary itself—or something else—is responsible for accepting the values; anything greater than 999999 results in an error dialog of "Invalid numeric value for Monthly limit".

 

[avtella]

After checking Voxel's github page for his R7800 build, I noticed he changed Traffic Meter's max numerical value from 6 digits to 9. Unfortunately, it would appear that the Traffic Meter binary itself—or something else—is responsible for accepting the values; anything greater than 999999 results in an error dialog of "Invalid numeric value for Monthly limit".

All we can do is pester Netgear for these old issues, I filed a report and did Team Viewer with a Lvl2 tech for the blank page issue in Attached Devices and the IPV6 filtering issue a month back.