It would be nice to have a way to disable the Docker DHCP service.  The Docker DHCP setting in my 6.4 rc6 server is blank but this past weekend it started handing out network addresses and effectively took down my entire home network.  Looking through my Unifi controller I noticed that devices were getting assigned 169.254.??.?? and 172.17.0.?? network addresses and then getting reassigned proper address for my network.   It took me a couple of hours to trace down the problem while working with Unifi support and only found it by luck because I remembered reading that the new Docker process can hand out addresses if desired to do so.  I turned the Docker process off and my network started working properly again.  I started running unRaid 6.4 with rc5.  When I rebooted the server after the update, the server was assigned a 169.254.??.?? address.

 

I also believe this is what is causing my bond0 (unRaid main network connection) to fail on a server reboot.  It is getting assigned a 169.254.??.?? address.  See this thread for more information on that problem.  I have been running a bonded connection ever since I started using unRaid back in version 6.2.  The current behavior is new and just started with 6.4.

 

The server is assigned 10.205.1.6 notice it is reporting that it is assigned 169.254.76.230

 

root@mccserverur01:~# ifconfig
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        inet 10.205.1.6  netmask 255.255.255.0  broadcast 10.205.1.255
        inet6 fe80::225:90ff:fe66:89f8  prefixlen 64  scopeid 0x20<link>
        ether 00:25:90:66:89:f8  txqueuelen 1000  (Ethernet)
        RX packets 22262757  bytes 9167171872 (8.5 GiB)
        RX errors 0  dropped 85  overruns 0  frame 0
        TX packets 200650061  bytes 26828194621 (24.9 GiB)
        TX errors 0  dropped 7 overruns 0  carrier 0  collisions 0

 

Edited July 7, 20178 yr by csmccarron

I've not had any if the issues you speak of, I'm running bonds and vlans networking wise.

 

One bit of feedback I can provide is its not DHCP handing out 169.x addresses, these are local private addresses you computer will take if no IP is assigned from DHCP.

 

That been said unraid should be using bond0 as its primary interface based on what I understand. The 169 must be coming from one interface, is it showing up on any of the others interfaces? - Edit I've not tested how often the webUI updates the IP listed in the UI, could be old information. Someone else may be able to confirm that.

Do you have two interfaces assigned to bond0?

Edited July 10, 20178 yr by Tuftuf

The problem the OP have is fixed in next rc. There was a problem when two binds were created.

bond0 is for unRaid.  All other NICs are for virtual machines including bond4 and are not looking for addresses when unRaid boots.  When the next RC comes out I will test to see if it is fixed.  Prior to installing 6.4, bond0 would get assigned the correct address during boot that my Unifi USG gave it.  All my network addresses are manages via the Unifi Controller so when unRaid is booting, it has to ask the network for an address.  Even though it shows the incorrect address on the screen, ifconfig shows the correct address.