Custom firmware build for R7800 v. 1.0.2.74.2SF & v. 1.0.2.74.3SF

[kamoj]

Run this command from the router command line to fix the problem:

sed -i '38,46d' /usr/sbin/net-wall

(It makes the same change as when installing 1.0.2.74.3SF)

To restore to original:

\cp -p /rom/usr/sbin/net-wall /usr/sbin/net-wall

 

[MinkyMomo]

I lost the ability to connect to my Sonos devices from the phone app upon upgrading from 74.1SF to 74.2SF, and dropped back to 74.1SF; upon upgrading to 74.3SF, my Sonos devices are back.

I do run OpenVPN server on my router.

 

[Cruncher]

I am also using OpenVPN. Just installes V3 and everything is working fine.

Thank you for your effort.

 

[tarassippo]

After updating to 1.0.2.74.2SF I can no longer access the router neither through WinSCP nor thorough PuTTY, error with the key: does it mean I have to go through the process of re-creating the 'authorised keys' as per Voxel's readme.doc file ? ?

 

[Sizzlechest]

After updating to 1.0.2.74.2SF I can no longer access the router neither through WinSCP nor thorough PuTTY, error with the key: does it mean I have to go through the process of re-creating the 'authorised keys' as per Voxel's readme.doc file ? ?

Any firmware update wipes the root directory, which includes the keys. You should get a thumbdrive and use it to store a backup of your root directory. It can be configured to reinstall your settings if they are missing after a new firmware install.

Format the thumbdrive as ext3 and create a post-install.sh script in the folder autorun/scripts. Here's mine:

#!/bin/sh
if [ ! -f "/root/firewall-start.sh" ]
then
  cp /tmp/mnt/$1/firewall-start.sh /root/.
  chmod a+x /root/firewall-start.sh
fi

if [ ! -f "/root/.ssh/authorized_keys" ]
then
  mkdir -p /root/.ssh
  cp /tmp/mnt/$1/authorized_keys /root/.ssh/authorized_keys
fi

if [ ! -f "/overlay/etc/dnscrypt-proxy-2.toml " ]; then
  sed -i -r "s/^(server_names[[:space:]]*=[[:space:]]*).*/\1['cloudflare']/" /etc/dnscrypt-proxy-2.toml

fi

 

[kamoj]

Update to 74.3SF or :
https://www.snbforums.com/threads/c...4-2sf-v-1-0-2-74-3sf.61962/page-2#post-554127

I lost the ability to connect to my Sonos devices from the phone app upon upgrading from 74.1SF to 74.2SF, and dropped back to 74.1SF; upon upgrading to 74.3SF, my Sonos devices are back.

I do run OpenVPN server on my router.

 

[tarassippo]

Ah great stuff, thank you @Sizzlechest... So, as long as I backup both 'authorized_keys' file and 'my.ppk' file, I am good to go, is that right ?

No need to keep a copy of 'id_dropbear' / 'id_rsa' / 'id_rsa.pub' ?

 

[microchip]

Ah great stuff, thank you @Sizzlechest... So, as long as I backup both 'authorized_keys' file and 'my.ppk' file, I am good to go, is that right ?

No need to keep a copy of 'id_dropbear' / 'id_rsa' / 'id_rsa.pub' ?

you should copy the dropbear keys too

 

[Sizzlechest]

you should copy the dropbear keys too

I don't care about connecting from my router to another computer, so I don't have that stuff, but if you care about that, they should be included.

Just to break down my script for clarity:

#!/bin/sh
if [ ! -f "/root/firewall-start.sh" ]
then
  cp /tmp/mnt/$1/firewall-start.sh /root/.
  chmod a+x /root/firewall-start.sh
fi

This copies a file "firewall-start.sh" from the USB drive to the /root directory if it's missing. I need this because I have a special firewall rule that can't be done through the GUI and needs a custom iptables command.

if [ ! -f "/root/.ssh/authorized_keys" ]
then
  mkdir -p /root/.ssh
  cp /tmp/mnt/$1/authorized_keys /root/.ssh/authorized_keys
fi

This is to allow me to connect via PuTTY. Like I said, I don't care about keys on the router since I don't have a need to ssh from the router to another computer or device. If you have other files, add them to this list.

if [ ! -f "/overlay/etc/dnscrypt-proxy-2.toml" ]; then
  sed -i -r "s/^(server_names[[:space:]]*=[[:space:]]*).*/\1['cloudflare']/" /etc/dnscrypt-proxy-2.toml

fi

I want to use encrypted DNS, but the defaults of dnscrypt proxy use servers that are not optimal for my location. I'd rather use Cloudflare. This will edit the default dnscrypt-proxy-2.toml file to only use Cloudflare. You do NOT want to copy a modified dnscrypt-proxy-2.toml file off the USB drive since this file will change when a new version of dnscrypt proxy is included in the firmware update, thus you will be missing other new or changed default settings. It's better to modify the new default file on-the-fly using sed.

 

[microchip]

I meant the dropbear host keys in /etc/dropbear

 

[tarassippo]

I meant the dropbear host keys in /etc/dropbear

I was under the impression that those keys are the always the same as Voxel doesn't change them in his firmware updates...

 

[microchip]

I was under the impression that those keys are the always the same as Voxel doesn't change them in his firmware updates...

Those are default ones but it's recommended to change them as per README of Voxel, which also includes how to do it

 

[tarassippo]

Those are default ones but it's recommended to change them as per README of Voxel, which also includes how to do it

Fully clear now... You need to back up also the keys in the /etc/dropbear folder only if you don't want to stick with the generic ones provided in Voxel's firmware and you are going to make your own keys

 

[Luizk]

voxel thank you sr

 

[Alex Wood]

EDIT: Ignore this, updated to 74.3 again and it's working this time...
Upon update to 74.3 (from 74.1) my port forward rules no longer work (but are still listed in the web UI).

 

[kamoj]

There is no change regarding this - what I can see.
Reboot once and try again. Next step:
But you can revert to 74.1SF and see if it works again.

Upon update to 74.3 (from 74.1) my port forward rules no longer work (but are still listed in the web UI).

 

[Alex Wood]

There is no change regarding this - what I can see.
Reboot once and try again. Next step:
But you can revert to 74.1SF and see if it works again.

Very weird, I'd already reverted to 74.1, which got everything working again. But I've just reinstalled 74.3 to try a few mire things, and it is working fine, so ignore me completely - maybe the firmware got corrupted during the first update or something, but as I say it's working now.

 

[e38BimmerFN]

Next time, if you encounter problems after a FW update, try a factory reset and setup from scratch to see if the problem continues or gets resolved.

Very weird, I'd already reverted to 74.1, which got everything working again. But I've just reinstalled 74.3 to try a few mire things, and it is working fine, so ignore me completely - maybe the firmware got corrupted during the first update or something, but as I say it's working now.

 

[scooter2765]

Installed .3 works for me great ..Thanks Voxel

 

[ngoquata]

I reset my R7800 setting and installed .74.3SF.
I install Entware follow instruction in readme.

root@R7800:~$ mkfs.ext4 -L optware /dev/sda1
mke2fs 1.45.5 (07-Jan-2020)
/dev/sda1 contains a ext4 file system labelled 'hdd35'
        last mounted on Thu Jan  1 07:00:26 1970
Proceed anyway? (y,N) y
Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and                                                                                                                                                              journal checksum features.
Creating filesystem with 122096384 4k blocks and 30531584 inodes
Filesystem UUID: 290a8fae-b920-4735-a118-3580aa949022
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

root@R7800:~$ tune2fs -O ^metadata_csum,^64bit /dev/sda1
tune2fs 1.45.5 (07-Jan-2020)
Disabling checksums could take some time.
Proceed anyway (or wait 5 seconds to proceed) ? (y,N) y
Please run `resize2fs -s /dev/sda1' to disable 64-bit mode.
root@R7800:~$ cd /tmp/mnt/sda1
root@R7800:/tmp/mnt/sda1$ wget https://www.voxel-firmware.com/Downloads/Voxel/En                                                                                                                                                             tware/entware-cortex-a15-3x-initial-generic.tar.gz
--2020-03-01 07:30:59--  https://www.voxel-firmware.com/Downloads/Voxel/Entware/                                                                                                                                                             entware-cortex-a15-3x-initial-generic.tar.gz
Resolving www.voxel-firmware.com... 194.135.87.112
Connecting to www.voxel-firmware.com|194.135.87.112|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5536132 (5.3M) [application/x-gzip]
Saving to: 'entware-cortex-a15-3x-initial-generic.tar.gz'

entware-cortex-a15- 100%[===================>]   5.28M   651KB/s    in 9.7s

2020-03-01 07:31:12 (557 KB/s) - 'entware-cortex-a15-3x-initial-generic.tar.gz'                                                                                                                                                              saved [5536132/5536132]

root@R7800:/tmp/mnt/sda1$ tar -xzf entware-cortex-a15-3x-initial-generic.tar.gz
root@R7800:/tmp/mnt/sda1$ reboot

but after reboot there is NO entware directory like it should be

root@R7800:~$ ls -l /opt/*
-rw-r--r--    1 root     root          855 Jan  1  1970 /opt/filelist
-rw-r--r--    1 root     root            9 Jan  1  1970 /opt/version

/opt/kamoj:
drwxr-xr-x    3 root     root          232 Feb 22 14:37 addons

/opt/leafp2p:
-rwxr-xr-x    1 root     root       729056 Jan  1  1970 leafp2p

/opt/rcagent:
drwxr-xr-x    2 root     root          232 Jan  1  1970 cgi
-rwxr-xr-x    1 root     root       355008 Jan  1  1970 cgi_processor
-rwxr-xr-x    1 root     root        39044 Jan  1  1970 downloader
-rwxr-xr-x    1 root     root        11624 Jan  1  1970 nas_service
-rwxr-xr-x    1 root     root       213760 Jan  1  1970 rcagentd
-rwxr-xr-x    1 root     root          145 Jan  1  1970 run_server.sh
drwxr-xr-x    2 root     root          576 Jan  1  1970 scripts

/opt/remote:
-rwxr-xr-x    1 root     root        92208 Jan  1  1970 remote
-rwxr-xr-x    1 root     root        21124 Jan  1  1970 run_remote

/opt/xagent:
drwxr-xr-x    2 root     root          240 Jan  1  1970 certs
-rwxr-xr-x    1 root     root        39708 Jan  1  1970 genie_handler
-rwxr-xr-x    1 root     root          333 Jan  1  1970 run-xagent.sh
-rwxr-xr-x    1 root     root        84344 Jan  1  1970 xagent
-rwxr-xr-x    1 root     root        18428 Jan  1  1970 xagent_control

Please help me with this.

Thanks for reading!