Custom firmware build for R9000/R8900 v. 1.0.4.41HF

[Voxel]

Continuation of:

https://www.snbforums.com/threads/custom-firmware-build-for-r9000.40125/
. . .
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-r8900-v-1-0-4-39-1hf.62968/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-r8900-v-1-0-4-40hf.63602/

New version of my custom firmware build: 1.0.4.41HF.

Changes (vs 1.0.4.40HF):

1. net-wall script is fixed for ppp0 connection and modifyed to provide more safety (OpenVPN/WireGuard client, thanks to R. Gerrits).
2. OpenVPN: vpn-firewall.sh script is fixed (thanks to R. Gerrits).
3. DNSCrypt Proxy v.2 init script is fixed (time synchronization, thanks to kamoj).
4. ipset package is upgraded 7.4->7.6+ [2020-03-09].
5. iptables package is upgraded 1.4.21->1.8.4.
6. wireguard package is upgraded 1.0.20200413->1.0.20200520.
7. wireguard-tools package is upgraded 1.0.20200319->1.0.20200513.
8. curl package is upgraded 7.69.1->7.70.0.
9. dbus package is upgraded 1.12.12->1.13.12.
10. libubox package is upgraded 2020-02-27->2020-05-25.
11. uci package is upgraded 2020-01-27->2020-04-24.
12. unbound package (used in stubby) is upgraded 1.9.6->1.10.1.
13. yaml package (used in stubby) is upgraded 0.2.2->0.2.4.
14. util-linux package is upgraded 2.35.1->2.35.2.
15. sqlite package is upgraded 3310100->3320100.
16. nano package is upgraded 4.9.2->4.9.3.
17. Toolchain: Go is upgraded 1.14.1->1.14.3.

The link is:

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

Voxel.

 

[KW.]

Oh yes! I was waiting didn't dare to ask when it was coming but was a bit jealous on the R7800 users in almost 24 hours. Thank you so much for this!

 

[kamoj]

Wow @Voxel, your releases are really leading edge and up to date!

Can we have updates of Wireguard for the R7800 as well?

 

[Voxel]

Can we have updates of Wireguard for the R7800 as well?

But I have on the site the most up-to-date version of wireguard-go:

https://git.zx2c4.com/wireguard-go

i.e. 2020-03-20...

https://voxel-firmware.com/Download...Guard/wireguard-go_0.0.20200320-1_ipq806x.ipk

wireguard-go is updated rather rarely...

Voxel.

 

[nsx]

awesome! thank you very much!!

 

[Toni]

Thanks for this new release Voxel!

I see a new message repeating every few seconds on my log since the update to 1.4.41:

May 27 21:48:32 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:32 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:48:41 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:41 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:48:50 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:50 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:48:59 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:59 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:49:08 R9000 sysinit: killall: nslookup: no process killed
May 27 21:49:08 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:49:17 R9000 sysinit: killall: nslookup: no process killed
May 27 21:49:17 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:49:26 R9000 sysinit: killall: nslookup: no process killed

Do you know whats causing it?

 

[pepperoni]

Just installed 1.0.4.41HF, Thank you for your time and knowledge on this firmware !

 

[lateparty]

Hey Voxel,

Thanks again for another great update. Update donation provided as usual

Additionally, I was curious to know, at one point between firmware updates, using the Netgear Guest network in isolation mode ignored the dnsmasq entry for "domain" and now it doesn't seem to - or at least it behaved like it did.

The problem I'm facing is, some URLs from my Cloudflare DNS point to my DDNS with a cname so I can access them externally, but, internally using the hosts file on the router, I point them to the LAN IP address. In older version of the firmware this worked perfectly, however now when I'm on the guest network, the device resolves to the internal IP which naturally cannot be reached, despite there being an equivalent upstream name resolution, that it no longer reaches.

Are you aware of any change that may have caused this, or what is leading to this behaviour?

 

[Voxel]

Hey Voxel,

Thanks again for another great update. Update donation provided as usual

Additionally, I was curious to know, at one point between firmware updates, using the Netgear Guest network in isolation mode ignored the dnsmasq entry for "domain" and now it doesn't seem to - or at least it behaved like it did.

The problem I'm facing is, some URLs from my Cloudflare DNS point to my DDNS with a cname so I can access them externally, but, internally using the hosts file on the router, I point them to the LAN IP address. In older version of the firmware this worked perfectly, however now when I'm on the guest network, the device resolves to the internal IP which naturally cannot be reached, despite there being an equivalent upstream name resolution, that it no longer reaches.

Are you aware of any change that may have caused this, or what is leading to this behaviour?

Well, thanks for report. I'll check this. To say true I never used guest network . So special testing is needed.

Do you use some specific DNS processing like DNSCtypt or stubby? Or just ordinary DNS set in GUI?

Voxel.

 

[lateparty]

Well, thanks for report. I'll check this. To say true I never used guest network . So special testing is needed.

Do you use some specific DNS processing like DNSCtypt or stubby? Or just ordinary DNS set in GUI?

Voxel.

Working from home and I don’t trust my employer enough to have a device with that kind of visibility

Thanks for checking it out, I am using dnscrypt 2 (via port 64153)

 

[Voxel]

Thanks for this new release Voxel!

I see a new message repeating every few seconds on my log since the update to 1.4.41:

May 27 21:48:32 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:32 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:48:41 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:41 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:48:50 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:50 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:48:59 R9000 sysinit: killall: nslookup: no process killed
May 27 21:48:59 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:49:08 R9000 sysinit: killall: nslookup: no process killed
May 27 21:49:08 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:49:17 R9000 sysinit: killall: nslookup: no process killed
May 27 21:49:17 R9000 sysinit: ***(pot.c,main,379): command name is wrong!
May 27 21:49:26 R9000 sysinit: killall: nslookup: no process killed

Do you know whats causing it?

I am sorry: missed this.

I've checked. The command "killall nslookup" is called from the script netconn.sh, part of DNI 's "pot" package.

https://github.com/SVoxel/R9000/tree/master/package/pot

I did not touch it. So it should be the same. The message "R9000 sysinit: ***(pot.c,main,379): command name is wrong!" is from the same DNI package:

/************************************************
 * functions implemented in POT flash partition *
 *        Delta Networks Ltd. (R) 2012          *
 ************************************************/
. . .
int main(int argc, char *argv[])
{
    daemon(1, 1);
    if (strstr(argv[0], "ntpst") != NULL)
        return ntpst_func(argc, argv);
    else if (strstr(argv[0], "stamac") != NULL)
        return stamac_func(argc, argv);
    else if (strstr(argv[0], "potval") != NULL)
        return potval_func(argc, argv);
    else if (strstr(argv[0], "potd") != NULL)
        return pot_func(argc, argv);
    else
        dfp("command name is wrong!\n");
    return -1;
}
. . .

So seems one more bug from DNI (stock)... In general it should be ignored. I'll check this (next version).

Voxel.

 

[Stan Dragos Cristian]

Hello Voxel thanks for this release.

One question for r9000 owners: What speed do you guys get when transferring files from local PC to a USB attached drive on the router ?

For me, no matter what i try, the speed don't go over 40-50 MB/s.

I use Ubuntu on my PC and i tried:

• Transferring using Nautilus auto-mount, through gvfs both AFP and SMB protocols
• Mounting myself using:

  mount -t cifs //source /mount -o credentials=/home/mylocaluser/.smbcredentials,vers=2.0,uid=mylocaluser

• Transferring using Nautilus through custom mount,
• Transfer using rsync, cp and pv
• I upgraded the SMB daemon. The default preinstalled smbd is Version 3.6.25, i installed samba4 through Voxel entware (Version 4.11.6) and changed the local mounting option to 'vers=3.0'

no luck, still locked to 40+ MB/s

any ideas what else should i try ?

 

[lateparty]

Hello Voxel thanks for this release.

One question for r9000 owners: What speed do you guys get when transferring files from local PC to a USB attached drive on the router ?

For me, no matter what i try, the speed don't go over 40-50 MB/s.

I use Ubuntu on my PC and i tried:

• Transferring using Nautilus auto-mount, through gvfs both AFP and SMB protocols
• Mounting myself using:
• Transferring using Nautilus through custom mount,
• Transfer using rsync, cp and pv
• I upgraded the SMB daemon. The default preinstalled smbd is Version 3.6.25, i installed samba4 through Voxel entware (Version 4.11.6) and changed the local mounting option to 'vers=3.0'

no luck, still locked to 40+ MB/s

any ideas what else should i try ?

I did some investigation into OpenWRT write speeds because I use a Linksys EA8500 as an extension AP and as an Rsync backup target, and there is some extensive work done over on their forums with the conclusion basically being the processors in there aren’t optimised for fast file writes.

There is a good test they had with just doing a dd write command with specified block size that demonstrate it’s a limitation of the CPU rather than drive, file system, protocol or network. Sorry that I don’t have the time right now to help address your question exactly but this should be enough to get you browsing and find those resources.

 

[Voxel]

For me, no matter what i try, the speed don't go over 40-50 MB/s.

Transfer from laptop with Windows 10 to USB drive attached to R9000 by Samba: ~62MB/s
Transfer from laptop with Windows 10 to USB drive attached to R9000 by FTP: ~73MB/s

Maybe you should try FTP?

Voxel.

 

[ecsjjgg]

I want to thank you for this release, @Voxel , because now my R9000 works perfectly... I've had nothing but troubles with it lately for example slow browsing, and slow access to my Qnap TS-451A...

I have also had to change my channel on the 5 GHz network multiple times a week, as no devices could connect to it...

But this firmware works, I have not had to change my 5 GHz channel in about a week, and browsing is as fast as I could expect!

I 'Dirty Installed' it over the last of your release, I mean that I did not clear the data/factory reset my R9000


And I might add that I use strict access control (block all new devices from connecting)
I also use QOS

Both of this settings where off in the previous releases of your F/W, as it made my browsing even slower...

 

[wildfirebill]

Having a bit of trouble with usb ports, installed latest release last night trying to install netware server but usb ports aren't showing up.

Sent from my SM-N950U using Tapatalk

 

[multicast]

Continuation of:

https://www.snbforums.com/threads/custom-firmware-build-for-r9000.40125/
. . .
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-r8900-v-1-0-4-39-1hf.62968/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-r8900-v-1-0-4-40hf.63602/

New version of my custom firmware build: 1.0.4.41HF.

Changes (vs 1.0.4.40HF):

1. net-wall script is fixed for ppp0 connection and modifyed to provide more safety (OpenVPN/WireGuard client, thanks to R. Gerrits).
2. OpenVPN: vpn-firewall.sh script is fixed (thanks to R. Gerrits).
3. DNSCrypt Proxy v.2 init script is fixed (time synchronization, thanks to kamoj).
4. ipset package is upgraded 7.4->7.6+ [2020-03-09].
5. iptables package is upgraded 1.4.21->1.8.4.
6. wireguard package is upgraded 1.0.20200413->1.0.20200520.
7. wireguard-tools package is upgraded 1.0.20200319->1.0.20200513.
8. curl package is upgraded 7.69.1->7.70.0.
9. dbus package is upgraded 1.12.12->1.13.12.
10. libubox package is upgraded 2020-02-27->2020-05-25.
11. uci package is upgraded 2020-01-27->2020-04-24.
12. unbound package (used in stubby) is upgraded 1.9.6->1.10.1.
13. yaml package (used in stubby) is upgraded 0.2.2->0.2.4.
14. util-linux package is upgraded 2.35.1->2.35.2.
15. sqlite package is upgraded 3310100->3320100.
16. nano package is upgraded 4.9.2->4.9.3.
17. Toolchain: Go is upgraded 1.14.1->1.14.3.

The link is:

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

Voxel.

@Voxel I've been using your FWs for a while now, something weird happened yesterday, well have been happened for couple weeks now, even before upgrading to 1.0.4.41HF. My R9000 was rebooting itself several times, I couldn't detect why nor find a clue in the logs either, to make story short it died yesterday, only the LAN lights were on if something was plugged, nor IP nothing, antenna lights were dead and power light off.

After buying and emergency replacement, today I was able to upload the FW again using TFTP after pressing the reset button for several times, I got the blinking Power LED and was able to ping its default IP.

Question is, now is running 1.0.4.41HF, it seems to be fine but is there any file/log I could check for errors or a clue about what could happened or if the issue is still there and waiting to go down again?

One thing I noticed, I couldn't restore my configuration from the Backup, every time I tried the R9000 just stopped responding or was erratic, had to do everything from scratch.

I had the QoS enabled, I think everything started when I enabled, I meant the sporadic reboots.


Any help from your experience is VERY appreciated.

 

[Voxel]

Question is, now is running 1.0.4.41HF, it seems to be fine but is there any file/log I could check for errors or a clue about what could happened or if the issue is still there and waiting to go down again?

Usually all messages are in the file

/var/log/log-message

You can check it. I hope your R9000 should be OK.

One thing I noticed, I couldn't restore my configuration from the Backup, every time I tried the R9000 just stopped responding or was erratic, had to do everything from scratch.

Probably you config is spoiled somehow, just save new config.

Voxel.

 

[multicast]

Usually all messages are in the file

/var/log/log-message

You can check it. I hope your R9000 should be OK.



Probably you config is spoiled somehow, just save new config.

Voxel.

@Voxel Thank you, it seems to be working fine since I restored the FW, can't find any major error messages within log-message log, I'll keep an eye if reboots come back again. Thanks for the info.

Was testing the Netgear AX45 but can't see is better tho, maybe is because I'm not using AX, I'll go the AX80 and TP-Link Archer AX6000. Do you have plans for developing customized FW for the new Nighthawk AXs line?

 

[blueliner]

Hello,

This is running really well..simply awesome firmware for the R9000. Thank you.