Ubuntu 18.04를 실행하는 내 워크스테이션에는 방대한 네트워크 인터페이스 목록이 있는데 그 이유와 출처가 무엇인지 모르겠습니다. 소스를 식별하고 궁극적으로 불필요한 소스를 제거하려면 어떻게 해야 합니까?
목록은 다음과 같습니다.
$ ifconfig
br-29520a0ce031: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.16.1 netmask 255.255.240.0 broadcast 192.168.31.255
inet6 fe80::42:caff:fed9:52e prefixlen 64 scopeid 0x20<link>
ether 02:42:ca:d9:05:2e txqueuelen 0 (Ethernet)
RX packets 251577 bytes 39174576 (39.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 309301 bytes 69182317 (69.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-ff1381b996dc: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.32.1 netmask 255.255.240.0 broadcast 192.168.47.255
inet6 fe80::42:3cff:fe7f:4557 prefixlen 64 scopeid 0x20<link>
ether 02:42:3c:7f:45:57 txqueuelen 0 (Ethernet)
RX packets 267586 bytes 46766800 (46.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 335535 bytes 79812439 (79.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
inet6 fe80::42:c7ff:fe35:d36e prefixlen 64 scopeid 0x20<link>
ether 02:42:c7:35:d3:6e txqueuelen 0 (Ethernet)
RX packets 29876 bytes 140318987 (140.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 37338 bytes 59172455 (59.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.50.200.154 netmask 255.255.0.0 broadcast 10.50.255.255
inet6 fe80::1bc3:ab5d:375c:8ce6 prefixlen 64 scopeid 0x20<link>
ether b8:ca:3a:81:32:80 txqueuelen 1000 (Ethernet)
RX packets 25972627 bytes 15133370409 (15.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1143922 bytes 352665651 (352.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfb500000-fb520000
enp7s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:ca:3a:81:32:81 txqueuelen 1000 (Ethernet)
RX packets 25361880 bytes 15989431890 (15.9 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14442174 bytes 7247141626 (7.2 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xfb200000-fb220000
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 1000 (Local Loopback)
RX packets 8701819 bytes 3493583516 (3.4 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8701819 bytes 3493583516 (3.4 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth097d5a6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::c94:feff:fea4:284a prefixlen 64 scopeid 0x20<link>
ether 0e:94:fe:a4:28:4a txqueuelen 0 (Ethernet)
RX packets 30506 bytes 9858899 (9.8 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35067 bytes 20332314 (20.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth5716a8c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::bc62:38ff:fed2:b18a prefixlen 64 scopeid 0x20<link>
ether be:62:38:d2:b1:8a txqueuelen 0 (Ethernet)
RX packets 159232 bytes 26302540 (26.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 170757 bytes 34933057 (34.9 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth5faed64: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::d4be:66ff:fe5a:4648 prefixlen 64 scopeid 0x20<link>
ether d6:be:66:5a:46:48 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2360 bytes 483714 (483.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth7ce715c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::6031:cdff:fe13:66dd prefixlen 64 scopeid 0x20<link>
ether 62:31:cd:13:66:dd txqueuelen 0 (Ethernet)
RX packets 66523 bytes 13644088 (13.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 103133 bytes 22174559 (22.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth9b98dd5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a89b:b2ff:fe54:45a0 prefixlen 64 scopeid 0x20<link>
ether aa:9b:b2:54:45:a0 txqueuelen 0 (Ethernet)
RX packets 76962 bytes 11725527 (11.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 53731 bytes 9298294 (9.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vethb5023c5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::1cb9:b6ff:fe9a:c42a prefixlen 64 scopeid 0x20<link>
ether 1e:b9:b6:9a:c4:2a txqueuelen 0 (Ethernet)
RX packets 62643 bytes 9497323 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 110635 bytes 15533473 (15.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0(Docker), lo(localhost) enp0s25및 enp7s0(이더넷 장치 0 및 1)을 식별했습니다 .
하지만 다른 사람들도 br-*그렇고 veth*나도 그렇고전혀 모른다그들이 어디서 왔는지, 그곳에서 무엇을 하는지.
답변1
br-* - 브리지, veth* - 가상 이더넷. 도커를 사용하고 있습니다.
자세한 내용을 보려면 여기를 클릭하세요:
답변2
현재 이 호스트에서 실행 중인 가상 머신 및/또는 Docker 컨테이너는 몇 개입니까? 이러한 VM/컨테이너의 총 가상 네트워크 인터페이스 수가 veth*표시되는 인터페이스 수와 일치합니까?
이러한 veth*인터페이스는 VM/컨테이너에 있는 가상 네트워크 카드의 "호스트 측"일 수 있으며 이러한 br-*인터페이스는브리지 인터페이스(예: VMware의 가상 스위치에 해당) 서로 다른 가상 머신/컨테이너를 서로, 호스트 및/또는 외부 세계에 연결합니다. docker0~이다기본Docker의 브리지이지만 두 개의 물리적 네트워크 카드가 있으므로 구성에 기본 브리지보다 더 많은 브리지가 필요할 수 있습니다.