[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Va bene i nomi strani alle interfacce, ma...


Il 11/02/2020 09:28, Marco Gaiarin ha scritto:

Serverino proxmox6 (debian buster, kernel 5.3.18-1-pve); la scheda di rete
integrata viene decentemente vista e rinominata:

  root@ino:~# grep tg3 /var/log/kern.log
  Feb 11 09:16:42 ino kernel: [    3.449190] tg3.c:v3.137 (May 11, 2014)
  Feb 11 09:16:42 ino kernel: [    3.468877] tg3 0000:1e:00.0 eth0: Tigon3 [partno(BCM95723) rev 5784100] (PCI Express) MAC address 9c:8e:99:7b:86:d9
  Feb 11 09:16:42 ino kernel: [    3.468879] tg3 0000:1e:00.0 eth0: attached PHY is 5784 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
  Feb 11 09:16:42 ino kernel: [    3.468881] tg3 0000:1e:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
  Feb 11 09:16:42 ino kernel: [    3.468883] tg3 0000:1e:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
  Feb 11 09:16:42 ino kernel: [    3.485088] tg3 0000:1e:00.0 ens1: renamed from eth0
  Feb 11 09:16:44 ino kernel: [  101.292206] tg3 0000:1e:00.0 ens1: Link is up at 100 Mbps, full duplex
  Feb 11 09:16:44 ino kernel: [  101.292208] tg3 0000:1e:00.0 ens1: Flow control is on for TX and on for RX

ma me ne serve una seconda, che aggiungo in un secondo momento; questa viene
vista, ma rinominata in un modo direi alquanto pittoresco:

  root@ino:~# grep e1000e /var/log/kern.log
  Feb 11 09:16:42 ino kernel: [    3.451250] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
  Feb 11 09:16:42 ino kernel: [    3.451251] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  Feb 11 09:16:42 ino kernel: [    3.451430] e1000e 0000:20:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
  Feb 11 09:16:42 ino kernel: [    3.502028] e1000e 0000:20:00.0 0000:20:00.0 (uninitialized): registered PHC clock
  Feb 11 09:16:42 ino kernel: [    3.556137] e1000e 0000:20:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 2c:27:d7:14:9b:67
  Feb 11 09:16:42 ino kernel: [    3.556139] e1000e 0000:20:00.0 eth0: Intel(R) PRO/1000 Network Connection
  Feb 11 09:16:42 ino kernel: [    3.556182] e1000e 0000:20:00.0 eth0: MAC: 3, PHY: 8, PBA No: G17305-003
  Feb 11 09:16:42 ino kernel: [    3.557393] e1000e 0000:20:00.0 rename3: renamed from eth0

Mi sono dato una occhata al wiki debian, e mi sembra tutto OK:

	https://wiki.debian.org/NetworkInterfaceNames

In particolare quella integrata:

Il nome della scheda integrata dovrebbe essere enp30s0


  root@ino:~# udevadm test-builtin net_id /sys/class/net/ens1
  Load module index
  Parsed configuration file /usr/lib/systemd/network/99-default.link
  Created link configuration context.
  Using default interface naming scheme 'v240'.
  ID_NET_NAMING_SCHEME=v240
  ID_NET_NAME_MAC=enx9c8e997b86d9
  ID_OUI_FROM_DATABASE=Hewlett Packard
  ID_NET_NAME_PATH=enp30s0
  ID_NET_NAME_SLOT=ens1
  Unload module index
  Unloaded link configuration context.

mentre quella aggiuntiva:

e il nome della scheda aggiuntiva dovrebbe essere enp32s0


  root@ino:~# udevadm test-builtin net_id /sys/class/net/rename3
  Load module index
  Parsed configuration file /usr/lib/systemd/network/99-default.link
  Created link configuration context.
  Using default interface naming scheme 'v240'.
  ID_NET_NAMING_SCHEME=v240
  ID_NET_NAME_MAC=enx2c27d7149b67
  ID_OUI_FROM_DATABASE=Hewlett Packard
  ID_NET_NAME_PATH=enp32s0
  ID_NET_NAME_SLOT=ens1
  Unload module index
  Unloaded link configuration context.

Cioè, il problema è che ritiene che entrambe debbano chiamarsi 'ens1',
quindi la seconda la chiama 'rename3'?
Però c'è sempre da capire il motivo per cui il nome dello slot (ens1),  viene inizialmente generato identico per entrambe le schede che, si presume, dovrebbero trovarsi su slot Pcie diversi. 



Mah, non ci sono più i kernel di una volta... ;-)

Luciano
Reply to: