how to configure one new network interface

[sunzen]

Hi all

I'm sorry for asking for such a seemingly simple question, while i really got stuck in this matter.

I tried to install CentOS 7 on VMWare workstation, and changed configuration of network adapters
after CentOS was originally installed, specifically, I delete the original NAT network adapter, and
add two new network adapters respectively supported by BRIDGE and HOST-ONLY.

On CentOS 7, I can notice the two added devices, as following,
~~~~~~~~~~~~~~~~~~~~~
[root@localhost ~] lspci | grep Ethernet
02:01.0 Ethernet Controller: Advanced Micro Devices, Inc. ......
02:05.0 Ethernet Controller: Advanced Micro Devices, Inc. ......
~~~~~~~~~~~~~~~~~~~~~

But there are no corresponding management scripts in /etc/sysconfig/network-scripts/.

I tried to use net.ifnames=0 kernel parameters and udev persistent network rules, and add a script named as ifcfg-eth0,
but it still does not work.
Could anyone give me more useful information about configuring newly added network interfaces?

Thanks a lot.
Sunzen

[TrevorH]

Change the model of the cards that VMWare is emulating. The ones you have now are not supported. Try e1000 instead.

[sunzen]

hi TrevorH,

Thanks for your information.

I changed the network card model to e1000 by adding ethernet1.virtualDev="e1000" entry in VM configuration file,
and can see the difference:
~~~~~~~~~~~~~~~~~~~~~~~
root@localhost ~]# lspci | grep Ethernet
02:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
02:05.0 Ethernet controller: Advanced Micro Devices, Inc. [AMD] 79c970 [PCnet32 LANCE] (rev 10)
~~~~~~~~~~~~~~~~~~~~~~~

But it still doesn't work when ifup the first interface
~~~~~~~~~~~~~~~~~~~~~~~
[root@localhost ~]# ifup eth0
ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device eth0 does not seem to be present, delaying initialization.
~~~~~~~~~~~~~~~~~~~~~~~

Manually edited by me, ifcfg-eth0 is as following:
~~~~~~~~~~~~~~~~~~~~~~~
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="eth0"　　　　　　
HWADDR=00:50:56:3D:5B:F6
PEERDNS=yes
PEERROUTES=yes
IPADDR=192.168.200.158
NETMASK=255.255.255.0　　　
GATEWAY=192.168.200.10　
~~~~~~~~~~~~~~~~~~~~~~~

What's wrong with it?
If there is anything missing, please tell me.

Thanks
Sunzen

[sunzen]

hi TrevorH,

Sorry for troubling you with previous mail.

Now I can see the interface with "ip link"

root@localhost network-scripts]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 00:50:56:3d:5b:f6 brd ff:ff:ff:ff:ff:ff

The remaining is to configure the new ens33 interface.
I think i can do it now.

Many thanks to you.
Sunzen

[josephcolton]

I am also using VMWare, but I am using their ESXi solution. With it I build a virtual machine and set it to use the E1000 network adaptor. Then I convert the virtual machine into a template and use it to deploy multiple CentOS 7 machines (Actually, I am trying to have a class of students using CentOS in virtual machines). The problem is that for some reason, when I build virtual machines from the template, vSphere forgets that the interface was supposed to be the E1000 and converts it to "flexible" which translates to the "PCnet32 LANCE".

I figure, okay, fine, vSphere is broken, but surely CentOS will work. Unfortunately, the OS does not come with the drivers installed. They are not even built.

When I do a more full install with the kernel development stuff all there, I try to go in and build the kernel module. I go into the /usr/src/kernels/3.10.0-123.el7.x86_64/ directory and use "make menuconfig" to add AMD support and tell the kernel I want the PCnet32 and LANCE device drivers.

When I try to build the kernel, modules, anything, I get the following error:

make[1]: *** No rule to make target `/usr/src/kernels/3.10.0-123.el7.x86_64/arch/x86/syscalls/syscall_32.tbl', needed by `arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h'. Stop.
make: *** [archheaders] Error 2

I looked for the file and found this thread viewtopic.php?t=47978&p=203958 but that does not end in a solution.

All I want is to be able to get the networking working from within the virtual machine. I can have additional software if I can put it on a DVD, but I cannot get networking unless it is there. Any ideas what I can do to solve this problem?

Thanks.

[TrevorH]

Don't try to build a kernel for this, you'll be wasting your time. For a start you'll need to rebuild everytime there's a new kernel and the card will stop working after a reboot until you do. There've been 10 kernel updates since CentOS 7 was released about 6 months ago so on average your systems are going to stop working about every 3 weeks!

The problem is that Redhat intentionally removed support for those old 100Mb cards and I doubt if it's coming back. Better find a way to fix your VM template.