similar to: centso 5 modifying my ifcfg-eth[x] files

I am using centos 5 x86_64 AMD64 X2 4200+. I am current on yum update. My machine has two ethernet cards. e1000 (eth0) and forcedeth (eth1) [root at fsdsigns2 ~]# more /etc/modprobe.conf alias eth0 e1000 alias eth1 forcedeth sometimes on boot the forcedeth driver thinks it is eth0: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

centos 5 had modprobe.conf entries for eth0 and if present eth1. something like: alias eth0 forcedeth alias eth1 e1000e For the new centos 6 (I have the rhel 6 client installed on my laptop) the modprobe.conf file is gone. Which is fine. I understand files can be created in /etc/modprobe.d and server the same purpose. My question is I dont see (doing a grep) any eth0 alias's in the files in

I need to allocate public IP address to two guest os. I have only 2 network card Interface on server. say eth0 and eth1. I set eth1 a public IP address. so it should in # vi /etc/sysconfig/ifcfg-eth1 DEVICE=eth1 BOOTPROTO=static HWADDR=00:1a:4d:83:ad:00 BROADCAST=202.127.29.0 IPADDR=202.127.29.5 NETMASK=255.255.255.0 NETWORK=202.127.29.0 ONBOOT=yes TYPE=Ethernet Question 1: do I have to

What is happening in centos 5 with network config files??? I have a machine with 2 network cards. ifcfg-eth1 keeps changing to DHCP. All my static setup is gone. Why is it doing this? How can I stop it? I run "netconfig -d eth1" and re-setup my static information. I reboot and now I am back to DHCP. I have a gigabyte motherboard, nvidia chipset. forcedeth driver. eth0 is e1000.

When I was working on this last time (with the r8169 driver), someone on this list provided the following script which is what "fixed" the issue at the time by creating a new 70-persistent-net.rules file with the devices enumerated in order. However, this no longer works now. echo "[KICKSTART] Binding eth interfaces to the expected MAC address in UDEV" echo "## Created by

Hello, I created a CentOS 5.0 x86_64 guest under Debian Etch with Xen 3.0.3 and it boots fine except for one re-occuring problem - whenever it boots the /etc/sysconfig/network-scripts/ifcfg-eth0 script gets renamed to .bak and doesn''t configure the ethernet device. Here is the content of this file: TYPE=Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.0.247

I am new to CentOS (coming from Fedora) and I really like it! I am having difficulty getting one of my machines to boot and assign the same designation of eth0 and eth1 to the same nics consistantly. I have an MSI motherboard with 2 nics on the board. Strangely enough both nics report the same MAC address. This is not an issue since I use the computer to route between two different subnets so

So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After

All, I've got a machine running CentOS 5.3 and this machine has got 2 - built-in 1 Gig NICs and a expansion card with 4 - 100 Meg NICs. For whatever reason at install time, it made the expansion card eth0 through eth3 and the internal ports eth4 and eth5. And by default the 'machine' is known on the network by the eth0 NIC, so my throughput is limited to 100 Mb. How can I force

I have two servers with identical hardware ... TYAN i3210w system boards with dual intel gigabit interfaces, and a PCI intel gigabit nic. I'm running Centos 5.4, x86_64, 2.6.18-164.6.1.el5 Every other time I reboot, the nics initialize in a different order. anaconda had setup /etc/modprobe.conf with alias lines for the cards: alias eth0 e1000 alias eth1 e1000e alias eth2 e1000e However,

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

Anyone else seen this eth-device and what brings it up? [root at oh1mrr etc]# ifconfig __tmp1192348344 Link encap:Ethernet HWaddr 52:54:AB:DD:2E:D1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2094689 errors:0 dropped:0 overruns:0 frame:0 TX packets:1645734 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX

Me again. The ASUS P5N32-SLI motherboard in my new machine has dual NICs but CentOS has only detected one of them. I've tried rebooting with the network plugged in only to the second one, but kudzu still doesn't find it. Any suggestions?

I am attempting to put 3 network cards in one box, running centos 64 5.4 network cards are forcedeth (motherboard), e1000e and r8169. I have ifcfg-eth0, ifcfg-eth1 and ifcfg-eth2 all configured up. All looks fine. eth0 is my internal network (forcedeth) eth1 is Cable modem eth2 is T1 data Once I connect the three networks and try to ping something all I can ping is internal network machines.

I have a server located remotely running CentOS 5.x. I need to have two IP's on the same interface. So I have this: /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none BROADCAST=69.x.x.199 HWADDR=00:x:x:x:c6:10 IPADDR=69.x.x.194 NETMASK=255.255.255.248 NETWORK=69.x.x.192 ONBOOT=yes GATEWAY=69.x.x.193 TYPE=Ethernet So I added this:

Hi all Can someone explain me this: ifcfg-eth0-range1: ONBOOT="yes" IPADDR_START="192.168.1.48" IPADDR_END="192.168.1.55" CLONENUM_START="1" Why Bcast is 192.168.1.51 and why Mask is 255.255.255.252 ? OS: Centos 6.3/64bit Thanks Levi # ifconfig eth0:1 Link encap:Ethernet HWaddr 00:9C:02:99:FA:00 inet addr:192.168.1.48

Hi, I'm wondering about the impact of using both dom0 and domU's on a server at the same time. I'm worried about the performance impact of running a Mysql server in a domU and now I'm thinking about moving the Mysql part of a LAMP setup into dom0 and running a few Apache guests as domUs. Since the Apaches will serve mostly from an NFS share they won't have much impact on