Beiträge von _calm_bomb_

Thanks people, that fixed it!

I did.. Nothing changes.

Hmmm... listing the packages on the system, I can see that the omv plugins are at 7.x:

# dpkg -l | grep -e 'openmediavault.*plugin'
ii  openmediavault-backup           7.1.4                                all          backup plugin for OpenMediaVault.
ii  openmediavault-borgbackup       7.0.8                                all          borgbackup plugin for OpenMediaVault.
ii  openmediavault-compose          7.2.7                                all          OpenMediaVault compose plugin
ii  openmediavault-diskstats        7.0.1-2                              all          openmediavault disk monitoring plugin
ii  openmediavault-fail2ban         7.0.1                                all          OpenMediaVault Fail2ban plugin
ii  openmediavault-nut              7.0.5-1                              all          openmediavault Network UPS Tools (NUT) plugin
ii  openmediavault-sharerootfs      7.0-1                                all          openmediavault share root filesystem plugin
ii  openmediavault-wireguard        7.0.7                                all          openmediavault WireGuard plugin
ii  openmediavault-zfs              7.1.1                                amd64        OpenMediaVault plugin for ZFS

So something is wrong in the web UI...

I just upgraded today to OMV 7.4.8 (from 7.0.4) and noticed that all my plugins are showing versions 6.x.

First of all, I have to mention I upgraded "manually", by running omv-upgrade in the terminal, because going to System > Update Management > Updates didn't show anything. Also, trying to scan for new updates from the web UI doesn't seem to do anything.

I'm trying to understand what is going on. I have this installation since v4.x or something like that and never had issues.

I will attach a omv-systeminfo output to this post.

What should I check or do to make my system up to date?

Zitat von chente

At this time all OMV6 plugins are compatible with OMV7.

Thanks a lot!

I'd like to upgrade to OMV7 and I see the message to make sure that all installed plugins are supported. How can I check this? I can't find a place that says what are the plugins supported in OMV7.

Zitat von chente

Well, you should check your network and/or your server, there is no other explanation.

Well, I'm (a bit) ashamed to say it was a classic issue of "did you try to turn off and on again?". I rebooted the server - I had multiple updates done yesterday - and lo and behold, it now works without problems!

Zitat von chente

That is not logical. If the tunnel has been configured with the plugin defaults you should access any host on the network (make sure the iptables box is checked). The only reason could be that you have some restriction in your network, it could be in the router or in the server (firewall, iptables...).

The iptables box is checked.

I created a tunnel and set up a client. I can connect from the client (Android phone) and I can reach every service on the server (10.11.12.77) and the router (10.11.12.1), but not other hosts. I have some raspberry pi's in the house used as media players and they are in the same LAN (10.11.12.105 and 10.11.12.106), but I can't reach them when connected through wireguard (with OMV Extras plugin). The local network is 10.11.12.0/24.

Also, IP forwarding is enabled:

# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

Any hints?

Zitat von raulfg3

perhaps can help you:

https://wiki.omv-extras.org/do…_the_same_lan_as_the_host

Thema

docker composer - networks

Hi all,

I am trying to migrate from Portrainer to Composer, and I have a question about the network configuration.

Prior, in Portainer, this was my config:
(Quelltext, 15 Zeilen)


... and I was using 192.168.1.x as the network in all my containers. Each with a different IP.

Now I'm trying to use this config, creating a file to each container:
(Quelltext, 18 Zeilen)


Only with this container, all was fine. But when I try to add another container with same config (only changing ipv4_address and…

Jubri

1. Juli 2023

This looks really great. I tried it and I was able to ping the host from the container, but not the other way around. I'll check this again this weekend, maybe I've overlooked something.

Thanks for pointing me to this!

Zitat von votdev

The decision is done by systemd-resolved as far as I have found out with Google. The fastest DNS server wins. I think you need to configure your DHCP server to only submit the IP address of interest.

As a workaround go the OMV network interface config page in the UI and enter 10.11.12.77 in the DNS server field. This way your manuall config will overrule DHCP.

Thanks. I thought of that too.. I'll play with some settings to see what helps better. I prefer to keep the DHCP server as it is, because sometimes the Pi-hole (very rarely) goes down and the second IP helps.

PS: also, my pi-hole is in fact a docker container on OMV itself, so I find it funny that the connection to it would be slower than to the router.

I'm running OMV 6.4.6 on baremetal. Since the last upgrade I noticed that the system doesn't resolve my local DNS records anymore.

The system is set up with DHCP and it receives two nameservers: 10.11.12.77, 10.11.12.1 - first one is the Pi-hole I run, second one is the router which forwards the requests to my ISP's DNS. I have set up some local hosts in the Pi-hole and it worked like a charm until a week ago. Also, I notice this happens only on the OMV machine.

Checking /etc/resolv.conf, it points correctly to /run/systemd/resolve/stub-resolv.conf, but running resolvectl I see it point to the router's IP address as default nameserver:

# resolvectl
Global
       Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink

Link 2 (enp3s0)
Current Scopes: DNS LLMNR/IPv4
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 10.11.12.1
DNS Servers: 10.11.12.77 10.11.12.1

What can I do to have .77 as default DNS always?