Posts by toppi

  • OMV 8 update to 8.0.5-2

    Hi,


    just for information if it cares. Also got those messages druing update, but everyting is okay:


  • Notification test mail not working in 8.0.1-1

    It´s not arm, it´s x86_64.


    After reboot, IPv6 is again enabled:


    Code
    root@intrepid:~# sysctl net.ipv6.conf.lo.disable_ipv6
net.ipv6.conf.lo.disable_ipv6 = 0
root@intrepid:~# sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 0


    One eror is gone but still:



    I then though reinstalling sendmail might be a good idea, but I think it´s not ;)


  • Notification test mail not working in 8.0.1-1

    I ran into trouble updating to OMV8 yesterday and thought that it was caused by IPv6. I was unable to download containerio but that was a sync problem on the repos.

    So I disabled IPv6 temporary but I thought it would be eabeld again after a reboot. Now I´m unsere whether I habe rebooted. I will do it now and rerun the commands.

  • Notification test mail not working in 8.0.1-1

    Sure:


    Code
    root@intrepid:~# ip addr show lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever

root@intrepid:~# sysctl net.ipv6.conf.lo.disable_ipv6
net.ipv6.conf.lo.disable_ipv6 = 1
root@intrepid:~# sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1

  • Notification test mail not working in 8.0.1-1

    Hi,


    the frst one completet without any error.


    Here´s the result from the 2nd, starting with the frist error:


  • Notification test mail not working in 8.0.1-1

    Hi votdev,


    thank you. I did, but still 2 errors. Here´s the output. Had to remove the first 5 or 6 entries vecause of the character limitations.:


  • Notification test mail not working in 8.0.1-1

    Did not work for me:


  • Issue during Upgrade

    During the omv-release-upgrade I got the follwing error:


    I fixed the upgrade using the fix7to8-script. But even now I can´t upgrade that package:



    Someone any ideas? Or is it a temporary problem with packet source?

  • OMV7 > OMV8 unable to start home assistant KVM

    Thanks a lot. Did the Upgrade today an ran into the same issue.


    Code
        <loader readonly='yes' type='pflash' format='raw'>/usr/share/ovmf/OVMF.fd</loader>
    <nvram template='/usr/share/OVMF/OVMF_VARS_4M.fd' templateFormat='raw' format='raw'>/var/lib/libvirt/qemu/nvram/UEFI-Test_VARS.fd</nvram>


    Adding the above lines did fix it for me. Thank you, gents!

  • LXC Container does not use the added MAC-Address

    Hi,


    I´ve created a LXC-Container and during setup I added a bridge interface with a static MAC-Address:


    But after each reboot, the MAC-Address changes but the right one is still in the .xml of the container^^




    AM I doing something wrong?

  • Can´t access pihole in macvlan

    Hey!


    Thank you. I´ve set it up in the lxc way now which works like a charm and was done in 5 Minutes. Additionally it gives me an IPv6 adress :)


    However...I think something is wrong with my OMV. If I connect through my Unify Router using the wireguard plugin I can reach every ressource in my network except OMV.


    Since yesterday I get DUP!´s when I ping my OMV from other machines. I have investigated so many hours but I can not see whtas wrong.


    I´m also considrering moving to Proxmox and virtualise OMV there.

  • Can´t access pihole in macvlan

    Hi,


    I was able to find out the reason, but I still don't understand why this is happening:


    If I start a VM in KVM plugin also using br0 as network interface, I can't no longer access a docker container using macvlan which also uses br0.


    If I stop the KVM VM I can immediately access the pihole docker container.


    Any hints?

  • Can´t access pihole in macvlan

    I´m completly out of ideas. I tried another container (adguard) with the same result. Outbound traffic ist working, ingress not.


    I don´t think that it is related to my network, because it does not work on OMV itself.


    Can someone see any errors here:


    Code
    root@intrepid:~# ip route get 192.168.178.252
192.168.178.252 dev br0 src 192.168.178.2 uid 0
    cache


    Code
    root@intrepid:~# traceroute 192.168.178.252
traceroute to 192.168.178.252 (192.168.178.252), 30 hops max, 60 byte packets
 1  intrepid.home.lan (192.168.178.2)  3052.725 ms !H  3052.691 ms !H  3052.683 ms !H

    Doesn´t it take much too long?


    Code
    root@intrepid:~# arp
Address                  HWtype  HWaddress           Flags Mask            Iface
unifi.home.lan           ether   76:ac:b9:5f:23:36   C                     br0
192.168.178.252                  (unvollständig)                          br0
192.168.178.81           ether   cc:5e:f8:15:0f:3d   C                     br0

    Might this be the problem? Missing ARP entry?

    Is it correct, that ingress is "false"?

  • Can´t access pihole in macvlan

    Quote from raulfg3

    sorry if is not relevant, but you can't access to a macvlan from other bridge network, you can access from a pc on the same lan, but not ressolve by swag for example, because swag is on bridge mode and pihole on macvlan.

    I'm trying to access from other pc's in the same network. One Linux notebook and a Windows pc.