Get mac address from ip by arping

 arping -D 172.19.0.3 -I eth1

centos not found network card

kudzu -p | grep network
network.hwaddr: 00:22:64:8a:8d:3c
network.hwaddr: b4:99:ba:a8:97:a5
network.hwaddr: b4:99:ba:a8:97:a4


cd  /etc/sysconfig/network-scripts/
cp ifcfg-eth1 ifcfg-eth2
nano ifcfg-eth2

DEVICE=eth1
TYPE="Ethernet"
ONBOOT="yes"
USERCTL="no"
HWADDR="00:22:64:8a:8d:3c"
BOOTPROTO="static"
IPADDR="172.19.0.1"
NETMASK="255.255.0.0"
GATEWAY="110.164.189.17"

linux ___tmpxxxx network card not found

Network interfaces named ___tmpxxxx when HWADDR is not specified Article ID: 36572 - Created on: Nov 18, 2009 2:46 PM - Last Modified:  Dec  15, 2010 9:55 AM   Issue Ethernet  interface keeps changing into  '__tmpxxxx'.  When server is rebooted, interfaces are named as '__tmp' instead of ethx.  Invalid network interface name after reboot  Environment Red Hat Enterprise Linux  5.3  initscripts-8.45.25-1.el5-x86_64  Resolution To prevent this from occurring, the "HWADDR=" parameter should be used in  /etc/sysconfig/network-scripts/ifcfg-ethx as follows:  Ethernet Device DEVICE=ethx BOOTPROTO=static HWADDR=xx:xx:xx:xx ONBOOT=yes Root Cause  What happens is:  1. initrd loads modules. Generally not network ones, unless you've  specifically configured it to do so.   2. udev loads modules. It loads them in parallel. This means that  if you have multiple network drivers in the machine, they will race  against each other for device assignment.   3. when a network device is created, /lib/udev/rename_device is run  to attempt to coerce the device name into whatever device name is mapped  to that MAC address in the ifcfg files. Otherwise, you just get the order  they happen to initialize in (which can change from boot to boot)   4. rest of boot runs (during which you can do other things)  Due to the fact udev does not load modules sequentially (#2), you will get  non-deterministic ethernet device ordering if you have multiple network  drivers in the machine. It's inevitable. So, it is required to use HWADDR=  in the ifcfg files  to accomplish that mapping. You could also use udev  rules directly (with NAME=).