3 máquinas Ubuntu sem rede esta manhã

3 máquinas Ubuntu sem rede esta manhã

Execute uma variedade de máquinas Windows, MAC e Ubuntu em nosso escritório. Tudo funcionando bem, até esta manhã, quando três das máquinas Ubuntu não mostram nenhuma rede, mas configurações de cabos Ethernet (e Wifi) intocadas desde sexta-feira.

Brinquei um pouco com as conexões e não tive alegria esta manhã. Estão todos aparecendo Connection failed Activation of network connection failed. Eu poderia entender uma falha no fim de semana, mas 3? E tanto o Wifi quanto a Ethernet falhando.

Peguei um USB e inicializei a partir de um novo download do 23.04 e tive o mesmo problema - isso em 2 máquinas diferentes.

Reformatei uma das máquinas, instalei 23.04 e mesmo problema. Tentei um "experimente o Ubuntu" virgem na outra máquina e o mesmo problema.

Uso o Ubuntu há mais de 10 anos e nunca vi nada parecido com isso - sugestões? Compreendo que pode ter sido uma atualização que causou o problema, mas uma nova cópia do 23.04 certamente teria resolvido isso.

Por último - provavelmente é um falso positivo, mas notei no fim de semana que nossa caixa Synology colocou em quarentena um arquivo rotulado comoUnix.Malware.Kaiji-10003916-0 - prometheus

Máquinas Windows e MAC funcionando bem, e 2 máquinas Ubuntu rodando 22.04 e 20.04 funcionando bem...

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:23:24:cc:a0:73 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 84:ef:18:4f:fc:86 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5ac8:c13d:d002:cff/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever


sudo lshw -c network
  *-network                 
       description: Wireless interface
       product: Dual Band Wireless-AC 3165 Plus Bluetooth
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlp1s0
       version: 99
       serial: 84:ef:18:4f:fc:86
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=5.19.0-43-generic firmware=29.4063824552.0 7265D-29.ucode latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:125 memory:df000000-df001fff
  *-network
       description: Ethernet interface
       product: Ethernet Connection (2) I219-V
       vendor: Intel Corporation
       physical id: 1f.6
       bus info: pci@0000:00:1f.6
       logical name: eno1
       version: 31
       serial: 00:23:24:cc:a0:73
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.19.0-43-generic duplex=full firmware=0.8-4 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:123 memory:df100000-df11ffff


ifconfig -a
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:23:24:cc:a0:73  txqueuelen 1000  (Ethernet)
        RX packets 24641  bytes 2100911 (2.1 MB)
        RX errors 0  dropped 27  overruns 0  frame 0
        TX packets 482  bytes 116491 (116.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf100000-df120000  

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 17096  bytes 3061579 (3.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17096  bytes 3061579 (3.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5ac8:c13d:d002:cff  prefixlen 64  scopeid 0x20<link>
        ether 84:ef:18:4f:fc:86  txqueuelen 1000  (Ethernet)
        RX packets 461  bytes 84832 (84.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 774  bytes 181455 (181.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Unattended-upgrades.log
2023-06-09 11:23:23,107 WARNING Could not figure out development release: Distribution data outdated. Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details.
2023-06-09 11:23:23,107 INFO Starting unattended upgrades script
2023-06-09 11:23:23,108 INFO Allowed origins are: o=Ubuntu,a=jammy, o=Ubuntu,a=jammy-security, o=UbuntuESMApps,a=jammy-apps-security, o=UbuntuESM,a=jammy-infra-security
2023-06-09 11:23:23,108 INFO Initial blacklist: 
2023-06-09 11:23:23,108 INFO Initial whitelist (not strict): 
2023-06-09 11:23:28,194 INFO No packages found that can be upgraded unattended and no pending auto-removals
2023-06-12 10:43:15,017 WARNING Could not figure out development release: Distribution data outdated. Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details.
2023-06-12 10:43:15,017 INFO Starting unattended upgrades script
2023-06-12 10:43:15,018 INFO Allowed origins are: o=Ubuntu,a=jammy, o=Ubuntu,a=jammy-security, o=UbuntuESMApps,a=jammy-apps-security, o=UbuntuESM,a=jammy-infra-security
2023-06-12 10:43:15,018 INFO Initial blacklist: 
2023-06-12 10:43:15,018 INFO Initial whitelist (not strict): 
2023-06-12 10:43:19,213 INFO No packages found that can be upgraded unattended and no pending auto-removals

Responder1

user535733 - Li seu comentário e segui em frente imediatamente, pois não poderia ser o roteador, pois todas as outras máquinas estavam bem. Ontem tive um problema um pouco diferente, reiniciei o roteador e agora tudo está funcionando bem. Suspirar. Tão ocupado em resolver o problema porque deve ser complicado, sabe? :-)

Obrigado a todos que responderam...

informação relacionada