Jump to content

  • BR0 missing after update to 6.10.0-rc4 when enabling IPV6

    Taubin

    By Taubin

      • Solved Minor

    I updated to the latest rc4 and have been having an issue with networking. When enabling ipv6, the network goes down and does not come back up until I force a reboot. I let the system sit for quite a while and it just timed out until I forced a reboot. On reboot, the system came back up and was assigned an ipv6 address properly, however BR0 is missing. I did the following after reading quite a few posts here:


      

    rm /var/lib/docker/network/files/local-kv.db

/etc/rc.d/rc.docker restart

     

    That did not bring back BR0 at all. I've rebooted since then and still cannot get BR0 back.

     

    Screenshot and diag file attached.

     

     

    unraid2.png

    unraid1.png

    plunkett-server-diagnostics-20220320-1414.zip

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    bonienl

    Uncheck the br0 DHCP pool for IPv6 under Docker Settings.

    Docker uses SLAAC and a DHCP pool is not required.

     

    • Upvote 1
    Link to comment
    Taubin
    9 hours ago, bonienl said:

    Uncheck the br0 DHCP pool for IPv6 under Docker Settings.

    Docker uses SLAAC and a DHCP pool is not required.

     

     

    Thank you! I feel so dumb now. It's working properly, thank you very much.

    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.

    Guest
    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.

×
×
  • Create New...