Perguntas[networking](ubuntu)

Instalei o Ubuntu 24.04.2 LTS em um novo PC e estou enfrentando um problema com o adaptador Bluetooth. O sistema o detecta e parece estar ligado, mas não consegue encontrar nenhum dispositivo Bluetooth próximo.

Aqui estão as informações relevantes do sistema e diagnóstico:

Sistema operacional: Ubuntu 24.04.2 LTS Versão do kernel: 6.11.0-24-generic Adaptador Bluetooth: Rádio Bluetooth IMC Networks (ID USB 13d3:3600)

Saídas de diagnóstico:

Saída lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 004: ID 30fa:2350 INSTANT USB Keyboard
Bus 003 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 006: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 007: ID 30fa:0400  USB Optical Mouse
Bus 003 Device 008: ID 13d3:3600 IMC Networks Bluetooth Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub

lspci | grep Ethernet:

84:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 0c)

lsmod | grep bluetooth e lsmod | grep btusb saída:

bluetooth              1028096  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
btusb                   69632  0
btrtl                   36864  1 btusb
btintel                 69632  1 btusb
btbcm                   24576  1 btusb
btmtk                   36864  1 btusb
bluetooth              1028096  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

status do systemctl bluetooth

bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-04-27 12:53:16 EDT; 5min ago
       Docs: man:bluetoothd(8)
   Main PID: 960 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37563)
     Memory: 3.2M (peak: 3.7M)
        CPU: 17ms
     CGroup: /system.slice/bluetooth.service
             └─960 /usr/libexec/bluetooth/bluetoothd

Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/faststream
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/opus_05
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/opus_05
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Apr 27 12:53:40 moribots bluetoothd[960]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/opus_05_duplex

listar todos os rfkill

0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

bluetoothctl mostra relatórios Energizado: sim

Controller C0:BF:BE:B6:06:D9 (public)
    Manufacturer: 0x005d (93)
    Version: 0x0c (12)
    Name: moribots
    Alias: moribots
    Class: 0x006c0104 (7078148)
    Powered: yes
    Discoverable: no
    DiscoverableTimeout: 0x000000b4 (180)
    Pairable: yes
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink            (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: Audio Source          (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree         (0000111e-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0548
    Discovering: no
    Roles: central
    Roles: peripheral
Advertising Features:
    ActiveInstances: 0x00 (0)
    SupportedInstances: 0x05 (5)
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name
    SupportedSecondaryChannels: 1M
    SupportedSecondaryChannels: 2M
    SupportedSecondaryChannels: Coded

Comportamento do comando bluetoothctl scan on: quando executo o scan on no bluetoothctl, o comando é executado e inicia a descoberta, mas não lista nenhum dispositivo Bluetooth próximo.

Saída dmesg relevante (mensagens do kernel sobre detecção de dispositivos e relacionadas a bluetooth/firmware):

[    0.514056] Relocating firmware framebuffer to offset 0x0000000000000000[d] within [mem 0x6800000000-0x6bffffffff flags 0x14220c]
[    0.656835] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.656841] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 1
[    0.657122] ahci 0000:80:17.0: version 3.0
[    0.657940] xhci_hcd 0000:00:0d.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000200009810
[    0.658458] ahci 0000:80:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[    0.658461] ahci 0000:80:17.0: 4/4 ports implemented (port mask 0xf0)
[    0.658462] ahci 0000:80:17.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds
[    0.658898] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.658900] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 2
[    0.658902] xhci_hcd 0000:00:0d.0: Host supports USB 3.2 Enhanced SuperSpeed
[    0.658936] usb usb1: Product: xHCI Host Controller
[    0.658937] usb usb1: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.659549] usb usb2: Product: xHCI Host Controller
[    0.659550] usb usb2: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.662654] xhci_hcd 0000:80:14.0: xHCI Host Controller
[    0.662676] xhci_hcd 0000:80:14.0: new USB bus registered, assigned bus number 3
[    0.663817] xhci_hcd 0000:80:14.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000200009810
[    0.664080] xhci_hcd 0000:80:14.0: xHCI Host Controller
[    0.664082] xhci_hcd 0000:80:14.0: new USB bus registered, assigned bus number 4
[    0.664083] xhci_hcd 0000:80:14.0: Host supports USB 3.2 Enhanced SuperSpeed
[    0.664109] usb usb3: Product: xHCI Host Controller
[    0.664109] usb usb3: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.665486] usb usb4: Product: xHCI Host Controller
[    0.665486] usb usb4: Manufacturer: Linux 6.11.0-24-generic xhci-hcd
[    0.667970] scsi host0: ahci
[    0.668049] scsi host1: ahci
[    0.668094] scsi host2: ahci
[    0.668139] scsi host3: ahci
[    0.668190] scsi host4: ahci
[    0.668237] scsi host5: ahci
[    0.668283] scsi host6: ahci
[    0.668324] scsi host7: ahci
[    0.900715] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[    1.145479] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[    1.294731] usb 3-2: new high-speed USB device number 3 using xhci_hcd
[    1.543702] usb 3-3: new low-speed USB device number 4 using xhci_hcd
[    1.792280] usb 3-7: new high-speed USB device number 5 using xhci_hcd
[    2.045769] usb 3-8: new full-speed USB device number 6 using xhci_hcd
[    2.296268] usb 3-9: new low-speed USB device number 7 using xhci_hcd
[    2.546264] usb 3-14: new full-speed USB device number 8 using xhci_hcd
[    2.676615] usb 3-14: Product: Bluetooth Radio
[    3.288546] intel_vpu 0000:00:0b.0: [drm] Firmware: intel/vpu/vpu_37xx_v0.0.bin, version: 20230726*MTL_CLIENT_SILICON-release*2101*ci_tag_mtl_pv_vpu_rc_20230726_2101*648a666b8b9
[    3.296754] Bluetooth: Core ver 2.22
[    3.317632] NET: Registered PF_BLUETOOTH protocol family
[    3.317635] Bluetooth: HCI device and connection manager initialized
[    3.317638] Bluetooth: HCI socket layer initialized
[    3.317639] Bluetooth: L2CAP socket layer initialized
[    3.317643] Bluetooth: SCO socket layer initialized
[    3.374792] rtw89_8851be 0000:83:00.0: loaded firmware rtw89/rtw8851b_fw.bin
[    3.376058] rtw89_8851be 0000:83:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 5
[    3.376060] rtw89_8851be 0000:83:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 3
[    4.372663] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.372666] Bluetooth: BNEP filters: protocol multicast
[    4.372670] Bluetooth: BNEP socket layer initialized
[    4.373513] Bluetooth: MGMT ver 1.23
[   15.142427] Bluetooth: RFCOMM TTY layer initialized
[   15.142434] Bluetooth: RFCOMM socket layer initialized
[   15.142438] Bluetooth: RFCOMM ver 1.11

Alguém pode me ajudar a identificar qual driver preciso instalar? Este driver está instalado em um PC Asus ROG700 pré-montado.

Estou tentando procurar redes Wi-Fi disponíveis usando o Ubuntu Server. Estou tentando fazer isso sem instalar nenhum pacote de terceiros.

Pelo que sei, durante o processo de instalação do Ubuntu Server, o assistente propõe algumas redes disponíveis que encontrou, mas não consigo dizer qual programa ele usa no ISO para fazer isso.

1. é possível fazer isso sem instalar nenhum pacote extra?
2. caso contrário, qual pacote posso instalar para fazer uma varredura rápida? (observe que gostaria de evitar o NetworkManager e continuar usando o systemd-networkd padrão)

Nosso scanner de segurança mostra que há uma vulnerabilidade no Kernel 5.15.0-134-generic atual. Então, fiz uma atualização e ela interrompeu gravemente a conectividade de rede. A ponto de, após a inicialização, o servidor nem reconhecer mais a interface de rede. Este é um Dell Poweredge r710 (sei que é muito antigo). Estou apenas tentando mantê-lo ativo. O endereço IP não lista a placa de rede Ethernet, mas mostra outros dispositivos de rede.

A única coisa que me vem à mente é que o novo kernel tem apenas uma semana e talvez ainda não tenha sido atualizado com os mesmos drivers. Se eu reverter o kernel, a placa de rede (NIC) volta instantaneamente e a conectividade volta a funcionar. Tentei conectar um adaptador de rede USB dongle e ele também não detecta, então o suporte de hardware ausente não se limita à interface da placa de rede. Também instalamos uma placa de fibra óptica de 10 GB, que ainda funciona com ambos os kernels. Isso nunca aconteceu comigo antes. Vocês têm alguma ideia ou solução possível?

Resumo : Tenho um serviço em execução na porta 9000, ao qual consigo me conectar localmente (127.0.0.1:9000) a partir de um aplicativo Go, mas não de outra máquina (192.168.0.136:9000). Consigo fazer ping entre os dois computadores e a porta 9000 está aberta no UFW.

EDIT 1 : Não consigo acessar o serviço mesmo se desabilitar o UFW.

Sou iniciante em Linux e redes. Tenho um laptop com Ubuntu 24.04.2.LTS conectado (via Wi-Fi) ao meu roteador de internet doméstico. Também tenho um desktop com Windows 11 conectado (via Ethernet) ao mesmo roteador.

Executar ifconfig no Ubuntu fornece: (copiei apenas a parte que considero relevante)

wlp0s20f3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.136  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::ddd9:be4c:f345:fe99  prefixlen 64  scopeid 0x20<link>
        ether 28:a0:6b:0d:68:2b  txqueuelen 1000  (Ethernet)
        RX packets 25308  bytes 12372387 (12.3 MB)
        RX errors 0  dropped 800  overruns 0  frame 0
        TX packets 11271  bytes 5198621 (5.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Executar o ipconfg no Windows resulta em: (copiei apenas a parte que considero relevante)

   Connection-specific DNS Suffix  . : home
   Link-local IPv6 Address . . . . . : fe80::249e:fcf2:6e8f:99d0%6
   IPv4 Address. . . . . . . . . . . : 192.168.0.46
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Tenho um serviço Clickhouse em execução no meu laptop Ubuntu, que estou tentando acessar a partir de um aplicativo Go em execução no meu desktop Windows. Continuo recebendo o erro: panic: dial tcp 192.168.0.136:9000: connectex: Nenhuma conexão pôde ser feita porque a máquina de destino a recusou ativamente.

Tenho certeza de que o Clickhouse está funcionando corretamente na porta 9000, pois consigo me conectar a ele quando executo meu código Go diretamente no laptop Ubuntu . A string de conexão em ambos os casos pode ser encontrada aqui .

Consigo executar ping no computador Windows a partir do computador Ubuntu e vice-versa . No entanto, não consigo executar ping na porta 9000 a partir do computador Windows . Estou usando o PsPing do PsTools no Windows.

Verifiquei que as portas estão abertas no UFW: netstat -tulpn

Como posso acessar este serviço do Clickhouse no meu computador Windows?

Edições

• 2025-03-15: Minha pergunta não é semelhante a esta pelos seguintes motivos:
  • Meu kernel é 6.11.0-19-generic, que é mais recente que o kernel que resolveu o problema daquele usuário.
  • Ao contrário desse usuário, quando executo sudo dmesg | grep wcnou sudo dmesg | grep ath, nada aparece.
  • O wifi da minha máquina está visível nas configurações de rede.

Resumo

Recentemente, configurei uma máquina dual boot com Windows 11/Ubuntu 24 com uma placa-mãe MSI MPG X870E Carbon WiFi. Normalmente, obtenho minhas conexões WiFi da placa-mãe; não há dongle externo. Em ambos os sistemas operacionais, o WiFi tende a ser mais lento do que em outros dispositivos de especificações mais baixas na mesma rede.

Ao solucionar isso, executei iwconfig, que retornou:

lo        no wireless extensions.

enp9s0    no wireless extensions.

enp10s0   no wireless extensions.

wlp17s0   no wireless extensions.

Isso me parece estranho. Já que consigo usar a internet (mesmo que lentamente), não deveria conseguir ver alguns resultados aqui?

Informações de diagnóstico

A execução ifconfigmostra mais resultados (reduzi alguns endereços IP *quando suspeito que eles podem ser sensíveis):

enp10s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether ****:****:****:****:****:****  txqueuelen 1000  (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

enp9s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether ****:****:****:****:****:****  txqueuelen 1000  (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

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask ***.***.***.***
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 573  bytes 62912 (62.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 573  bytes 62912 (62.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp17s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet ***.***.***.***  netmask ***.***.***.***  broadcast ***.***.***.***
        inet6 ****:****:****:****:****:****  prefixlen 128  scopeid 0x0<global>
        inet6 ****:****:****:****:****:****  prefixlen 64  scopeid 0x20<link>
        inet6 ****:****:****:****:****:****:*****:*****  prefixlen 64  scopeid 0x0<global>
        inet6 ****:****:****:****:****:****:*****:*****  prefixlen 64  scopeid 0x0<global>
        ether ****:****:****:****:****:****  txqueuelen 1000  (Ethernet)
        RX packets 391880  bytes 505296333 (505.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 141640  bytes 97357724 (97.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

A execução sudo lshw -C networkme dá (números de série e endereços IP redigidos *porque não sei se são confidenciais):

  *-network                 
       description: Ethernet interface
       product: RTL8125 2.5GbE Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: enp9s0
       version: 05
       serial: **:**:**:**:**:**
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.11.0-19-generic firmware=rtl8125b-2_0.0.2 07/13/20 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:24 ioport:d000(size=256) memory:a0000000-a000ffff memory:a0010000-a0013fff
  *-network
       description: Ethernet interface
       product: Realtek Semiconductor Co., Ltd.
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:0a:00.0
       logical name: enp10s0
       version: 01
       serial: **:**:**:**:**:**
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.11.0-19-generic firmware=rtl8126a-3_0.0.5 08/30/24 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:42 ioport:c000(size=256) memory:a0100000-a010ffff memory:a0110000-a0113fff
  *-network
       description: Ethernet interface
       product: WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800]
       vendor: Qualcomm Technologies, Inc
       physical id: 0
       bus info: pci@0000:11:00.0
       logical name: wlp17s0
       version: 01
       serial: **:**:**:**:**:**
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=ath12k_pci driverversion=6.11.0-19-generic firmware=N/A ip=***.***.***.*** latency=0 link=yes multicast=yes
       resources: irq:163 memory:a0200000-a03fffff

Correr lsusbme dá:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0b05:18e5 ASUSTek Computer, Inc. ROG CHAKRAM
Bus 001 Device 003: ID 3434:d030 Keychron  Keychron Link 
Bus 001 Device 004: ID 0db0:0076 Micro Star International MYSTIC LIGHT
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:5420 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 003 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 004: ID 1bcf:2283 Sunplus Innovation Technology Inc. Full HD webcam
Bus 003 Device 005: ID 0489:e10a Foxconn / Hon Hai 
Bus 003 Device 006: ID 0db0:0b58 Micro Star International USB Audio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0bda:0420 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 004 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Retornos correntes lspci:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14d8
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 14d9
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db
00:01.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14dd
00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14dd
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e7
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev 10)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch (rev 10)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] (rev c8)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 HDMI/DP Audio
04:00.0 Non-Volatile memory controller: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1602 (DRAM-less) (rev 01)
05:00.0 Non-Volatile memory controller: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1602 (DRAM-less) (rev 01)
06:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01)
07:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
07:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01)
0d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01)
0e:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
0e:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
0e:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
0e:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
0e:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
0e:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01)
11:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)
13:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43fd (rev 01)
14:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01)
15:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43fd (rev 01)
16:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01)
17:00.0 PCI bridge: ASMedia Technology Inc. Device 2421 (rev 01)
18:00.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01)
18:01.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01)
18:02.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01)
18:03.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01)
79:00.0 USB controller: ASMedia Technology Inc. Device 2426 (rev 01)
7a:00.0 USB controller: ASMedia Technology Inc. Device 2425 (rev 01)
7b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c9)
7b:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller
7b:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP
7b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b6
7b:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b7
7b:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
7c:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b8

Aqui estão as configurações do meu sistema:

# System Details Report
---

## Report details
- **Date generated:**                              2025-03-08 15:58:02

## Hardware Information:
- **Hardware Model:**                              Micro-Star International Co., Ltd. MS-7E49
- **Memory:**                                      64.0 GiB
- **Processor:**                                   AMD Ryzen™ 9 7950X3D × 32
- **Graphics:**                                    AMD Radeon™ RX 7900 XTX
- **Graphics 1:**                                  AMD Radeon™ Graphics
- **Disk Capacity:**                               4.1 TB

## Software Information:
- **Firmware Version:**                            1.A1G
- **OS Name:**                                     Ubuntu 24.04.2 LTS
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               46
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.11.0-19-generic

Pergunta anterior

Configurei esta máquina anteriormente como Windows 11/Linux Mint 22, e durante esse período tive um problema de falta de Wi-Fi. Recebi ajuda para esses problemas aqui . Desde que substituí o Linux Mint pelo Ubuntu, ainda encontro, às vezes, o Windows 11 sem Wi-Fi após reiniciá-lo a partir do Ubuntu, mas isso é corrigido reiniciando a máquina.

Estou usando o Ubuntu Desktop. Gostaria de usar um nome de host em vez do endereço IP quando quiser conectar-me ao Ubuntu Desktop enquanto uso ssh. Isso tornaria mais fácil conectar-se a esse dispositivo, pois o IP pode mudar após uma reinicialização.

Então agora preciso executar:

ssh [email protected]

No entanto, eu gostaria de ter algo assim:

ssh [email protected]

Alguma ideia de como posso atribuir um nome de host ao meu desktop Ubuntu?

Tenho uma instalação nova do servidor Ubuntu 24.04 com 5 NICs.

O primeiro é o DHCP e não é realmente usado. Os outros 4 serão usados ​​como interfaces Pi-hole.

Tentei a seguinte configuração. Posso acessar via SSH a esses endereços IP, mas não consigo navegar na internet após atribuir os endereços IP estáticos.

# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
#network:
#    ethernets:
#        eno1:
#            dhcp4: true
#    version: 2
network:
    ethernets:
        eno1:
            dhcp4: true
        enp4s0:
            dhcp4: false
            addresses: [10.3.142.3/23]
            routes:
                - to: 10.3.142.0/23
                  via: 10.3.142.1
            nameservers:
                addresses: [1.1.1.1, 1.0.0.1, 8.8.8.8, 8.8.4.4]
        enp5s0:
            dhcp4: false
            addresses: [172.1.0.2/24]
            routes:
                - to: 172.1.0.0/24
                  via: 172.1.0.1
            nameservers:
                addresses: [1.1.1.1, 1.0.0.1, 8.8.8.8, 8.8.4.4]
        enp6s0:
            dhcp4: false
            addresses: [10.2.142.2/24]
            routes:
                - to: 10.2.142.0/24
                  via: 10.2.142.254
            nameservers:
                addresses: [1.1.1.1, 1.0.0.1, 8.8.8.8, 8.8.4.4]
        enp7s0:
            dhcp4: false
            addresses: [172.1.0.3/24]
            routes:
                - to: 172.1.0.0/24
                  via: 172.1.0.1
            nameservers:
                addresses: [1.1.1.1, 1.0.0.1, 8.8.8.8, 8.8.4.4]

version: 2

Estou esquecendo de algo na minha configuração? Preciso configurar mais alguma coisa para fazer isso funcionar?

eno1não está conectado a nenhuma rede no momento. ip routemostra o seguinte:

10.2.142.0/24 dev enp6s0 proto kernel scope link src
10.2.142.2 10.2.142.0/24 via 10.2.142.254 dev enp6s0 proto static
10.3.142.0/23 dev enp4s0 proto kernel scope link src
10.3.142.3 10.3.142.0/23 via 10.3.142.1 dev enp4s0 proto static
172.1.0.0/24 dev enp5s0 proto kernel scope link src
172.1.0.2 172.1.0.0/24 via 172.1.0.1 dev enp5s0 proto static

Todas as interfaces estão conectadas a diferentes roteadores, que têm diferentes ISPs e acesso à internet.

desculpe pelo feedback tardio, só consegui verificar essas configurações recentemente, parece que a tabela de roteamento estava faltando mesmo, obrigado

Não tenho conexão de rede com fio executando o Ubuntu 24.04 em um novo sistema com uma placa-mãe GIGABYTE X870 EAGLE WIFI7 (AM5, DDR5, M.2 PCIe 5.0, Wi-Fi 7).

O Bluetooth parece estar disponível, mas o "diálogo" do Bluetooth nas configurações não encontra nenhum dispositivo, apesar do telefone no qual estou digitando isso ter o Bluetooth habilitado.

Não havia rede durante a instalação. Então estou executando o que vem com 24.04.1 - nenhuma atualização feita.

O Windows 11 foi instalado na nova máquina e havia uma conexão, então imagino que o hardware esteja OK.

Ajuda.

Saída do script de informações sem fio: https://pastebin.ubuntu.com/p/dJJ8vvVc5W/

desde hoje, meu Thunderbird 128.7 não consegue se conectar a nenhum dos meus provedores de e-mail baseados em IMAP, dizendo que a conexão seria recusada. Tentei reinstalar o Thunderbird, mas sem sucesso.

Acho que o problema pode ser com o OpenSSL, mas não tenho certeza:

$ openssl s_client -connect imap.gmx.net:993
40674AC1B6760000:error:8000006F:system library:BIO_connect:Connection refused:../crypto/bio/bio_sock2.c:125:calling connect()
40674AC1B6760000:error:10000067:BIO routines:BIO_connect:connect error:../crypto/bio/bio_sock2.c:127:
40674AC1B6760000:error:8000006F:system library:BIO_connect:Connection refused:../crypto/bio/bio_sock2.c:125:calling connect()
40674AC1B6760000:error:10000067:BIO routines:BIO_connect:connect error:../crypto/bio/bio_sock2.c:127:
connect:errno=111

Logs do TCPDump ("Laubhaufen" é meu computador local):

19:00:31.179106 IP Laubhaufen.59062 > imap.gmx.net.imaps: Flags [S], seq 294025527, win 64240, options [mss 1460,sackOK,TS val 2359456286 ecr 0,nop,wscale 7], length 0
19:00:31.236708 IP imap.gmx.net.imaps > Laubhaufen.59062: Flags [R.], seq 0, ack 294025528, win 65535, length 0
19:00:31.236875 IP Laubhaufen.54472 > imap.gmx.net.imaps: Flags [S], seq 1928034102, win 64240, options [mss 1460,sackOK,TS val 831832553 ecr 0,nop,wscale 7], length 0
19:00:31.274870 IP imap.gmx.net.imaps > Laubhaufen.54472: Flags [R.], seq 0, ack 1928034103, win 65535, length 0

(embora "comprimento 0" esteja me confundindo)

Não parece ser um problema com o OpenSSL em si, já que ele se conecta bem ao https:

$ openssl s_client -connect www.gmx.net:443
CONNECTED(00000003)
[...]

gnutls também falha na conexão com IMAP:

gnutls-cli -s imap.gmx.de -p 993
Processed 146 CA certificate(s).
Resolving 'imap.gmx.de:993'...
Connecting to '212.227.17.170:993'...
Connecting to '212.227.17.186:993'...
Could not connect to 212.227.17.186:993: Connection refused

Depois de falhar também com GnuTLS e também para vários outros servidores IMAP, suspeito de um problema de firewall, mas não tenho um firewall que eu saiba, além de iptablesmas não alterei a configuração do iptables, hmm. Alguma ideia de como eu poderia depurar isso?

Informações do sistema: Estou executando o Ubuntu com base no bookworm/sid com o OpenSSL versão 3.0.2, gnutls-3.7.3

Instalei o Ubuntu 24.04.1 LTS em um Mac Mini 2018. Ele diz que o wifi não pode ser encontrado. Eu verifiquei:

Instalando drivers Broadcom Wireless

E parece que não tem meu modelo 14e4.

lspci -nn -d 14e4: mostrou:

03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4364 802.11ac Wireless Network Adapter [14e4:4464] (rev 03)

iwconfig mostrou:

lo        no wireless extensions.
eth0      no wireless extensions.