• [6.9.2] No connection br0 -> bridge

    • Minor

    Hello guys,


    The problem:

    I have some docker containers that I configured on br0 and gave them a new IP in my network(different then UnRaid's IP)

    They work fine but unfortunately they don't even have ping to UnRaid's IP (bridge).

    It seems the other way around is also true. I cannot ping a docker container with br0 IP from UnRaid.

    Needless to say ping is not the problem itself but the fact that there are no connections between them.


    The issue:

    You cannot install a DNS filter in a docker container(on a different br0 IP) and have the whole UnRAID server use it.


    Steps to reproduce:

    Install a docker image (Nextcloud in my case) assign an IP on br0 and:

    1. Open the docker's console and try to ping/access the UnRaid's IP. It will not work.

    2. From UnRaid's console try to ping/access the br0 IP docker image. It will not work.



    It seems this is an issue only with docker! If I assign a br0 IP on a VM there is no issue whatsoever.



    Am I getting something wrong here? Or should this be working?


    Thanks in advance,



    User Feedback

    Recommended Comments

    This is actually by design with Docker. We've discussed this at length before and your options each with their own caveats are:

    1. enable host access to docker networks in the Settings | Docker (Advanced View)
      my screenshot is disabled since I don't use it
    2. Enable VLANs in Settings | Network Settings
      and add custom networks in Docker settings
    3. If you have a spare Network card, you can keep it separate from the default bond between the other network interfaces (usually bond0) and then setup a custom network there for docker

    It is best to setup Unraid so it only has an IP in an interface that is not the same as the one being used by docker else the issue with connectivity will occur
    Some older threads for more details:



    • Thanks 1
    Link to comment

    Thank you very much for the reply and explanation!

    I guess vlans will be the rabbit hole I'll go down on.

    Link to comment

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Status Definitions


    Open = Under consideration.


    Solved = The issue has been resolved.


    Solved version = The issue has been resolved in the indicated release version.


    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.


    Retest = Please retest in latest release.

    Priority Definitions


    Minor = Something not working correctly.


    Urgent = Server crash, data loss, or other showstopper.


    Annoyance = Doesn't affect functionality but should be fixed.


    Other = Announcement or other non-issue.