Beiträge von toppi

    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?

    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.

    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?

    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"?

    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.


    However, I have not yet received an answer to one question. Do other dockers work? If so, this may also be a specific Docker problem. If no, then the search continues in the VLAN.

    I only use pihole with macvlan. All my other docker containers without macvlan are running fine.

    But when I created the macvlan in my default lan, nothing from unifi comes in place to prevent network access.


    So my OMV has the IP 192.168.178.2 and I created the macvlan in that network. Pihole had 192.168.178.252 and it worked for ages....

    Yes. It's a Unifi switch. And again, I can reach any network from the container. But I can not access the container.


    Exact the same problem.


    I've created the new vlan, created the macvlan for it in OMV and assigned it to the pihole container. Same behavior.


    I`m using a bridge in OMV to allow a Windows VM to access the localhost. Perhaps something has changed there?

    Strange.


    I have now created the macvlan manually and referred to it in the pihole yaml. Container comes up, correct IP assigned but again, I can't access pihole or even ping it. But no problem to ping the e.g. the host IP from the container.

    Hi,


    since a few days I have a strange problem with my pihole configuration. It worked without any issues, but now I can't access pihole anymore.


    It starts without problems and gets the correct IP (192.168.178.252) assigned, but no external access is possible, but I can ping any address from within the container:



    And here is my yaml:



    Any ideas?