net

Setting up bonding using NetworkManager on eth interfaces

creating bond connection

nmcli con add type bond ifname mybond0 bond.options "mode=balance-alb"

adding ethernet cards to bonding

serwer /home/backup # nmcli con add type ethernet ifname enp0s29u1u1 master mybond0
Connection 'bond-slave-enp0s29u1u1' (8a069f83-f95b-4dd5-9963-1d8c9dcfc539) successfully added.

serwer /home/backup # nmcli con add type ethernet ifname enp1s0 master mybond0
Connection 'bond-slave-enp1s0' (12b6d022-101e-4c8c-87d2-d6efe1f79dfd) successfully added.

after adding you have to put interface up

serwer /home/backup # nmcli con up bond-slave-enp1s0
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)

serwer /home/backup # ifconfig
enp0s29u1u1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether f6:99:69:f9:43:fe  txqueuelen 1000  (Ethernet)
        RX packets 5929  bytes 1061146 (1.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 287  bytes 80351 (78.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether f6:99:69:f9:43:fe  txqueuelen 1000  (Ethernet)
        RX packets 1362209365  bytes 1985983975123 (1.8 TiB)
        RX errors 29  dropped 3  overruns 0  frame 29
        TX packets 533809288  bytes 101619941777 (94.6 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 27  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5812409  bytes 946683892 (902.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5812409  bytes 946683892 (902.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

mybond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        inet 10.0.1.10  netmask 255.255.255.0  broadcast 10.0.1.255
        inet6 fe80::50ae:b62e:aff0:23f1  prefixlen 64  scopeid 0x20<link>
        ether f6:99:69:f9:43:fe  txqueuelen 1000  (Ethernet)
        RX packets 590  bytes 148539 (145.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 265  bytes 111298 (108.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Reference 1 Reference 2

Wireless Signal Strength and Noise Levels

Signal Strength

The signal strength is the wireless signal power level received by the wireless client.

  • Strong signal strength results in more reliable connections and higher speeds.
  • Signal strength is represented in -dBm format (0 to -100). This is the power ratio in decibels (dB) of the measured power referenced to one milliwatt.
  • The closer the value is to 0, the stronger the signal. For example, -41dBm is better signal strength than -61dBm.

Noise Level

The noise level indicates the amount of background noise in your environment.

  • If the noise level is too high, it can result in degraded strength and performance for your wireless signal strength.
  • Noise level is measured in -dBm format (0 to -100). This is the power ratio in decibels (dB) of the measured power referenced to one milliwatt.
  • The closer the value to 0, the greater the noise level.
  • Negative values indicate less background noise. For example, -96dBm is a lower noise level than -20dBm.

Signal to Noise Ratio

The signal-to-noise ratio (SNR) is the power ratio between the signal strength and the noise level.

  • This value is represented as a +dBm value.
  • In general, you should have a minimum of +25dBm signal-to-noise ratio. Lower values than +25dBm result in poor performance and speeds.

For example:

  • If you have a -41dBm signal strength, and a -50dBm noise level, this results in a poor signal-to-noise ratio of +9dBm.
  • If you have a -41dBm signal strength, and a -96dBm noise level, this results in an excellent signal-to-noise ratio of +55dBm.