Posts by ahecht

Quote from space_ranger

Just an update with a solution I found for anyone suffering with this problem. You can add a delay to the startup by creating a systemd override.

Code

sudo systemctl edit libvirtd

Then add the following lines to delay for 30 seconds. That works for my setup but the time can be altered to whatever works for the sytem.

Code

[Service]
ExecStartPre=/bin/sleep 30

The autostart function is now working fine for me.

Display More

I know I'm dragging this up months later, but that same step solved the problem for me without having to disable IPv6. It would be nice if this could be automated in some way.

After the upgrade, eth0 got renamed to end0, so I had to go to Network -> Interfaces and create a new end0 interface, and then I had to upgrade the Wireguard plugin to use end0.

Ahh, figured it out. The upgrade somehow renamed eth0 to end0. I had to create a new network interface for end0 and then change my Wireguard tunnel to reference it. I missed that when running through omv7:omv7_plugins:wireguard [omv-extras.org] again since it doesn't mention setting the "Network adapter" field.

I have a Raspberry Pi 4. I was running OMV6 and Wireguard was working fine. I upgraded to OMV7 (7.7.0-2) using the instructions from crashtest at RE: OMV 6 -> 7 on Raspberry Bullseye

When I'm outside of my LAN and using the Android Wireguard app I can connect to the VPN. However, when connected, I can only access services running on the Pi such as the OMV GUI or webservices running in docker. SSH into the pi via the LAN IP address works too. However, if I try to access anything outside the Pi, whether on my LAN (such as my router's configuration page at 192.168.1.1) or via WAN, it doesn't go through and the connection just eventually times out. This all worked before the upgrade.

I found that I also had to add the following four lines to /etc/default/openmediavault :

OMV_SAMBA_LOADPRINTERS="yes"
OMV_SAMBA_PRINTING="CUPS"
OMV_SAMBA_PRINTCAPNAME="CUPS"
OMV_SAMBA_DISABLESPOOLSS="no"

I also had to add the following under Services -> SMB/CIFS -> Settings -> Extra options:

[printers]
   comment = All Printers
   browseable = yes
   path = /var/spool/samba
   printable = yes
   guest ok = yes
   read only = yes

I am running OMV 6 on a Raspberry Pi 4B with the Wireguard plugin. I used the default settings, which the documentation indicates should do IP forwarding. When I connect my phone to the tunnel using the official Wireguard app I can successfully access pages being served on my home LAN. However, if I go to https://www.whatismyip.com/ while connected to the tunnel I get the IP address of the phone's 4G connection, not the IP address of my home network.

My tunnel config is as shown:

[Interface]
Address = 10.192.1.254/24

SaveConfig = true
ListenPort = 51820
PrivateKey = [redacted]
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

[Peer]
PublicKey = [redacted]
AllowedIPs = 10.192.1.1/32
PresharedKey = [redacted]

And my client config is:

[Interface]
Address = 10.192.1.1/24
PrivateKey = [redacted]
DNS = 192.168.1.1

[Peer]
PublicKey = [redacted]
PresharedKey = [redacted]
Endpoint = [redacted]:51820
AllowedIPs = 0.0.0.0/0

I have verified that systemctl net.ipv4.ip_forward returns "1". I installed PiVPN on the same device at port 51821 and using the same app on my phone to connect to the non-OMV Wireguard server on that port does successfully give my the IP of my home network.

Does the OMV 6 install script work on the new Raspberry Pi OS Lite Bullseye version?