Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SYSNICS network config?

Featured Replies

What does the SYSNICS="1" mean or do in the /boot/config/network.cfg file?

My unraid server uses LACP bond mode 4 with two physical NICs, apparently it works, but I'd like to finetune where possible.

Shouldn't it be SYSNICS="2" then?

 

I use bonding on a remote debian server with this config:

auto lo
iface lo inet loopback

auto bond0
iface bond0 inet manual
bond-slaves enp1s0 enp2s0
bond-mode 802.3ad
bond-miimon 100
bond-updelay 200
bond-downdelay 200
bond-lacp-rate 0
bond-xmit_hash_policy layer3+4

auto br0
iface br0 inet static
address 192.168.1.9
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 127.0.0.1
bridge_ports bond0
bridge_waitport 0
bridge_fd 0

 

And I would like to have my unraid server use the same settings for its bond mode 4. Currently it's:

 

# Generated settings:
IFNAME[0]="br0"
BONDNAME[0]="bond0"
BONDING_MIIMON[0]="100"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BONDING_MODE[0]="4"
BONDNICS[0]="eth0 eth1"
BRNICS[0]="bond0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.11"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
DNS_SERVER1="192.168.1.9"
DNS_SERVER2="1.0.0.2"
USE_DHCP6[0]="no"
SYSNICS="1"

 

The bonding seems to work:

# ifconfig
bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500
        ether d0:50:99:d1:8f:47  txqueuelen 1000  (Ethernet)
        RX packets 370606  bytes 60409014 (57.6 MiB)
        RX errors 0  dropped 191  overruns 0  frame 0
        TX packets 2881873  bytes 4333925543 (4.0 GiB)
        TX errors 0  dropped 170 overruns 0  carrier 0  collisions 0

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.11  netmask 255.255.255.0  broadcast 0.0.0.0
        ether d0:50:99:d1:8f:47  txqueuelen 1000  (Ethernet)
        RX packets 338185  bytes 15248343 (14.5 MiB)
        RX errors 0  dropped 53  overruns 0  frame 0
        TX packets 86837  bytes 4182443853 (3.8 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:3d:e5:d5:ce  txqueuelen 0  (Ethernet)
        RX packets 650  bytes 75489 (73.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 497  bytes 124616 (121.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether d0:50:99:d1:8f:47  txqueuelen 1000  (Ethernet)
        RX packets 351441  bytes 57287347 (54.6 MiB)
        RX errors 0  dropped 4  overruns 0  frame 0
        TX packets 53320  bytes 69543800 (66.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x91300000-9137ffff

eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether d0:50:99:d1:8f:47  txqueuelen 1000  (Ethernet)
        RX packets 14203  bytes 2002583 (1.9 MiB)
        RX errors 0  dropped 3  overruns 0  frame 0
        TX packets 2824329  bytes 4262089349 (3.9 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x91400000-9147ffff

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5309  bytes 378075 (369.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5309  bytes 378075 (369.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethadea463: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 76:af:3b:7e:14:8d  txqueuelen 0  (Ethernet)
        RX packets 650  bytes 84589 (82.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 497  bytes 124616 (121.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether fe:54:00:57:cb:d9  txqueuelen 1000  (Ethernet)
        RX packets 6067  bytes 738073 (720.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12127  bytes 36184105 (34.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

So that looks OK now, but is there a way to set

bond-lacp-rate 0
bond-xmit_hash_policy layer3+4

in unraid network config?

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
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.