[RISOLTO] - Eliminare una interfaccia di rete

Fedora Linux Configurazione
#1

Salve,
da terminale, il comando:

ifconfig

dà il seguente output:

em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.80 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::222:4dff:fe80:f9c7 prefixlen 64 scopeid 0x20
ether 00:22:4d:80:f9:c7 txqueuelen 1000 (Ethernet)
RX packets 7595 bytes 6868221 (6.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6427 bytes 1076376 (1.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7100000-f7120000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 8 bytes 580 (580.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 580 (580.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

L’interfaccia “lo” è stata creata da virt-manager, stò cercando di eliminarla, ho provato anche disinstallando, e reinstallando virt-manager, ma pur non comparendo nelle interfacce di rete del programma, essa si ripresenta da riga di comando, qualcuno può aiutarmi ad eliminarla?

#2

In base a cosa dici che lo è stata creata da virt-manager? E’ l’interfaccia di loopback quella. Servono ai servizi del sistema per comunicare tra loro, non vedo perché eliminarla…a meno di non rischiare ad avere alcuni servizi non funzionanti…

#3

Perchè succede anche con altre interfacce sempre create in virt-manager:

ifconfig

bridge: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.1.80 netmask 255.255.255.0 broadcast 192.168.1.255
ether 72:6d:7c:ca:64:af txqueuelen 0 (Ethernet)
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

em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.80 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::222:4dff:fe80:f9c7 prefixlen 64 scopeid 0x20
ether 00:22:4d:80:f9:c7 txqueuelen 1000 (Ethernet)
RX packets 17186 bytes 13238577 (12.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13089 bytes 2371636 (2.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7100000-f7120000

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.1 netmask 255.255.255.0 broadcast 192.168.80.255
ether 52:54:00:1d:c0:8e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 42 bytes 1764 (1.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0-nic: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:1d:c0:8e txqueuelen 500 (Ethernet)
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

virbr0-nic.0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.80 netmask 255.255.255.0 broadcast 192.168.80.255
ether 52:54:00:1d:c0:8e txqueuelen 0 (Ethernet)
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

adesso invece l’interfaccia “lo” che è sparita dal terminale, compare nella finestra di virt-manager

#4

Nuovi sviluppi

em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.80 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::222:4dff:fe80:f9c7 prefixlen 64 scopeid 0x20
ether 00:22:4d:80:f9:c7 txqueuelen 1000 (Ethernet)
RX packets 316 bytes 283092 (276.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 258 bytes 28919 (28.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7100000-f7120000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 8 bytes 580 (580.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 580 (580.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.80.1 netmask 255.255.255.0 broadcast 192.168.80.255
ether 52:54:00:1d:c0:8e txqueuelen 0 (Ethernet)
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

Scusa non avevo capito, in tal caso significa che è tutto nella norma. Chiudo la discussione.

#5

Le interfaccie create da virt-manager non sono create da lui ma da libvirtd quando avvii una macchina virtuale. La cosa è necessaria per comunicare con la macchina virtuale.
L’interfaccia di loopback è altro ancora.

Ciao