similar to: [Advice] CentOS6 + KVM + bonding + bridging

Hi, Just thought I'd share some test results of mine in case anyone is interested. Basically the tests are siumulating what our product does with files - although the tests do it a lot quicker (not as many files though). The test is to create 1 million files (each containing the text of the file number) spread over a number of directories. The files are then removed in the same manner as

Hello, I just signed up to this mailing-list (note: my first mailing list at all), because I'm having some problems related to speex. Let me just introduce you to what I'm doing. I am writing a short (really short) paper about VoIP techniques, especially audio codecs for speech. I pointed out basic technologies behind audio codecs; vector quantization, lpc, long-term prediction and some

OK. Different mailing lists are set up differently. This list is unusual because your answers only go to the person who replied to you. So if you want the other people on the listserv to see your answer, you should make sure that Speex-dev at xiph.org<mailto:Speex-dev at xiph.org> is added to the TO: field of your outgoing message. Hopefully someone else will also attempt to answer your

Hi, The man page for nsd.conf claims the following syntax is valid: provide-xfr: 0/0 NOKEY However, this gives the error: /var/dnsx/nsd.zones:9: error: Bad ip4 address '0' The following does work: provide-xfr: 0.0.0.0/0 NOKEY So either the code is wrong, or the man page :) Paul

Our site has been experiencing problems with Samba causing kernel panics under heavy use. We are running Mandrake 7.0 and Samba 2.0.6. We are no longer using the distro included with Mandrake - we actually downloaded the 2.0.6 release and recompiled. Downloading from Samba shares causes no problems - and downloads are frequent and heavy - but uploading similar amounts of data leaves a catatonic

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

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you 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

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

Hi, I'm trying to configure a network bridge over a bonding without any success. Here is my configuration: ifcfg-eth0: DEVICE=eth0 HWADDR=00:1E:C9:E8:3F:E5 ONBOOT=yes USERCTL=no MASTER=bond0 SLAVE=yes ifcfg-eth1: DEVICE=eth1 HWADDR=00:1E:C9:E8:3F:E7 ONBOOT=yes USERCTL=no MASTER=bond0 SLAVE=yes ifcfg-bond0: DEVICE=bond0 ONBOOT=yes BRIDGE=br0 USERCTL=no ifcfg-bridge0: DEVICE=br0

Hi! I just upgraded a machine to 7.7.1908 and the default route is not being set on boot. This particular server has a bonded interface, and the corresponding configuration for the master is ( /etc/sysconfig/network-scripts/ifcfg-bond0): TYPE=Bond BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes NAME=bond0 DEVICE=bond0 ONBOOT=yes IPADDR=10.3.20.131 PREFIX=24

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, some months ago I ran into a hassle with following, quite simple config that works on CentOS 6 and CentOS 5 extremeley well, for years. However, I have problems getting it running on CentOS 7. ,-- bond0.100 -- brbond0.100 -> (VMs) eth0 (eno1 on C7) --. | |--- bond0 ----|--

Hello list, Please don''t shoot me. I know I''m doing something with bonding that bonding wasn''t made for. I just want to give it a try. I want a simple mechanism to have a failover on a 24Mbit line to a 2Mbit line in case the 24Mbit line goes down. Between A and B there are two lines: a 24Mbit and a 2Mbit. I use two OpenVPN tunnels with tap devices: +-- tap0 (A)---

HI All. I have a linux box connected to a switch network with 2 network interfaces, how would I able to ''trunk'' these 2 interfaces? options I can see are: - ethernet bonding - iproute2? - teql Which one are the best to use? I''m curretly having problem with ethernet bonding, my setup are as follow: ip add: 192.168.10.30/24 I do: # modprobe bonding # ip addr add

Hi guys, I am trying to get bonding work on a debian etch system. I searched already in the mailing list but unfortunately I couldnt find a proper solution. This is what i did so far. - Installed Debian Etch on my server - Installed the following packages for using Xen from the Debian repository: xen-hypervisor-3.0.3-1-i386-pae linux-image-2.6.18-5-xen-686 linux-image-2.6.18-5-xen-686 xen-tools

Dear All, Please ignore my previous mail I have using CentOS 4.4 Linux and Kernel Version is 2.6.9-42.EL I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server) I have configured Ethernet Channel Bonding in

Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of

Hi all, i have a xen 4.3 installation and would like to have a bridge bond szenario: *** eth0 eth1 | | bond0 | br0 | vif = [ ''bridge=br0,mac=xx:xx:xx:xx:xx:xx'' ] *** With the network script in debian wheezy *** /etc/network/interfaces auto bond0 iface bond0 inet manual slaves eth0 eth1

I four nodes setup to do active-backup bonding and the drivers loaded for the bonded network interfaces vary between tg3 and e100. All interfaces with the e100 driver loaded report errors much like what you see here: bonding: bond0: link status definitely down for interface eth2, disabling it e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex bonding: bond0: link status definitely up for

CentOS 6.2......... Why do the physical interfaces report (correctly) that they're negotiated at 1000Mb/s, but when I `cat /proc/net/bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: Supported ports: [