Posts by MarcS

  • Wireguard Plugin settings no longer working in OMV7

    Hi - my Wireguards settings from OMV6 are no lnger working in OMV7.


    It used to be super simple to setup Wireguard for split traffic. All I had to do is tick Restrict on Server side and add my relevant Remote Network range to the WG-Client profile and it worked.


    With OMV7 I cannot get the same setup to work with Wireguard.

    To even reach the WG-Network client at all I need to amend the Client-Profile to include the Local (!) (not the Remote) network range. Still I cannot in any configuration reach the other Local hosts.


    I tried every configuration option in the OMV Plugin. Maybe anyone has some ideas?


    Here is my configuration:


    Remote Client_E1 on 192.168.1.0/24 ----INTERNET---[local network: 192.168.9.0/24 Wireguard Server_Host 1------Host 2----Host 3]


    I want to be able to connect via SSH and Webbrowser from E1 to Host1 and all hosts on the local network (Host 2 and Host 3)

    OMV6 settings is simple:

    Server: Restric [X]

    Client profile: Allowed IPs: 192.168.1.0/24

    -> worked fine


    OMV7 settings :

    I cannot access any hosts on the local network, other than the wireguard host itself.


    I tried the following settings:


    1)

    Server side:

    Restrict [X]

    Restrict routing to VPN subnet only [ ]

    Restrict routing to Local subnet only [ ]


    WG Client profile: Allowed IPs: 192.168.1.0/24 (this setting used to work in OMV6)

    -> no server is reachable at all


    2)

    Server side:

    Restric [X]

    Restrict routing to VPN subnet only [X}

    Restrict routing to Local subnet only [ ]


    WG Client profile: Allowed IPs: 192.168.9.0/24

    -> only the Wireguard server is reachable but no other host in the destination network is reachable


    3)

    Server side:

    Restric [X]

    Restrict routing to VPN subnet only [X]

    Restrict routing to Local subnet only [X]


    WG Client profile: Allowed IPs: 192.168.9.0/24

    -> only the Wireguard server is reachable but no other host in the destination network is reachable


    4)

    Server side:

    Restric [ ]

    Restrict routing to VPN subnet only [ ]

    Restrict routing to Local subnet only [ ]


    WG Client profile: Allowed IPs: 192.168.9.0/24

    -> only the Wireguard server is reachable but no other host in the destination network is reachable

  • ZFS on Raspberry Pi - howto

    So I installed the kernel headers and ZFS and rebooted.
    When I try to create apool its complainng...

    Code
    The ZFS modules cannot be auto-loaded.
Try running 'modprobe zfs' as root to manually load them.

running "modprobe zfs" gives me:
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.6.42-v8+

    Do you know what I am missing?

  • ZFS on Raspberry Pi - howto

    Is there a way to add Proxmox Kernel and ZFS on Raspberry Pi 4? It can run a 64Bit Kernel.

    I tried to install ZFS on the RPI but it doesn run (although it installs the plugin).

    I also tried to install the OMB Kernel PLugin (for Proxmox) but OMV7 says Plugin is not available.

    Is there anything I can do?

    many thanks

  • Errors from "openmediavault-cleanup_sf_snapshots"

    Does anyone know how the below error is linked to the snapshot clean-up rules? There must be an orphan line in there...

    "/etc/cron.hourly/openmediavault-cleanup_sf_snapshots:"

    Code
    ERROR: not a btrfs filesystem: /srv/dev-disk-by-uuid-676c97c6-950d-4fe7-911f-1d3fb2e83756
ERROR: can't access '/srv/dev-disk-by-uuid-676c97c6-950d-4fe7-911f-1d3fb2e83756'
Traceback (most recent call last):
  File "/sbin/omv-sfsnapadm", line 286, in <module>


    any ideas?

    many thanks

  • Errors from "openmediavault-cleanup_sf_snapshots"

    I am getting error messages from Snapshot managent after removing a disk from the server. I checked and tHere are currently no more snapshots scheduled for the deleted disk.

    Please see error message below. How can I remove this? many thanks

  • OMV shared folder permissions

    I am having trouble with OMV folder permissions on a filesystem created by Synology.

    OMV can mount and see everything fine but when I create Shared Folders + SMBs , the permissions don't allow for write access from a remote host.

    Only after I run chmod 02775 on Foldername, the respective SMB becomes writeable.


    Why is that? Do I have to manually run chmod on every folder I want to share? I thought creating a shared folder takes care of that.

    This is the setup:

    OMV1---Folder1 (shared folder)----SMB---+++++++++++---OMV2

  • rootfs matches resource limit

    Quote from ryecoaaron

    Use this instead: du -d1 -h -x /var/ | sort -h (the -x will not check the space of other filesystems). A quick look of your other output tells me it is mostly in /var though. Probably logs, docker, or plex.

    thanks. This command saved my day. I had my 32GB root fs at 99% !! Nervous .....:)

  • Linux Raid1 to Raid5

    I have a NAS with 2 disks in Raid1 full of data.

    Has anyone managed to migrate a Linux Raid1 to a Raid5 setup by adding 1 disk, while the data on the 2 original disks is retained? Theoretical this should be no problem but the internet is somewhat inconclusive so I was wondering if anyone has actually done it and all data was intact.

    thanks!

  • Migrate OMV to new platform

    as far as I understood the debian text Avahi provides hostnames independentent of any DNS service. So it could be cresting errors when Regen forces it to name the new host (using the same hostname) while the old host is still connected on the network. This was my case. The old host remains on the network.