search for: bond0

Hi! Is it HTB fully compatible with BOND interface? I have this setup (mode= fault tolerance) : BOND0 -> ETH0 + ETH1 BOND1 -> ETH2 + ETH3 ( http://www.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/Documentation/networking/bonding.txt ) HTB work very well with Class over BOND0. If I add Class for BOND1 it generate balance errors. Also with HTB.init (http://sourceforge.net/projects/ht...

...ll the NIC adapters on all of my R710's running CentOS 5.5. Here is an sample of the error messages: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. bonding: bond0: setting mode to active-backup (1). bonding: bond0: Setting MII monitoring interval to 500. ADDRCONF(NETDEV_UP): bond0: link is not ready bonding: bond0: Adding slave eth0. bnx2: eth0: using MSIX bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: enslaving eth0 as a backup interface with a down l...

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the installation starts off the creation of bond0 and all VLANs on bond0 go without issue. Jumpi...

...have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth0 Dec 17 08:34:21 3_10 kernel: bonding: bond0: making interface eth1 the new active one. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active int...

...es a new bond with the same name but not connected to any device. Two bonds with the same name is confusing for my other monitoring scripts. I'm wondering why a second bond is created? Is it a bug in NetworkManger? #Create a bond with two slaves nmcli con add autoconnect no type bond con-name bond0 ifname bond0 nmcli con mod bond0 ipv6.method ignore ipv4.method manual ipv4.addresses ${BOND_IP}/${BOND_CIDR} ${BOND_GW} ${BOND_DNS} ${BOND_DNS_SEARCH} ipv4.never-default no ipv4.ignore-auto-dns no nmcli con add autoconnect no type bond-slave con-name bond-slave-eth0 ifname eth0 master bond0 nmcli...

...o any device. Two bonds with the same name is confusing for >> my other monitoring scripts. >> I'm wondering why a second bond is created? Is it a bug in NetworkManger? >> >> >> #Create a bond with two slaves >> nmcli con add autoconnect no type bond con-name bond0 ifname bond0 >> nmcli con mod bond0 ipv6.method ignore ipv4.method manual ipv4.addresses >> ${BOND_IP}/${BOND_CIDR} ${BOND_GW} ${BOND_DNS} ${BOND_DNS_SEARCH} >> ipv4.never-default no ipv4.ignore-auto-dns no >> nmcli con add autoconnect no type bond-slave con-name bond-slave...

...sts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while others are not. When restarting the network service via /etc/init.d/network, nothing is pingable. Here are my configs; ifcfg-bond0 DEVICE=bond0 USERCTL=no BOOTPROTO=none ONBOOT=yes IPADDR=10.0.0.10 NETMASK=255.255.0.0 NETWORK=10.0.0.0 TYPE=Unknown IPV6INIT=no ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no ifcfg-eth1 DEVICE=eth1 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no /...

Hi, I've using linux bonding in active-backup mode to combine two pairs of GigE NICs (eth0/eth1, eth2/eth3) into two logical bonds (bond0/bond1). All is working fine. However, I would like to specify a primary interface for each bond. This means I need to specify different options to the bonding module for each bond. I have tried every conceivable incantation of options and cannot get the kernel to recognize the second set of options...

...m repo via yum and ctdb-packages. After restarting both nodes everything was fine, we could access files on the cluster. On monday I noticed that the nodes didn't had their initial adresses: Node 1: hostname dscln01, public IP 10.0.0.41/8, now 10.0.0.42/8 /etc/sysconfig/network-scripts/ifcfg-bond0: DEVICE=bond0 BOOTPROTO=none IPADDR=10.0.0.41 NETWORK=10.0.0.0 BROADCAST=10.0.0.255 NETMASK=255.0.0.0 ONBOOT=yes USERCTL=no Node 2: hostname dscln02, public IP 10.0.0.42/8, now 10.0.0.41/8 /etc/sysconfig/network-scripts/ifcfg-bond0: DEVICE=bond0 BOOTPROTO=none IPADDR=10.0.0.42 NETWORK=10.0.0.0...

...nothing in messages that looks wrong? Anyone have an idea? kernel: Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008) kernel: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link fail kernel: bonding: bond0: setting mode to 802.3ad (4). kernel: bonding: bond0: Setting MII monitoring interval to 500. kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready kernel: bonding: bond0: Adding slave eth0. kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link. kernel: bonding: bond0: Addin...

Hi, We have a Dell server with 4 Ethernet interface. I would to aggregate them in a bond. Everything work but the default gateway doesn?t work on the ? bond0 ? interface and I have no links. My configuration: - CentOS 7: :/etc/sysconfig/network-scripts# uname -a Linux nas-mtd2 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - NetworkManager disabled: :/etc/sysconfig/network-scripts# systemctl list-unit-files...

Hello, I have a server with 4 NICS running CentOS 5.2. I have bonded the interfaces together such that 'bond0' consists of eth0-3. This is not a problem, and works fine. However, I now need to create a virtual interface. In a non-bonded server I would just create something like eth0:1, but with a bonded interface I am a bit confused. I have created bond0:1 simple by copying the /etc/sysconfig/network-...

...a website. here is the basic configuration I am looking at, with some things not added like hwaddress and a few tweaks (zeroconf?) am I even close? I admit I have never done this and have no mentor other than this exceptional mailing list. ============================ /etc/modprobe.conf alias bond0 bonding options bond0 mode=balance-alb miimon=100 ============================ ============================ bond0 DEVICE=bond0 BOOTPROTO=none BRIDGE=br0 ONBOOT=yes BONDING_OPTS="mode=1 miimon=100 primary=eth0" ============================ ============================ br0 DEVICE=br0 TYPE...

I've just setup nic bonding on our server (DL585-G7 running Centos 5.5 x86_64) as detailed on the wiki: http://wiki.centos.org/TipsAndTricks/BondingInterfaces and all seems fine but from other "howto's" I've seen on the web, they're should be a /proc/net/bond0/info As far as I can see, I don't have one and I'm not sure if it should be there or its absence is a sign I've done something wrong. I found /proc/net/dev_snmp6/bond0 but is the same? Any ideas? Thanx, Russell Smithies ==============================================================...

Hi, This may sound crazy but I will go ahead anyway. Here's my scenario: ifconfig bond0 10.10.10.1 netmask 255.0.0.0 ifenslave bond0 eth0 ifenslave bond0 eth1 brctl addbr stp0 brctl addif stp0 bond0 brctl stp stp0 on Is this a valid scenario? I am trying to bond two interfaces and run STP over the bonded interface..The problem I am trying to solve is to run STP over aggregated links...

...f9c2-141b-4a99-ab1e-328551aae612" DEVICE="em1" ONBOOT="yes" IPADDR="192.168.56.50" PREFIX="24" GATEWAY="192.168.56.1" DNS1="192.168.126.10" DNS2="192.168.220.10" IPV6_PRIVACY="no" NM_CONTROLLED=no as for the ifcfg-bond0 (the configuration file for the NIC bond, which is bond0): DEVICE=bond0 NAME=bond0 TYPE=Bond ONBOOT=yes BOOTPROTO=none IPADDR=192.168.56.70 PREFIX=24 BONDING_MASTER=yes BONDING_OPT="mode=1 miimon=100" TYPE=Ethernet and the ifcfg-slave1 configuration file, which is the first slave port f...

...xperiencing the most perplexing problem with iptables on CentOS 5.2. I'm hoping someone can point out what I must be missing here. I have memcached set up on several nodes on an internal network. I have the following rules set up to allow traffic between memcached nodes: IPTABLES -A INPUT -i bond0 -p tcp -m tcp -s 192.168.1.0/24 -d 192.168.1.0/24 --dport 11211 -j ACCEPT IPTABLES -A FORWARD -i bond0 -p tcp -m tcp -s 192.168.1.0/24 -d 192.168.1.0/24 --dport 11211 -j ACCEPT IPTABLES -A OUTPUT -o bond0 -p tcp -m tcp -s 192.168.1.0/24 -d 192.168.1.0/24 --dport 11211 -j ACCEPT IPTABL...

Hi Neil, Thanks for your comments. What's the purpose of creating spurious ?bond0?? It's confusing. Is it anywhere documented? Every time I restart NetworkManager it creates another bond0! Joe On Thu, Jul 7, 2016 at 5:44 PM, Digimer <lists at alteeve.ca> wrote: > On 07/07/16 05:36 PM, Digimer wrote: > > On 07/07/16 05:21 PM, Joe Smithian wrote: > >&gt...

I'm running into a situation where a bogus bonded interface named "bond0" is being created, in addition to the desired "bond2" interface. Can anyone confirm this? Anyone know why it's happening or what I do to get rid of it? I wanted to start my numbering scheme at 2 instead of 0, which I didn't think would be a problem. As you can see, I...

Has anyone successfully created a bonded interface (bond0) with say two nics AND also then aliased that interface to get bond0 and bond0:1 (for an alias ip) I just want to know if it's possible and reliable Thanks -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada