Sponsored Content
Full Discussion: IP Bonding
Operating Systems Linux Red Hat IP Bonding Post 302605999 by h@foorsa.biz on Friday 9th of March 2012 10:19:17 AM
Old 03-09-2012
You mean
Link aggregation or trunking or link bundling or Ethernet/network/NIC bonding or NIC teaming.
But not IP Bonding as far as I know.

Link Aggregation provides several benefits: Increased bandwidth, load balancing, and allows you to create redundant Ethernet links. If a link in your Ethernet channel goes down, the switches, routers, or servers you have configured to use LA will automatically fail over to the links that are still up and remain connected.
How you can do it then have a look here
 

10 More Discussions You Might Find Interesting

1. IP Networking

Bonding Internet Connections

I’m familiar with load balancing.. but Is it possible to actually bond multiple DSL lines together? I hear of ways to bond using MLPPP but that requires support from an ISP. Is there a way to actually bond without support from my ISP, or use say a cable modem and a DSL line together for faster... (0 Replies)
Discussion started by: harley313
0 Replies

2. IP Networking

Bonding of IP tunnels

Hello. Our Company is spreaded over Germany. There are main offices an branch offices. These offices are mostly connecte via multiple sdsl. We build a IPSEC VPN Infrastructure using Aastaro Security Gateways appliances. It seemed that only one VPN Connetion between to offices could be... (0 Replies)
Discussion started by: mschwadorf
0 Replies

3. Linux

ethernet bonding

I need to enable Ethernet Bonding on three systems, connected together via switch. What I tried ended up with failure, slaves cannot be detected n added to bon0. Here's what I did: created file /etc/modprobe.d/bonding.d and added the following to it: alias bond0 bonding options bonding... (2 Replies)
Discussion started by: dr_mabuse
2 Replies

4. Red Hat

RHEL 5.5 NIC Bonding

I am new to linux. I have a falconstor CDP installation which runs on RHEL 5.5 (Tikanga). There is a vendor option to bond nics in either 802.3ad or round robin, I choose 802.3ad. The server is connected to a Cisco 3750 switch. The problem is dropped packets and eth03 wont come up in the PO... (0 Replies)
Discussion started by: tjcooper
0 Replies

5. Red Hat

Bonding a Bond with LACP

Does anyone know if it's possible to bond two bonds together? My situation is I have two older Cisco switches that cannot carry a LACP (bond level 4) aggregated between them, but separate aggregates can be setup on the switches themselves. In order to have redundancy of two switches I would... (0 Replies)
Discussion started by: christr
0 Replies

6. Red Hat

BONDING with Flapping issue!

Hi team, I'm running into a problem configuring bonding on an CentOS 64bit on DELL Server. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes,... (3 Replies)
Discussion started by: leo_ultra_leo
3 Replies

7. IP Networking

Is bond0 ready and a bonding interface? - 4G Bonding Router Problems (RPI)

HI all, First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place. I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
Discussion started by: elliottlc
0 Replies

8. Red Hat

How to change bonding configuration in Linux 5.9?

I have 2 ethernet port in my linux (Red hat 5.9) machine.The 2 ethernet ports (eth0 and eth1)are bonded and are making one single ethernet port namely bond0. I have adaptive load share option selected.Now in this condition, if my eth0 port disconnected due to some failure, then will eth1 take the... (0 Replies)
Discussion started by: Anjan Ganguly
0 Replies

9. Red Hat

Network Bonding Issue

I have one production system where my customized application runs.The applications require seamless network connectivity with different machines connected in LAN and WAN. As these applications are very critical, it is very much required to have a seamless network activity.The applications are... (4 Replies)
Discussion started by: Anjan Ganguly
4 Replies

10. Red Hat

Network bonding

Dear All , Very recently we have configured Network bonding in our Linux Server Redhat Linux 5.x. After configuring , we restarted the network services , the link was down after that , we could not login in to the Server. So after that , we logged in to console and tried to... (2 Replies)
Discussion started by: jegaraman
2 Replies
NETDEVICE(7)						     Linux Programmer's Manual						      NETDEVICE(7)

NAME
netdevice - low-level access to Linux network devices SYNOPSIS
#include <sys/ioctl.h> #include <net/if.h> DESCRIPTION
This man page describes the sockets interface which is used to configure network devices. Linux supports some standard ioctls to configure network devices. They can be used on any socket's file descriptor regardless of the fam- ily or type. Most of them pass an ifreq structure: struct ifreq { char ifr_name[IFNAMSIZ]; /* Interface name */ union { struct sockaddr ifr_addr; struct sockaddr ifr_dstaddr; struct sockaddr ifr_broadaddr; struct sockaddr ifr_netmask; struct sockaddr ifr_hwaddr; short ifr_flags; int ifr_ifindex; int ifr_metric; int ifr_mtu; struct ifmap ifr_map; char ifr_slave[IFNAMSIZ]; char ifr_newname[IFNAMSIZ]; char *ifr_data; }; }; Normally, the user specifies which device to affect by setting ifr_name to the name of the interface. All other members of the structure may share memory. Ioctls If an ioctl is marked as privileged, then using it requires an effective user ID of 0 or the CAP_NET_ADMIN capability. If this is not the case, EPERM will be returned. SIOCGIFNAME Given the ifr_ifindex, return the name of the interface in ifr_name. This is the only ioctl which returns its result in ifr_name. SIOCGIFINDEX Retrieve the interface index of the interface into ifr_ifindex. SIOCGIFFLAGS, SIOCSIFFLAGS Get or set the active flag word of the device. ifr_flags contains a bit mask of the following values: Device flags IFF_UP Interface is running. IFF_BROADCAST Valid broadcast address set. IFF_DEBUG Internal debugging flag. IFF_LOOPBACK Interface is a loopback interface. IFF_POINTOPOINT Interface is a point-to-point link. IFF_RUNNING Resources allocated. IFF_NOARP No arp protocol, L2 destination address not set. IFF_PROMISC Interface is in promiscuous mode. IFF_NOTRAILERS Avoid use of trailers. IFF_ALLMULTI Receive all multicast packets. IFF_MASTER Master of a load balancing bundle. IFF_SLAVE Slave of a load balancing bundle. IFF_MULTICAST Supports multicast IFF_PORTSEL Is able to select media type via ifmap. IFF_AUTOMEDIA Auto media selection active. IFF_DYNAMIC The addresses are lost when the interface goes down. IFF_LOWER_UP Driver signals L1 up (since Linux 2.6.17) IFF_DORMANT Driver signals dormant (since Linux 2.6.17) IFF_ECHO Echo sent packets (since Linux 2.6.25) Setting the active flag word is a privileged operation, but any process may read it. SIOCGIFPFLAGS, SIOCSIFPFLAGS Get or set extended (private) flags for the device. ifr_flags contains a bit mask of the following values: Private flags IFF_802_1Q_VLAN Interface is 802.1Q VLAN device. IFF_EBRIDGE Interface is Ethernet bridging device. IFF_SLAVE_INACTIVE Interface is inactive bonding slave. IFF_MASTER_8023AD Interface is 802.3ad bonding master. IFF_MASTER_ALB Interface is balanced-alb bonding master. IFF_BONDING Interface is a bonding master or slave. IFF_SLAVE_NEEDARP Interface needs ARPs for validation. IFF_ISATAP Interface is RFC4214 ISATAP interface. Setting the extended (private) interface flags is a privileged operation. SIOCGIFADDR, SIOCSIFADDR Get or set the address of the device using ifr_addr. Setting the interface address is a privileged operation. For compatibility, only AF_INET addresses are accepted or returned. SIOCGIFDSTADDR, SIOCSIFDSTADDR Get or set the destination address of a point-to-point device using ifr_dstaddr. For compatibility, only AF_INET addresses are accepted or returned. Setting the destination address is a privileged operation. SIOCGIFBRDADDR, SIOCSIFBRDADDR Get or set the broadcast address for a device using ifr_brdaddr. For compatibility, only AF_INET addresses are accepted or returned. Setting the broadcast address is a privileged operation. SIOCGIFNETMASK, SIOCSIFNETMASK Get or set the network mask for a device using ifr_netmask. For compatibility, only AF_INET addresses are accepted or returned. Setting the network mask is a privileged operation. SIOCGIFMETRIC, SIOCSIFMETRIC Get or set the metric of the device using ifr_metric. This is currently not implemented; it sets ifr_metric to 0 if you attempt to read it and returns EOPNOTSUPP if you attempt to set it. SIOCGIFMTU, SIOCSIFMTU Get or set the MTU (Maximum Transfer Unit) of a device using ifr_mtu. Setting the MTU is a privileged operation. Setting the MTU to too small values may cause kernel crashes. SIOCGIFHWADDR, SIOCSIFHWADDR Get or set the hardware address of a device using ifr_hwaddr. The hardware address is specified in a struct sockaddr. sa_family contains the ARPHRD_* device type, sa_data the L2 hardware address starting from byte 0. Setting the hardware address is a privi- leged operation. SIOCSIFHWBROADCAST Set the hardware broadcast address of a device from ifr_hwaddr. This is a privileged operation. SIOCGIFMAP, SIOCSIFMAP Get or set the interface's hardware parameters using ifr_map. Setting the parameters is a privileged operation. struct ifmap { unsigned long mem_start; unsigned long mem_end; unsigned short base_addr; unsigned char irq; unsigned char dma; unsigned char port; }; The interpretation of the ifmap structure depends on the device driver and the architecture. SIOCADDMULTI, SIOCDELMULTI Add an address to or delete an address from the device's link layer multicast filters using ifr_hwaddr. These are privileged opera- tions. See also packet(7) for an alternative. SIOCGIFTXQLEN, SIOCSIFTXQLEN Get or set the transmit queue length of a device using ifr_qlen. Setting the transmit queue length is a privileged operation. SIOCSIFNAME Changes the name of the interface specified in ifr_name to ifr_newname. This is a privileged operation. It is allowed only when the interface is not up. SIOCGIFCONF Return a list of interface (transport layer) addresses. This currently means only addresses of the AF_INET (IPv4) family for com- patibility. Unlike the others, this ioctl passes an ifconf structure: struct ifconf { int ifc_len; /* size of buffer */ union { char *ifc_buf; /* buffer address */ struct ifreq *ifc_req; /* array of structures */ }; }; If ifc_req is NULL, SIOCGIFCONF returns the necessary buffer size in bytes for receiving all available addresses in ifc_len. Other- wise, ifc_req contains a pointer to an array of ifreq structures to be filled with all currently active L3 interface addresses. ifc_len contains the size of the array in bytes. Within each ifreq structure, ifr_name will receive the interface name, and ifr_addr the address. The actual number of bytes transferred is returned in ifc_len. If the size specified by ifc_len is insufficient to store all the addresses, the kernel will skip the exceeding ones and return suc- cess. There is no reliable way of detecting this condition once it has occurred. It is therefore recommended to either determine the necessary buffer size beforehand by calling SIOCGIFCONF with ifc_req set to NULL, or to retry the call with a bigger buffer whenever ifc_len upon return differs by less than sizeof(struct ifreq) from its original value. If an error occurs accessing the ifconf or ifreq structures, EFAULT will be returned. Most protocols support their own ioctls to configure protocol-specific interface options. See the protocol man pages for a description. For configuring IP addresses, see ip(7). In addition, some devices support private ioctls. These are not described here. NOTES
Strictly speaking, SIOCGIFCONF and the other ioctls that accept or return only AF_INET socket addresses, are IP-specific and belong in ip(7). The names of interfaces with no addresses or that don't have the IFF_RUNNING flag set can be found via /proc/net/dev. Local IPv6 IP addresses can be found via /proc/net or via rtnetlink(7). BUGS
glibc 2.1 is missing the ifr_newname macro in <net/if.h>. Add the following to your program as a workaround: #ifndef ifr_newname #define ifr_newname ifr_ifru.ifru_slave #endif SEE ALSO
proc(5), capabilities(7), ip(7), rtnetlink(7) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 NETDEVICE(7)
All times are GMT -4. The time now is 10:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy