LACP 802.3ad load balancing (bonding) on Ubuntu 18.04 not balancing evenly Announcing the...

Why is "Captain Marvel" translated as male in Portugal?

How many things? AとBがふたつ

Cold is to Refrigerator as warm is to?

Active filter with series inductor and resistor - do these exist?

What do you call a plan that's an alternative plan in case your initial plan fails?

What is the electric potential inside a point charge?

Limit for e and 1/e

Slither Like a Snake

How can players take actions together that are impossible otherwise?

I'm having difficulty getting my players to do stuff in a sandbox campaign

Should you tell Jews they are breaking a commandment?

Notation for two qubit composite product state

Direct Experience of Meditation

Replacing HDD with SSD; what about non-APFS/APFS?

Complexity of many constant time steps with occasional logarithmic steps

Unexpected result with right shift after bitwise negation

How should I respond to a player wanting to catch a sword between their hands?

Need a suitable toxic chemical for a murder plot in my novel

How do I automatically answer y in bash script?

Why does tar appear to skip file contents when output file is /dev/null?

What loss function to use when labels are probabilities?

The following signatures were invalid: EXPKEYSIG 1397BC53640DB551

Stop battery usage [Ubuntu 18]

Can a non-EU citizen traveling with me come with me through the EU passport line?



LACP 802.3ad load balancing (bonding) on Ubuntu 18.04 not balancing evenly



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Configure static IPv6 on UbuntuLinux bonding: 802.3ad (LACP) vs. balance-alb modetunneling layer 2 sshNIC Bonding works but can't pingLACP vs 802.3adIPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready & IPv6: ADDRCONF(NETDEV_UP): xenbr2: link is not ready on Ubuntu Server - Xen bridgeLink aggregation (LACP/802.3ad) max throughputStatic Public IP Address on Amazon EC2LACP - Load Balancing Network 2Gbit UbuntuWin2012R2 NIC Teaming with LACP, but one nic has not traffic





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I upgraded to Ubuntu 18.04 and the new Netplan configuration, but my (2) network cards stopped sharing the load evenly. In my network configuration, I have many connections to many different servers; this configuration worked with previous versions of Ubuntu.



My configuration is below:



network:
ethernets:
enp0s31f6:
dhcp4: false
enp1s0:
dhcp4: false
version: 2
bonds:
bond0:
interfaces: [enp0s31f6,enp1s0]
addresses: [10.0.10.10/16]
gateway4: 10.0.0.1
mtu: 9000
nameservers:
addresses: [10.0.0.1]
search: [mydomain.example.com]
parameters:
mode: 802.3ad
lacp-rate: fast
mii-monitor-interval: 100


However, ifconfig shows uneven distribution of the network load:



bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 9000
inet 10.0.10.10 netmask 255.255.0.0 broadcast 10.0.255.255
inet6 fe80::4876:c7ff:fecc:8a73 prefixlen 64 scopeid 0x20<link>
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7379403761 bytes 11148965732346 (11.1 TB)**
RX errors 0 dropped 168862 overruns 8554 frame 0
**TX packets 504974341 bytes 37356421339 (37.3 GB)**
TX errors 0 dropped 6 overruns 0 carrier 0 collisions 0

enp0s31f6: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 1251616 bytes 107128982 (107.1 MB)**
RX errors 0 dropped 83864 overruns 0 frame 0
**TX packets 1120861 bytes 238470225 (238.4 MB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0x92f00000-92f20000

enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7378152145 bytes 11148858603364 (11.1 TB)**
RX errors 0 dropped 0 overruns 8554 frame 0
**TX packets 503853480 bytes 37117951114 (37.1 GB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x92e00000-92e1ffff


Any idea what is wrong with this configuration? Thank you for your help.










share|improve this question














bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • What xmit_hash_policy did you set? According to the kernel documentation layer2 is the default which could explain the uneven distribution. Set this to layer3+4 and test again.

    – Thomas
    May 21 '18 at 15:27






  • 1





    What traffic had been disbalanced? Inbound or outbound from server?

    – Mikhail Khirgiy
    May 21 '18 at 16:17


















1















I upgraded to Ubuntu 18.04 and the new Netplan configuration, but my (2) network cards stopped sharing the load evenly. In my network configuration, I have many connections to many different servers; this configuration worked with previous versions of Ubuntu.



My configuration is below:



network:
ethernets:
enp0s31f6:
dhcp4: false
enp1s0:
dhcp4: false
version: 2
bonds:
bond0:
interfaces: [enp0s31f6,enp1s0]
addresses: [10.0.10.10/16]
gateway4: 10.0.0.1
mtu: 9000
nameservers:
addresses: [10.0.0.1]
search: [mydomain.example.com]
parameters:
mode: 802.3ad
lacp-rate: fast
mii-monitor-interval: 100


However, ifconfig shows uneven distribution of the network load:



bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 9000
inet 10.0.10.10 netmask 255.255.0.0 broadcast 10.0.255.255
inet6 fe80::4876:c7ff:fecc:8a73 prefixlen 64 scopeid 0x20<link>
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7379403761 bytes 11148965732346 (11.1 TB)**
RX errors 0 dropped 168862 overruns 8554 frame 0
**TX packets 504974341 bytes 37356421339 (37.3 GB)**
TX errors 0 dropped 6 overruns 0 carrier 0 collisions 0

enp0s31f6: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 1251616 bytes 107128982 (107.1 MB)**
RX errors 0 dropped 83864 overruns 0 frame 0
**TX packets 1120861 bytes 238470225 (238.4 MB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0x92f00000-92f20000

enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7378152145 bytes 11148858603364 (11.1 TB)**
RX errors 0 dropped 0 overruns 8554 frame 0
**TX packets 503853480 bytes 37117951114 (37.1 GB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x92e00000-92e1ffff


Any idea what is wrong with this configuration? Thank you for your help.










share|improve this question














bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • What xmit_hash_policy did you set? According to the kernel documentation layer2 is the default which could explain the uneven distribution. Set this to layer3+4 and test again.

    – Thomas
    May 21 '18 at 15:27






  • 1





    What traffic had been disbalanced? Inbound or outbound from server?

    – Mikhail Khirgiy
    May 21 '18 at 16:17














1












1








1


1






I upgraded to Ubuntu 18.04 and the new Netplan configuration, but my (2) network cards stopped sharing the load evenly. In my network configuration, I have many connections to many different servers; this configuration worked with previous versions of Ubuntu.



My configuration is below:



network:
ethernets:
enp0s31f6:
dhcp4: false
enp1s0:
dhcp4: false
version: 2
bonds:
bond0:
interfaces: [enp0s31f6,enp1s0]
addresses: [10.0.10.10/16]
gateway4: 10.0.0.1
mtu: 9000
nameservers:
addresses: [10.0.0.1]
search: [mydomain.example.com]
parameters:
mode: 802.3ad
lacp-rate: fast
mii-monitor-interval: 100


However, ifconfig shows uneven distribution of the network load:



bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 9000
inet 10.0.10.10 netmask 255.255.0.0 broadcast 10.0.255.255
inet6 fe80::4876:c7ff:fecc:8a73 prefixlen 64 scopeid 0x20<link>
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7379403761 bytes 11148965732346 (11.1 TB)**
RX errors 0 dropped 168862 overruns 8554 frame 0
**TX packets 504974341 bytes 37356421339 (37.3 GB)**
TX errors 0 dropped 6 overruns 0 carrier 0 collisions 0

enp0s31f6: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 1251616 bytes 107128982 (107.1 MB)**
RX errors 0 dropped 83864 overruns 0 frame 0
**TX packets 1120861 bytes 238470225 (238.4 MB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0x92f00000-92f20000

enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7378152145 bytes 11148858603364 (11.1 TB)**
RX errors 0 dropped 0 overruns 8554 frame 0
**TX packets 503853480 bytes 37117951114 (37.1 GB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x92e00000-92e1ffff


Any idea what is wrong with this configuration? Thank you for your help.










share|improve this question














I upgraded to Ubuntu 18.04 and the new Netplan configuration, but my (2) network cards stopped sharing the load evenly. In my network configuration, I have many connections to many different servers; this configuration worked with previous versions of Ubuntu.



My configuration is below:



network:
ethernets:
enp0s31f6:
dhcp4: false
enp1s0:
dhcp4: false
version: 2
bonds:
bond0:
interfaces: [enp0s31f6,enp1s0]
addresses: [10.0.10.10/16]
gateway4: 10.0.0.1
mtu: 9000
nameservers:
addresses: [10.0.0.1]
search: [mydomain.example.com]
parameters:
mode: 802.3ad
lacp-rate: fast
mii-monitor-interval: 100


However, ifconfig shows uneven distribution of the network load:



bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 9000
inet 10.0.10.10 netmask 255.255.0.0 broadcast 10.0.255.255
inet6 fe80::4876:c7ff:fecc:8a73 prefixlen 64 scopeid 0x20<link>
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7379403761 bytes 11148965732346 (11.1 TB)**
RX errors 0 dropped 168862 overruns 8554 frame 0
**TX packets 504974341 bytes 37356421339 (37.3 GB)**
TX errors 0 dropped 6 overruns 0 carrier 0 collisions 0

enp0s31f6: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 1251616 bytes 107128982 (107.1 MB)**
RX errors 0 dropped 83864 overruns 0 frame 0
**TX packets 1120861 bytes 238470225 (238.4 MB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0x92f00000-92f20000

enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 9000
ether 4a:76:c7:cc:8a:73 txqueuelen 1000 (Ethernet)
**RX packets 7378152145 bytes 11148858603364 (11.1 TB)**
RX errors 0 dropped 0 overruns 8554 frame 0
**TX packets 503853480 bytes 37117951114 (37.1 GB)**
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x92e00000-92e1ffff


Any idea what is wrong with this configuration? Thank you for your help.







ubuntu bonding lacp ubuntu-18.04






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 21 '18 at 15:12









ensnareensnare

93751733




93751733





bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 13 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • What xmit_hash_policy did you set? According to the kernel documentation layer2 is the default which could explain the uneven distribution. Set this to layer3+4 and test again.

    – Thomas
    May 21 '18 at 15:27






  • 1





    What traffic had been disbalanced? Inbound or outbound from server?

    – Mikhail Khirgiy
    May 21 '18 at 16:17



















  • What xmit_hash_policy did you set? According to the kernel documentation layer2 is the default which could explain the uneven distribution. Set this to layer3+4 and test again.

    – Thomas
    May 21 '18 at 15:27






  • 1





    What traffic had been disbalanced? Inbound or outbound from server?

    – Mikhail Khirgiy
    May 21 '18 at 16:17

















What xmit_hash_policy did you set? According to the kernel documentation layer2 is the default which could explain the uneven distribution. Set this to layer3+4 and test again.

– Thomas
May 21 '18 at 15:27





What xmit_hash_policy did you set? According to the kernel documentation layer2 is the default which could explain the uneven distribution. Set this to layer3+4 and test again.

– Thomas
May 21 '18 at 15:27




1




1





What traffic had been disbalanced? Inbound or outbound from server?

– Mikhail Khirgiy
May 21 '18 at 16:17





What traffic had been disbalanced? Inbound or outbound from server?

– Mikhail Khirgiy
May 21 '18 at 16:17










1 Answer
1






active

oldest

votes


















0














The following configuration work fine for me. Running Ubuntu 18.04 ppc64el. And BTW, if you want to use the REAL interface name instead of something like enp0s31f6, just do the following.



vi /etc/default/grub and add this:



GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"


Then rebuilt the boot loader



grub-mkconfig -o /boot/grub/grub.vfg


Reboot the system and You'll get the real nic name like eth0, eth1...
When it's done, edit this file and make sure it fit with your IP's !!!



vi /etc/netplan/01-netcfg.yaml

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
match:
macaddress: 'xx:xx:xx:xx:xx:xx'
wakeonlan: true
eth1:
match:
macaddress: 'xx:xx:xx:xx:xx:xx'
wakeonlan: true
bonds:
bond0:
interfaces: [eth0, eth1]
addresses: [192.168.0.10/24]
gateway4: 192.168.0.1
parameters:
mode: 802.3ad
lacp-rate: fast
mii-monitor-interval: 100
mtu: 9000
nameservers:
search: [home.lan],
addresses: [192.168.0.250]


Then, type netplan try to validate your configuration. If successful, run netplan apply and reboot.






share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "2"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f913106%2flacp-802-3ad-load-balancing-bonding-on-ubuntu-18-04-not-balancing-evenly%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The following configuration work fine for me. Running Ubuntu 18.04 ppc64el. And BTW, if you want to use the REAL interface name instead of something like enp0s31f6, just do the following.



    vi /etc/default/grub and add this:



    GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"


    Then rebuilt the boot loader



    grub-mkconfig -o /boot/grub/grub.vfg


    Reboot the system and You'll get the real nic name like eth0, eth1...
    When it's done, edit this file and make sure it fit with your IP's !!!



    vi /etc/netplan/01-netcfg.yaml

    # This file describes the network interfaces available on your system
    # For more information, see netplan(5).
    network:
    version: 2
    renderer: networkd
    ethernets:
    eth0:
    match:
    macaddress: 'xx:xx:xx:xx:xx:xx'
    wakeonlan: true
    eth1:
    match:
    macaddress: 'xx:xx:xx:xx:xx:xx'
    wakeonlan: true
    bonds:
    bond0:
    interfaces: [eth0, eth1]
    addresses: [192.168.0.10/24]
    gateway4: 192.168.0.1
    parameters:
    mode: 802.3ad
    lacp-rate: fast
    mii-monitor-interval: 100
    mtu: 9000
    nameservers:
    search: [home.lan],
    addresses: [192.168.0.250]


    Then, type netplan try to validate your configuration. If successful, run netplan apply and reboot.






    share|improve this answer






























      0














      The following configuration work fine for me. Running Ubuntu 18.04 ppc64el. And BTW, if you want to use the REAL interface name instead of something like enp0s31f6, just do the following.



      vi /etc/default/grub and add this:



      GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"


      Then rebuilt the boot loader



      grub-mkconfig -o /boot/grub/grub.vfg


      Reboot the system and You'll get the real nic name like eth0, eth1...
      When it's done, edit this file and make sure it fit with your IP's !!!



      vi /etc/netplan/01-netcfg.yaml

      # This file describes the network interfaces available on your system
      # For more information, see netplan(5).
      network:
      version: 2
      renderer: networkd
      ethernets:
      eth0:
      match:
      macaddress: 'xx:xx:xx:xx:xx:xx'
      wakeonlan: true
      eth1:
      match:
      macaddress: 'xx:xx:xx:xx:xx:xx'
      wakeonlan: true
      bonds:
      bond0:
      interfaces: [eth0, eth1]
      addresses: [192.168.0.10/24]
      gateway4: 192.168.0.1
      parameters:
      mode: 802.3ad
      lacp-rate: fast
      mii-monitor-interval: 100
      mtu: 9000
      nameservers:
      search: [home.lan],
      addresses: [192.168.0.250]


      Then, type netplan try to validate your configuration. If successful, run netplan apply and reboot.






      share|improve this answer




























        0












        0








        0







        The following configuration work fine for me. Running Ubuntu 18.04 ppc64el. And BTW, if you want to use the REAL interface name instead of something like enp0s31f6, just do the following.



        vi /etc/default/grub and add this:



        GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"


        Then rebuilt the boot loader



        grub-mkconfig -o /boot/grub/grub.vfg


        Reboot the system and You'll get the real nic name like eth0, eth1...
        When it's done, edit this file and make sure it fit with your IP's !!!



        vi /etc/netplan/01-netcfg.yaml

        # This file describes the network interfaces available on your system
        # For more information, see netplan(5).
        network:
        version: 2
        renderer: networkd
        ethernets:
        eth0:
        match:
        macaddress: 'xx:xx:xx:xx:xx:xx'
        wakeonlan: true
        eth1:
        match:
        macaddress: 'xx:xx:xx:xx:xx:xx'
        wakeonlan: true
        bonds:
        bond0:
        interfaces: [eth0, eth1]
        addresses: [192.168.0.10/24]
        gateway4: 192.168.0.1
        parameters:
        mode: 802.3ad
        lacp-rate: fast
        mii-monitor-interval: 100
        mtu: 9000
        nameservers:
        search: [home.lan],
        addresses: [192.168.0.250]


        Then, type netplan try to validate your configuration. If successful, run netplan apply and reboot.






        share|improve this answer















        The following configuration work fine for me. Running Ubuntu 18.04 ppc64el. And BTW, if you want to use the REAL interface name instead of something like enp0s31f6, just do the following.



        vi /etc/default/grub and add this:



        GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"


        Then rebuilt the boot loader



        grub-mkconfig -o /boot/grub/grub.vfg


        Reboot the system and You'll get the real nic name like eth0, eth1...
        When it's done, edit this file and make sure it fit with your IP's !!!



        vi /etc/netplan/01-netcfg.yaml

        # This file describes the network interfaces available on your system
        # For more information, see netplan(5).
        network:
        version: 2
        renderer: networkd
        ethernets:
        eth0:
        match:
        macaddress: 'xx:xx:xx:xx:xx:xx'
        wakeonlan: true
        eth1:
        match:
        macaddress: 'xx:xx:xx:xx:xx:xx'
        wakeonlan: true
        bonds:
        bond0:
        interfaces: [eth0, eth1]
        addresses: [192.168.0.10/24]
        gateway4: 192.168.0.1
        parameters:
        mode: 802.3ad
        lacp-rate: fast
        mii-monitor-interval: 100
        mtu: 9000
        nameservers:
        search: [home.lan],
        addresses: [192.168.0.250]


        Then, type netplan try to validate your configuration. If successful, run netplan apply and reboot.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 13 '18 at 23:17









        Sean Bright

        24515




        24515










        answered Aug 31 '18 at 19:11









        GuyPGuyP

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f913106%2flacp-802-3ad-load-balancing-bonding-on-ubuntu-18-04-not-balancing-evenly%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

            Список ссавців Італії Природоохоронні статуси | Список |...

            Українські прізвища Зміст Історичні відомості |...