Update - after setting the MAC in ifcfg-enp5s1 to what is shown in
ifconfig -a, I have success:
[root@localhost network-scripts]# ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.222.152 netmask 255.255.255.0 broadcast
192.168.222.255
inet6 fe80::e2cb:4eff:fe1f:35b2 prefixlen 64 scopeid 0x20<link>
ether e0:cb:4e:1f:35:b2 txqueuelen 1000 (Ethernet)
RX packets 2994 bytes 252507 (246.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1211 bytes 251506 (245.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp5s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.98.151 netmask 255.255.255.0 broadcast
192.168.98.255
inet6 fe80::2e0:4cff:feee:566b prefixlen 64 scopeid 0x20<link>
ether 00:e0:4c:ee:56:6b txqueuelen 1000 (Ethernet)
RX packets 125 bytes 19661 (19.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 33 bytes 3714 (3.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Howard
On 11/01/2015 12:43 PM, Howard White wrote:
Running the risk of changing more than one thing at a time. Previous
mung I moved the Intel NIC to a different PCI slot and it subsequently
did not appear as an Ethernet device in lspci. So I replaced it with a
RealTek NIC (MAC DB0303066320) in the slot that failed and now I have
entries:
[root@localhost ~]# lspci | grep Ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
05:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
[root@localhost ~]# ls -l /sys/class/net
total 0
lrwxrwxrwx. 1 root root 0 Nov 1 12:23 enp2s0 ->
../../devices/pci0000:00/0000:00:1c.5/0000:02:00.0/net/enp2s0
lrwxrwxrwx. 1 root root 0 Nov 1 12:23 enp5s1 ->
../../devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/enp5s1
lrwxrwxrwx. 1 root root 0 Nov 1 12:23 lo -> ../../devices/virtual/net/lo
I whacked up a quick file
[root@localhost network-scripts]# cat ifcfg-eth1
DEVICE=eth1
# HWADDR=00:60:B0:6D:61:DD
HWADDR=DB:03:03:06:63:20
ONBOOT=yes
TYPE=ethernet
NETMASK=255.255.255.0
BOOTPROTO=dhcp
and attempted an ifup eth1
[root@localhost network-scripts]# ifup eth1
Error: no device found for connection 'System eth1'.
OH, NOW THIS IS INTERESTING (pardon the shout):
[root@localhost network-scripts]# dmesg | grep -e eth
[ 0.745465] r8169 0000:02:00.0 eth0: RTL8168c/8111c at
0xffffc90000c78000, e0:cb:4e:1f:35:b2, XID 1c4000c0 IRQ 44
[ 0.745467] r8169 0000:02:00.0 eth0: jumbo features [frames: 6128
bytes, tx checksumming: ko]
[ 0.878406] systemd-udevd[205]: renamed network interface eth0 to enp2s0
[ 7.746723] 8139too 0000:05:01.0 eth0: RealTek RTL8139 at
0xffffc90010e4cc00, 00:e0:4c:ee:56:6b, IRQ 17
[ 7.887229] systemd-udevd[375]: renamed network interface eth0 to enp5s1
soooooo
[root@localhost network-scripts]# mv ifcfg-eth1 ifcfg-enp5s1
[root@localhost network-scripts]# vi ifcfg-enp5s1
[root@localhost network-scripts]# ifdown enp5s1
Device 'enp5s1' successfully disconnected.
[root@localhost network-scripts]# ifup enp5s1
Error: no device found for connection 'System enp5s1'.
But this is new:
[root@localhost network-scripts]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether e0:cb:4e:1f:35:b2 brd ff:ff:ff:ff:ff:ff
inet 192.168.222.152/24 brd 192.168.222.255 scope global dynamic
enp2s0
valid_lft 6066sec preferred_lft 6066sec
inet6 fe80::e2cb:4eff:fe1f:35b2/64 scope link
valid_lft forever preferred_lft forever
3: enp5s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 1000
link/ether 00:e0:4c:ee:56:6b brd ff:ff:ff:ff:ff:ff
Howard
On 11/01/2015 12:06 PM, Wesley Duffee-Braun wrote:
Hmmm..... is anything in 'ls -l /sys/class/net ' that softlinks to
/sys/devices/pci* ?
I'm thinking you'll see an entry for lo and enp2s0, but not the missing
NIC (unless we get lucky). Anyway - wherever the enp2s0 goes, follow
that to see what else is in that directory - probably something like
/sys/devices/pci0000\:00/0000\:00\:01.0/
For example, my two NICs
$ lspci | grep Ethernet
01:00.0 Ethernet controller: Intel Corporation 82580 Gigabit Network
Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82580 Gigabit Network
Connection (rev 01)
are in /sys/devices/pci0000\:00/0000\:00\:01.0/0000:01:00.0 and
0000:01:00.1 so you hopefully have entries akin to 0000:02:00.0 and
0000:05:00.0 - anything in there, specifically in (hopefully a) net
directory?
Also, anything from dmesg | grep -e eth ?
Trying to find out if maybe we just need to get the eth number of the
card and do ifconfig ethNUMBER up before network-manager starts.
--
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to nlug-talk@googlegroups.com
To unsubscribe from this group, send email to
nlug-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
---
You received this message because you are subscribed to the Google Groups "NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nlug-talk+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
