Custom firmware build for R7800 v. 1.0.2.72SF

[ildiko]

thank you for your hard work, you are the best!!!

 

[tarassippo]

There seems to be an issue with STUBBY (DoT) using the provided config file. Has anyone been able to address this?

root@R7800:/tmp/log$ cat stubby.log
Tue Dec 17 17:25:54 GMT 2019
[23:25:54.735267] STUBBY: Read config from file /etc/stubby/stubby.yml
[23:26:07.515961] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:07.516180] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:07.516305] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:07.516617] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:10.017492] STUBBY: 2606:4700:4700::1111                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:12 2019
[23:26:11.267726] STUBBY: 2606:4700:4700::1001                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:13 2019
[23:26:11.299529] STUBBY: 1.1.1.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:13 2019
[23:26:11.326395] STUBBY: 2606:4700:4700::1111                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:11.326895] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.327270] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.327551] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.327832] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.328113] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.328363] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.328582] STUBBY: 1.0.0.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:13 2019
[23:26:13.829488] STUBBY: 2606:4700:4700::1001                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:15.137610] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.137767] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.137892] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.138204] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.138485] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.138766] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.139016] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.139297] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.139547] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:17.433549] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:17.433893] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:17.434174] STUBBY: 2606:4700:4700::1111                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:19 2019
[23:26:18.787501] STUBBY: 2606:4700:4700::1001                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:20 2019
[23:26:18.812462] STUBBY: 1.1.1.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 4s at Tue Dec 17 23:26:22 2019
[23:26:18.836392] STUBBY: 2606:4700:4700::1111                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:18.836861] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:18.837236] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:18.837486] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:18.837829] STUBBY: 1.0.0.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 4s at Tue Dec 17 23:26:22 2019
[23:26:20.636173] STUBBY: 2606:4700:4700::1001                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:20.636548] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.636892] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637204] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637329] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637454] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637704] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637954] STUBBY:    *FAILURE* no valid transports or upstreams available!
root@R7800:/tmp/log$

Voxel is aware of this issue and hopefully he will fix it soon. Meanwhile, use DNSCrypt...

 

[kamoj]

Solution until new Voxel release:
edit stubby.yml and change from:
tls_min_version: GETDNS_TLS1_3
to:
tls_min_version: GETDNS_TLS1_2
Example:

sed -i 's/ls_min_version: GETDNS_TLS1_3/ls_min_version: GETDNS_TLS1_2/g' /etc/stubby/stubby.yml

There seems to be an issue with STUBBY (DoT) using the provided config file. Has anyone been able to address this?

 

[Voxel]

PLEASE keep supporting the R7800.

He he, do not worry much. I have three R7800 and I use all of them. So I have to keep supporting

Voxel.

 

[Voxel]

Solution until new Voxel release:
edit stubby.yml and change from:
tls_max_version: GETDNS_TLS1_3
to:
tls_max_version: GETDNS_TLS1_2

More proper is to change tls_min_version to GETDNS_TLS1_2 leaving tls_max_version: GETDNS_TLS1_3

. . .
ls_min_version: GETDNS_TLS1_2
tls_max_version: GETDNS_TLS1_3
. . .

And more easy to wait my next release. I hope to release it soon.

Voxel.

 

[DRiP]

More proper is to change tls_min_version to GETDNS_TLS1_2 leaving tls_max_version: GETDNS_TLS1_3

. . .
ls_min_version: GETDNS_TLS1_2
tls_max_version: GETDNS_TLS1_3
. . .

And more easy to wait my next release. I hope to release it soon.

Voxel.

That works! Thanks.

 

[spocko]

New version 1.0.2.73SF is available:

https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-73sf.60710/

Thanks so much for all your work Voxel!

 

[Fly56]

There are changes 72SF vs 70SF of course but they do not touch network performance. Rather multimedia... No changes in QCA drivers etc. Maybe you should backup your settings, then factory reset and restore the settings from backup. Or to set-up them anew...

Voxel.

Just a quick update. I ended up waiting to do anything more because of the holidays and I went to put 74SF onto my router. I again had the problems with my android based phones from connecting to the internet when on the R7800 WIFI signal. I use 2 r7000s in a bridge mode to connect other computers and they continued to work. I backed up the settings, did a factory reset, and then restored. That did not fix the problem. Then I did a reset again and set up anew, and that worked.

I'm not sure what happened from 70SF to 72SF/74SF, but I'm back going.

Thanks for your work in doing these firmwares.

 

[microchip]

Just a quick update. I ended up waiting to do anything more because of the holidays and I went to put 74SF onto my router. I again had the problems with my android based phones from connecting to the internet when on the R7800 WIFI signal. I use 2 r7000s in a bridge mode to connect other computers and they continued to work. I backed up the settings, did a factory reset, and then restored. That did not fix the problem. Then I did a reset again and set up anew, and that worked.

I'm not sure what happened from 70SF to 72SF/74SF, but I'm back going.

Thanks for your work in doing these firmwares.

Rule of thumb when doing a reset: Most of the time you need to reconfigure from scratch. Using a backup file may be convenient but you are re-introducting the same values again that may have caused you issues, which in essence defeats the purpose of a factory reset. It can work sometimes but very often it doesn't and you end up in the same situation as before the reset. If it works with no issues, great. Otherwise a reconfigure from scratch is needed. Can be a bit of a pain but it shouldn't take more than 30-45 minutes to set things up again

 

[percy3]

You should format it using special option, it is written in my README

mkfs.ext4 -O ^metadata_csum /dev/sda1

It is for kernel version < 3.10 (3.4.103 in R7800).

Voxel.

I wasn't sure if I used option metadata_csum originally so I have reformatted the drive from within the router firmware.
Still not possible to mount it. Works fine with NTFS however.

 

[Azimul Kabir Apu]

I wasn't sure if I used option metadata_csum originally so I have reformatted the drive from within the router firmware.
Still not possible to mount it. Works fine with NTFS however.

Last night I formatted my SSD with following code:

df -h /tmp/mnt/OPU_SSD (my drive lebel)
[it was mounted as /dev/sdb1 on /tmp/mnt/sdb1]

umount /tmp/mnt/OPU_SSD

mkfs.ext4 -L ssd -O ^metadata_csum /dev/sdb1

mount /dev/sdb1 /tmp/mnt/ssd
[got error message like: mounting /dev/sdb1 on /tmp/mnt/ssd failed.]

I tried restarting my router but router can't mount the SSD. I can see the SSD drive from www.routerlogin.net > Advanced > Advance Settings > USB Settings

I know the workaround. If I reformat the drive from Windows 10 by MiniTools it will be automatically mounted in router again.
But I want to know why the drive is not mounting by Telnet Command? @Voxel Please Help. Thank you.

 

[microchip]

Silly question @Voxel but what does the SF and HF letters mean at the end of your custom version number?

 

[L&LD]

@microchip Super Firmware and Herculean Firmware!

 

[Voxel]

@microchip Super Firmware and Herculean Firmware!

Yeah, almost so

Silly question @Voxel but what does the SF and HF letters mean at the end of your custom version number?

https://www.snbforums.com/threads/c...r-r7800-v-1-0-2-54sf.47947/page-2#post-420833

Voxel.

 

[microchip]

Yeah, almost so



https://www.snbforums.com/threads/c...r-r7800-v-1-0-2-54sf.47947/page-2#post-420833

Voxel.

Thanks. That makes it clear

 

[poondoggle]

Hi All,

I am currently back on the latest stock R7800 firmware after running DD-WRT for a couple of years. I recently upgraded to gigabit internet and can’t seem to break 400Mbps on downloads despite averaging between 750-850Mbps on fast.com.

I have read that this may be due to hardware acceleration not being enabled on the router. I also read that it isn’t supported natively for my router using DD-WRT.

I have two questions.

Is there anyway to check if hardware acceleration is enabled using Voxel’s firmware, and the second is does it support setting custom DNSMasq settings?

Thanks in advance!

 

[ZetiX]

Hi All,

I am currently back on the latest stock R7800 firmware after running DD-WRT for a couple of years. I recently upgraded to gigabit internet and can’t seem to break 400Mbps on downloads despite averaging between 750-850Mbps on fast.com.

I have read that this may be due to hardware acceleration not being enabled on the router. I also read that it isn’t supported natively for my router using DD-WRT.

I have two questions.

Is there anyway to check if hardware acceleration is enabled using Voxel’s firmware, and the second is does it support setting custom DNSMasq settings?

Thanks in advance!

There's hardware acceleration on Voxel since it's based on stock, but with upgraded packages.

 

[poondoggle]

There's hardware acceleration on Voxel since it's based on stock, but with upgraded packages.

Does it show whether or not acceleration is active? Do you know if Voxel’s supports DNSMasq setting? I am using a Pi-Hole and need to point DNS requests there.

 

[ZetiX]

Does it show whether or not acceleration is active? Do you know if Voxel’s supports DNSMasq setting? I am using a Pi-Hole and need to point DNS requests there.

It doesn't tell you whether HW accel is on or not. But Voxel stated that his firmware is based on the stock firmware, there should be a post somewhere in this forum.

As for Pi-Hole configuration, just go to the Internet tab on the stock firmware's web page and under DNS Address, use custom and input Pi-Hole's IP address.

 

[kamoj]

If these commands shows 0, NSS is active:

cat /sys/kernel/debug/ecm/ecm_nss_ipv4/stop
cat /sys/kernel/debug/ecm/ecm_nss_ipv6/stop

Does it show whether or not acceleration is active? Do you know if Voxel’s supports DNSMasq setting? I am using a Pi-Hole and need to point DNS requests there.