February 7, 20188 yr I moved from a tower which had a 2-port nic on the motherboard and a 6-port nic to a rackmounted chassis which didn't have room for the 6-port nic. Before switching the chassis, configured interfaces in the network settings for unRaid would automatically create the docker networks which would then make them available in the network type list when configuring a container template. After the switch the only networks that are created are bridge, host, none, br0 (over eth0 configured in the network settings). Eth1 is configured in unRaid, however, the network isn't created in docker. I can manually create the network and it is then listed among the network types in the container template, but this has to be done each time the array is started. Also, my network.cfg file continues to generate configurations from the previous 6-port NIC. Settings for br0 and eth1 are correct. Settings for eth2 were configured with the 6-port NIC which no longer exists. I tried removing the configuration, but it continues to get created. Any help is appreciated. IFNAME[0]="br0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="10.0.99.1" DNS_SERVER2="" DNS_SERVER3="" DHCP6_KEEPRESOLV="no" BRNAME[0]="br0" BRNICS[0]="eth0" BRSTP[0]="no" BRFD[0]="0" DESCRIPTION[0]="" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="10.0.3.2" NETMASK[0]="255.255.255.0" GATEWAY[0]="10.0.3.254" METRIC[0]="" USE_DHCP6[0]="yes" IPADDR6[0]="" NETMASK6[0]="" GATEWAY6[0]="" PRIVACY6[0]="" MTU[0]="" IFNAME[1]="eth1" DESCRIPTION[1]="" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="10.0.8.0" NETMASK[1]="255.255.255.0" GATEWAY[1]="10.0.8.254" METRIC[1]="" USE_DHCP6[1]="" MTU[1]="" IFNAME[2]="eth2" DESCRIPTION[2]="" PROTOCOL[2]="ipv4" USE_DHCP[2]="no" IPADDR[2]="10.0.8.2" NETMASK[2]="255.255.255.0" GATEWAY[2]="10.0.8.254" METRIC[2]="" USE_DHCP6[2]="" IPADDR6[2]="" NETMASK6[2]="" GATEWAY6[2]="" PRIVACY6[2]="" MTU[2]="" SYSNICS="3" store-diagnostics-20180207-0959.zip Edited February 7, 20188 yr by bokchoy Added diagnostics
February 7, 20188 yr Author 22 minutes ago, bonienl said: Please update to unRAID 6.4.1. Ok, I'll upgrade tonight and report back.
February 8, 20188 yr Author 13 hours ago, bonienl said: Please update to unRAID 6.4.1. Upgrading to 6.4.1 fixed this issue. Thanks!
Archived
This topic is now archived and is closed to further replies.