Netzwerkkarte wird nicht (richtig) erkannt

B

bforpc

Renowned Member
Nov 26, 2013
151
5
83
Hamburg
Ich habe im aktuellen Proxmox 3 Netzwerkkarten. 2 onboard, eine PCI-E. Diese PCI-E kann nicht genutzt werden.
Code: 
 lspci -nnk | grep -i Ethernet -A2
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
        Subsystem: ASRock Incorporation Device [1849:15b8]
        Kernel driver in use: e1000e
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
        Subsystem: TP-LINK Technologies Co., Ltd. TG-3468 Gigabit PCI Express Network Adapter [7470:3468]
        Kernel driver in use: vfio-pci
--
07:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
        Subsystem: ASRock Incorporation Device [1849:1539]
        Kernel driver in use: igb

Erkannt werden 3 Netzwerkkarten.

Code: 
ifconfig -a,  hier existiert sie nicht:
eth1      Link encap:Ethernet  HWaddr d0:50:99:a3:33:62
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14574467 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35857614 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1110424013 (1.0 GiB)  TX bytes:53092097684 (49.4 GiB)

eth2      Link encap:Ethernet  HWaddr d0:50:99:a3:33:60
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5075902 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2079886 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5718676991 (5.3 GiB)  TX bytes:219544032 (209.3 MiB)
          Interrupt:16 Memory:df600000-df620000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:182271 errors:0 dropped:0 overruns:0 frame:0
          TX packets:182271 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:74306540 (70.8 MiB)  TX bytes:74306540 (70.8 MiB)

tap101i0  Link encap:Ethernet  HWaddr 12:a4:de:3d:bd:15
       ...

tap101i1  Link encap:Ethernet  HWaddr fa:19:04:5d:90:6c
       ...

tap101i2  Link encap:Ethernet  HWaddr 22:1d:38:b0:dc:4b
       ...

tap101i3  Link encap:Ethernet  HWaddr 86:6e:15:3f:79:99
       ...

tap105i0  Link encap:Ethernet  HWaddr de:f6:88:87:2b:f4
       ...

tap110i0  Link encap:Ethernet  HWaddr 52:3c:67:06:1e:c1
       ...

tap110i1  Link encap:Ethernet  HWaddr f2:63:13:8c:bd:59
       ...

veth150i0 Link encap:Ethernet  HWaddr fe:8d:a6:5d:3a:5f
       ...

veth150i1 Link encap:Ethernet  HWaddr fe:46:0d:ae:62:38
       ...

veth151i0 Link encap:Ethernet  HWaddr fe:30:db:9a:9d:58
       ...

veth151i1 Link encap:Ethernet  HWaddr fe:02:81:21:bc:39
       ...

veth152i0 Link encap:Ethernet  HWaddr fe:fd:f3:f5:5c:82
       ...

veth152i1 Link encap:Ethernet  HWaddr fe:97:65:ff:e6:a6
       ...

veth153i0 Link encap:Ethernet  HWaddr fe:e0:00:9f:48:91
       ...

veth154i0 Link encap:Ethernet  HWaddr fe:7b:d9:c1:b5:df
       ...

veth156i0 Link encap:Ethernet  HWaddr fe:81:0a:c9:83:9b
       ...

veth157i0 Link encap:Ethernet  HWaddr fe:9f:3f:79:bd:f1
       ...

veth159i0 Link encap:Ethernet  HWaddr fe:3b:40:e2:be:2a
       ...

veth200i0 Link encap:Ethernet  HWaddr fe:a5:dc:1a:df:3c
       ...

vmbr0     Link encap:Ethernet  HWaddr d0:50:99:a3:33:62
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::d250:99ff:fea3:3362/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:196919 errors:0 dropped:0 overruns:0 frame:0
          TX packets:109123 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:99129505 (94.5 MiB)  TX bytes:84170730 (80.2 MiB)

vmbr1     Link encap:Ethernet  HWaddr fa:19:04:5d:90:6c
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          inet6 addr: fe80::c24a:ff:fe02:7883/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5668 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8242 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:288189 (281.4 KiB)  TX bytes:487104 (475.6 KiB)

vmbr2     Link encap:Ethernet  HWaddr d0:50:99:a3:33:60
          inet6 addr: fe80::d250:99ff:fea3:3360/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1082003 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:88723340 (84.6 MiB)  TX bytes:578 (578.0 B)

vmbr3     Link encap:Ethernet  HWaddr 86:6e:15:3f:79:99
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::3858:eff:fe8f:e1c4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:592 (592.0 B)  TX bytes:798 (798.0 B)

und ein dmesg |grep -i eth0 zeigt folgendes:

Code: 
 dmesg |grep -i eth0
[    0.692823] r8169 0000:01:00.0 eth0: RTL8168e/8111e at 0xffffc90000032000, c0:4a:00:02:78:83, XID 0c200000 IRQ 142
[    0.693492] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   17.207176] device eth0 entered promiscuous mode
[   17.393608] r8169 0000:01:00.0 eth0: link down
[   17.393608] r8169 0000:01:00.0 eth0: link down
[   19.030964] r8169 0000:01:00.0 eth0: link up
[   19.032072] vmbr1: port 1(eth0) entered forwarding state
[   19.032438] vmbr1: port 1(eth0) entered forwarding state
[   39.709365] eth0: renamed from veth9L5AD1
[   41.064396] eth0: renamed from vethRP8WMA
[   43.240539] eth0: renamed from vethMTKB80
[   45.262370] eth0: renamed from vethL3T568
[   48.082331] eth0: renamed from vethRO7RTF
[   50.026889] eth0: renamed from veth40GGY7
[   52.387868] eth0: renamed from vethW9VXRE
[   54.780679] eth0: renamed from vethTSSWVA
[   57.672366] eth0: renamed from vethRQF6P6
[ 7339.182238] vmbr1: port 1(eth0) entered disabled state
[ 7339.182692] device eth0 left promiscuous mode
[ 7339.183063] vmbr1: port 1(eth0) entered disabled state
[ 8307.138703] eth0: renamed from vethO3XBEN
[18961.904569] eth0: renamed from veth2AOILS
[19004.270979] eth0: renamed from vethLFE0UA
[19156.796888] eth0: renamed from vethWPGQGN
[19289.760959] eth0: renamed from vethB413M4
[19357.025838] eth0: renamed from veth9A9WLO
[19394.429517] eth0: renamed from vethM4JU7F
[19934.138352] eth0: renamed from veth0HY0WM
[19945.302101] eth0: renamed from vethX9JDHW
[20289.588013] eth0: renamed from vethUMDJTQ
[20341.131029] eth0: renamed from vethPFIJBL
[20888.219523] eth0: renamed from veth2UURYR
[21998.460875] eth0: renamed from vethHU8PPC

Die /network/interfaces zeigt:

Code: 
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

iface eth2 inet manual

auto vmbr0
iface vmbr0 inet static
        address  192.168.1.1
        netmask  255.255.255.0
        gateway  192.168.1.101
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet static
        address  192.168.4.1
        netmask  255.255.255.0
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr2
iface vmbr2 inet manual
        bridge_ports eth2
        bridge_stp off
        bridge_fd 0

auto vmbr3
iface vmbr3 inet static
        address  192.168.1.3
        netmask  255.255.255.0
        bridge_ports none
        bridge_stp off
        bridge_fd 0

Weiss jemand Rat?
 
Hi,
die Ethernet-Karte, die nicht geht, ist die RealTek onboard?

Ist es eine "normale" pve-standardinstallation?

Wie sind die Ausgaben von folgenden Befehlen:
Code: 
lspci -v | egrep Ethernet\|driver

cat /etc/udev/rules.d/70-persistent-net.rules

pveversion -v
Udo - der von Realtek-NICs allerdings nicht viel hält.
 
Hallo Udo,

nein, die onboard Karte funktionieren. Die gesteckte PCI-E Karte will nicht.
Code: 
~# lspci -v | egrep Ethernet\|driver
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: i915_bpo
        Kernel driver in use: xhci_hcd
        Kernel driver in use: mei_me
        Kernel driver in use: ahci
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: snd_hda_intel
        Kernel driver in use: i801_smbus
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
        Kernel driver in use: e1000e
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
        Kernel driver in use: vfio-pci
        Kernel driver in use: vfio-pci
        Kernel driver in use: xhci_hcd
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
        Kernel driver in use: igb
        Kernel driver in use: ahci
        Kernel driver in use: ahci


Code: 
~# cat /etc/udev/rules.d/70-persistent-net.rules
cat: /etc/udev/rules.d/70-persistent-net.rules: No such file or directory

:~# ls /etc/udev/rules.d/
[nichts]

Code: 
~# pveversion -v
proxmox-ve: 4.3-66 (running kernel: 4.4.19-1-pve)
pve-manager: 4.3-1 (running version: 4.3-1/e7cdc165)
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-46
qemu-server: 4.0-88
pve-firmware: 1.1-9
libpve-common-perl: 4.0-73
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-61
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.1-6
pve-container: 1.0-75
pve-firewall: 2.0-29
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.4-1
lxcfs: 2.0.3-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80

wegen der fehlenden udev rules habe ich mal

/sbin/udevadm trigger --type=devices --action=add

ausgeführt.
Dies hat die rules Datei angelegt, aber nur mit 2 Interfaces:
Code: 
cat 70-persistent-net.rules

# PCI device 0x8086:0x15b8 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d0:50:99:a3:33:60", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x8086:0x1539 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="d0:50:99:a3:33:62", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

Noch ein Hinweis: Ich habe exakt die gleiche PCI Karte in einem anderen proxmox Server (allerdings mit einem anderen Mainboard) - und dort funktioniert sie einwandfrei.

Jan
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom