Voxel Fuse module for voxel firmware (RBR50)

[mgiunktode]

Voxel firmware is running great for me on RBR50, but, in debian, I'd like to run veracrypt which requires fuse module: do you think it is possible to add or is already there and I'm doing something wrong?

I get this error:
"Error: fuse: device not found, try 'modprobe fuse' first"

Thanks in advance

 

[R. Gerrits]

So you are running a chroot-ed Debian installation on the RBR50?
Not sure how to get fuse running in there.

If you were using Entware, then you could install fuse by doing:

/opt/bin/opkg install libfuse fuse-utils

Entware also has encfs.
(and I saw your other post, Entware also has cryptsetup but I don't have experience with that, nor with encfs)

 

[mgiunktode]

Thanks for your reply, in fact I installed cryptsetup from entware but it seems that module loop is missing in the kernel.
Unfortunately encfs also seems to be based on fuse, therefore I'm convinced it will not work and unfortunately it is quite different from veracrypt and cryptsetup and doesn't probably fit my needs.

Anyone knows how to build that module for the kernel in RBR50?


Thanks ;-)

 

[Voxel]

Interesting...

Anyone knows how to build that module for the kernel in RBR50?

Probably I do.

You can try:

https://www.voxel-firmware.com/Downloads/loop-fuse.tar.gz

This archive contains both fuse and loop:

drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/etc/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/etc/modules.d/
-rw-r--r-- root/root         5 2021-03-31 21:34 overlay/etc/modules.d/30-loop
-rw-r--r-- root/root         5 2021-03-31 21:36 overlay/etc/modules.d/80-fuse
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/modules/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/modules/3.14.77/
-rw-r--r-- root/root     23952 2021-03-31 21:35 overlay/lib/modules/3.14.77/loop.ko
-rw-r--r-- root/root     89172 2021-03-31 21:35 overlay/lib/modules/3.14.77/fuse.ko

You should use "Overlay partition on USB" to load these modules. See my QuickStart.txt.

Please let us know the results of your tests.

Voxel.

 

[mgiunktode]

Interesting...



Probably I do.

You can try:

https://www.voxel-firmware.com/Downloads/loop-fuse.tar.gz

This archive contains both fuse and loop:

drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/etc/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/etc/modules.d/
-rw-r--r-- root/root         5 2021-03-31 21:34 overlay/etc/modules.d/30-loop
-rw-r--r-- root/root         5 2021-03-31 21:36 overlay/etc/modules.d/80-fuse
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/modules/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/modules/3.14.77/
-rw-r--r-- root/root     23952 2021-03-31 21:35 overlay/lib/modules/3.14.77/loop.ko
-rw-r--r-- root/root     89172 2021-03-31 21:35 overlay/lib/modules/3.14.77/fuse.ko

You should use "Overlay partition on USB" to load these modules. See my QuickStart.txt.

Please let us know the results of your tests.

Voxel.

Thanks voxel... I'll try soon and let you know ;-)

 

[mgiunktode]

Interesting...



Probably I do.

You can try:

https://www.voxel-firmware.com/Downloads/loop-fuse.tar.gz

This archive contains both fuse and loop:

drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/etc/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/etc/modules.d/
-rw-r--r-- root/root         5 2021-03-31 21:34 overlay/etc/modules.d/30-loop
-rw-r--r-- root/root         5 2021-03-31 21:36 overlay/etc/modules.d/80-fuse
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/modules/
drwxr-xr-x root/root         0 2021-03-31 21:25 overlay/lib/modules/3.14.77/
-rw-r--r-- root/root     23952 2021-03-31 21:35 overlay/lib/modules/3.14.77/loop.ko
-rw-r--r-- root/root     89172 2021-03-31 21:35 overlay/lib/modules/3.14.77/fuse.ko

You should use "Overlay partition on USB" to load these modules. See my QuickStart.txt.

Please let us know the results of your tests.

Voxel.

Ok, I have been able to do some tests and the modules seem to work correctly and mostly solved my problem; therefore I kindly ask you to add them to your default workflow so that we can have them by default in every release of your firmware: I believe they are very relevant modules that help making your firmware vastly better than stock firmware with very limited impact on size.

In particular: I have been able to use, in voxel/entware, an encrypted cryptsetup filesystem which I created in ubuntu. By use I mean that I can add/remove files and so on. This seems to work great!!!

Some aspects I need to further investigate:

1) Initially I had some problem using modprobe with modules on the overlay partition and was only able to use insmod... but I'm not an expert of modprobe/insmod and maybe you have to use insmod the first time before modprobe... Now it seems that the modules get loaded automatically at boot... which is good. I need to further test.
[UPDATE] I further investigated and it seem that the modules doesn't always get loaded automatically at boot: sometimes they don't and I need to manually use insmod. This maybe depends on the modules being on the overlay filesystem. Voxel if you make them available by default in your firmware there would be no need to put them on the overlay and I think they would get reliably loaded at boot.

2) I had problems creating an encrypted cryptsetup container/filesystem in voxel/entware which resulted in an error (that's why I created it in ubuntu); but maybe It depended on the modules not being loaded because of 1) . I need to further test.

3) I've not been able to user veracrypt in debian chroot; may the problem is related to the capability of mounting the filesystem or creating the /dev/mapper device. I need to further invesitgate.

4) When I mount the cryptsetup filesystem in entware I can see and use it (good), but I cannot see it in the debian chroot (not so good). Anyone knows how can I access the filesystem both within fimware/entware and in debian chroot? I think it should be possible since It is the same priciple as /mnt/optware... or not? but I don't know if I have to do something with some configuration file/script.
[UPDATE] I further investigated and I found that in fact it is the same principle ad /mnt/optware and it is enough to bind the mounted filesystem inside /mnt/optware/set-debian.sh script; therefore issue SOLVED

Thanks again Voxel