Voxel Custom firmware build for R7800 v. 1.0.2.91SF & v. 1.0.2.91.1SF

[Remy561]

Thread is updated.

Voxel.

Those are quite a number of security fixes! Updated again!

 

[LeKeiser]

Firmware updated and everything is working so well, as always
Thanx Mr Voxel!! Again and Again

 

[IAMP373R]

Thanks for fixing vulnerabilities so quickly, thank you Voxel.

Just post another meme

 

[kokishin]

Hi @Voxel from Loonyfornia,

First of all, Thanks!

An observation:
I use Cloudflare DNS servers 1.1.1.1. and 1.0.0.1. Whenever I install your most current firmware update, this info is retained in my 7800. After I installed 90.1.1SF, the DNS Server assignment changed to "Get Automatically from ISP". "Use These DNS Servers Primary DNS" had the google DNS Server 8.8.8.8. gray shaded since it wasn't selected. I changed the DNS Server assignment back to Cloudflare. I checked other config settings in the router and they were all retained. Perhaps just a one-time idiosyncrasy with my 7800.

Again, thanks.

 

[kokishin]

@Voxel

Just sent you a modest donation to show my appreciation for the work you do on your excellent firmware updates.

All the best in 2022!

 

[Voxel]

Just post another meme

Please continue your art.

Voxel.

 

[Voxel]

Wish I could drink a Perrier with you

Well, I'm wishing too . Maybe.

P.S.
France... Well... Maybe Perrier --> Bordeaux or Cognac? Non, rien de rien, non, je ne regrette rien...

Voxel.

 

[Carolus]

First of all, Thanks!,
Updating my AP's from 86

Never seen a more stable router like this one!! Thanks for all Voxel
I sent you a donation!
Gr, Carolus

 

[microchip]

Hey,

dnscrypt2 starts too early. This causes a problem with IPv6 that may be populated after dnscrypt2 starts. In that case, you won't have a working IPv6 and have to restart dnscrypt2 manually. I suggest changing the default START=70 to START=99

 

[NetBytes]

Just updated both my R7800 ap from .89.
Smooth as glass upgrade and everything working as expected.
Thanks again Voxel.

 

[hipek_pl]

Hello and first of all, thank you for a great job on this firmware...

I'm not sure if this is related to latest firmware or maybe some previous versions but VPN service messages are not available in the Log section even when "VPN Service" is marked...

I have discovered this today when I wanted to verify why I have received different IP over VPN than usual...

 

[brisk5181]

Thanks Voxel!

Anyone experienced wired or wireless goes off randomly? I am running one R7800 as main router, one R7800 and one AUSU RT-AC86U as AP. The main router wired and wireless connection randomly goes off, have to reboot the main router a couple times a day.

Thanks

 

[Sizzlechest]

Thanks Voxel!

Anyone experienced wired or wireless goes off randomly? I am running one R7800 as main router, one R7800 and one AUSU RT-AC86U as AP. The main router wired and wireless connection randomly goes off, have to reboot the main router a couple times a day.

Thanks

No. A full reset might be in order.

 

[hipek_pl]

Thanks Voxel!

Anyone experienced wired or wireless goes off randomly? I am running one R7800 as main router, one R7800 and one AUSU RT-AC86U as AP. The main router wired and wireless connection randomly goes off, have to reboot the main router a couple times a day.

Thanks

Hi

I have experienced the same when I upgraded from .89SF -> .90SF that 2Ghz were disconnecting randomly but 5Ghz and wired were working fine in my case.
Unfortunately settings restore and than factory reset did not solved problem. Problem gone after moving to original firmware, reset, move to Voxel firmware and setup everything manually (not from settings restore)...

 

[hipek_pl]

Does anyone using latest Voxel firmware with VLAN enabled on R7800?

I was trying to enable VLAN on my R7800 with 91.1SF + Kamoj 5.5b18 and end up with disconnected Internet.
Setup wizard / problem detection / ISP DHCP release / renew is not working and I found the following error in the logs:



device brwan entered promiscuous mode
device brwan left promiscuous mode
NET: Unregistered protocol family 24
brwan: port 1(ethwan) entered disabled state
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
DNI-QOS: Qos is disable
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
DNI-QOS: Qos is enable
device eth0 entered promiscuous mode
brwan: port 1(ethwan) entered forwarding state
brwan: port 1(ethwan) entered forwarding state
brwan: no IPv6 routers present
ethwan: no IPv6 routers present
device brwan entered promiscuous mode
msm_nand_read_oob 57f0800 800 0 failed -74, corrected 0
msm_nand_read_oob 57f0800 800 0 failed -74, corrected 0
msm_nand_read_oob 57f0800 800 0 failed -74, corrected 0
msm_nand_read_oob 57f0800 800 0 failed -74, corrected 0
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:67584, read 64 bytes
msm_nand_read_oob 57f1000 800 0 failed -74, corrected 0
msm_nand_read_oob 57f1000 800 0 failed -74, corrected 0
msm_nand_read_oob 57f1000 800 0 failed -74, corrected 0
msm_nand_read_oob 57f1000 800 0 failed -74, corrected 0
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:69632, read 64 bytes
msm_nand_read_oob 57f1800 800 0 failed -74, corrected 0
msm_nand_read_oob 57f1800 800 0 failed -74, corrected 0
msm_nand_read_oob 57f1800 800 0 failed -74, corrected 0
msm_nand_read_oob 57f1800 800 0 failed -74, corrected 0
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:71680, read 64 bytes
msm_nand_read_oob 57f2000 800 0 failed -74, corrected 0
msm_nand_read_oob 57f2000 800 0 failed -74, corrected 0
msm_nand_read_oob 57f2000 800 0 failed -74, corrected 0
msm_nand_read_oob 57f2000 800 0 failed -74, corrected 0
...
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:122880, read 64 bytes
msm_nand_read_oob 57fe800 800 0 failed -74, corrected 0
msm_nand_read_oob 57fe800 800 0 failed -74, corrected 0
msm_nand_read_oob 57fe800 800 0 failed -74, corrected 0
msm_nand_read_oob 57fe800 800 0 failed -74, corrected 0
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:124928, read 64 bytes
msm_nand_read_oob 57ff000 800 0 failed -74, corrected 0
msm_nand_read_oob 57ff000 800 0 failed -74, corrected 0
msm_nand_read_oob 57ff000 800 0 failed -74, corrected 0
msm_nand_read_oob 57ff000 800 0 failed -74, corrected 0
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:126976, read 64 bytes
msm_nand_read_oob 57ff800 800 0 failed -74, corrected 0
msm_nand_read_oob 57ff800 800 0 failed -74, corrected 0
msm_nand_read_oob 57ff800 800 0 failed -74, corrected 0
msm_nand_read_oob 57ff800 800 0 failed -74, corrected 0
UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 283:129024, read 64 bytes
device brwan left promiscuous mode
brwan: port 1(ethwan) entered disabled state
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
DNI-QOS: Qos is disable
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
DNI-QOS: Qos is enable
device eth0 entered promiscuous mode
brwan: port 1(ethwan) entered forwarding state
brwan: port 1(ethwan) entered forwarding state
brwan: no IPv6 routers present
ethwan: no IPv6 routers present


everything back to normal when I disable VLAN... and no such errors in the log occuring anymore...

I have also tested on fresh factory reset Voxel firmware and the same errors occuring so not related to Kamoj add-on nor Aegis etc...
Not tested with vendor original firmware as as it's not sable in 90+ versions as per my expirance...

 

[DRiP]

Voxel, 1st - thanks for the great firmware for the R7800. I have been using your updates several years now and greatly appreciate your work.

I have a question about a minor configuration issue I have stumbled on. This maybe something inherently Netgear related but hoping you might be able to shed some light on it or possibly address.

I run my router with “Respond to Ping on Internet Port” disabled as default. When ever I enable the OpenVPN service, the “Respond to Ping on Internet Port” gets re-enabled for some reason.

I realize that I can just go and disable “Respond to Ping on Internet Port” again, now that know this is happening, but is there a possible fix for this?

Thanks!

 

[hipek_pl]

Voxel, 1st - thanks for the great firmware for the R7800. I have been using your updates several years now and greatly appreciate your work.

I have a question about a minor configuration issue I have stumbled on. This maybe something inherently Netgear related but hoping you might be able to shed some light on it or possibly address.

I run my router with “Respond to Ping on Internet Port” disabled as default. When ever I enable the OpenVPN service, the “Respond to Ping on Internet Port” gets re-enabled for some reason.

I realize that I can just go and disable “Respond to Ping on Internet Port” again, now that know this is happening, but is there a possible fix for this?

Thanks!

In original vendor firmware this option is enabled and grayed out once VPN enabled. This is setup that way to keep VPN connection alive as per Netgear support response...

This was the main reason I have moved to custom firmware (DDWRT) but it had no SmartConnect option so found Voxel firmware and staying with this firmware from years as fits to all my needs...

 

[DRiP]

In original vendor firmware this option is enabled and grayed out once VPN enabled. This is setup that way to keep VPN connection alive as per Netgear support response...

This was the main reason I have moved to custom firmware (DDWRT) but it had no SmartConnect option so found Voxel firmware and staying with this firmware from years as fits to all my needs...

I do not see any problem with OpenVPN service stability when the wan ping is disabled. Not sure why it needs to be re-enabled when the OpenVPN service is enabled.

 

[hipek_pl]

I do not see any problem with OpenVPN service stability when the wan ping is disabled. Not sure why it needs to be re-enabled when the OpenVPN service is enabled.

This is not related to stability but keep alive the connection. On original firmware when this option was enabled and VPN on my phone was connected it remain connected until I have manually disconnected from the VPN (24h+). When this option is disabled on Voxel firmware you will get disconnected after few hours of inactivity as OpenVPN client software is unable to get response from OpenVPN server on your router.

 

[Voxel]

I run my router with “Respond to Ping on Internet Port” disabled as default. When ever I enable the OpenVPN service, the “Respond to Ping on Internet Port” gets re-enabled for some reason.

I realize that I can just go and disable “Respond to Ping on Internet Port” again, now that know this is happening, but is there a possible fix for this?

This stuff (enabling respond to ping) is inside of the pre-built binary 'net-cgi' from the GPL by NG/DNI. So sorry, I cannot change its behavior. But do you really change OpenVPN ON/OFF too often? I just do enable it with disabling 'respond to ping' and forget it almost forever...

Voxel.