Existe uma maneira, na linha de comando, dado um endereço MAC de uma interface de rede local na máquina atual (por exemplo 01:23:45:67:89:ab
), para determinar se essa interface é WiFi ou com fio?
Estou tentando fazer isso em um script de shell.
Existe uma maneira, na linha de comando, dado um endereço MAC de uma interface de rede local na máquina atual (por exemplo 01:23:45:67:89:ab
), para determinar se essa interface é WiFi ou com fio?
Estou tentando fazer isso em um script de shell.
Como desenvolvedor, estou tentando configurar convidados VM no host Ubuntu 22 (virtualbox) para poder acessar a Internet. A diferença é que não estou executando um roteador externo na mesma sub-rede privada, então suponho que também preciso configurar uma funcionalidade de "roteador/gateway" no host para conectar corretamente os dois mundos (?).
Para lhe dar um contexto, estou tentando migrar minha configuração atual (antiga), que é assim:
(Internet) <--> asus router (static public ip a.b.c.d, gateway + dhcp for internal subnet 192.168.84.1) <--> ubuntu host (192.168.84.107) <--> vm guests (192.168.84.xxx)
A configuração no host atual (antigo) é uma ponte simples (encapsulando o eth0 físico), gateway configurado para 192.168.84.1 (o roteador asus), tudo funciona perfeitamente.
Meu novo host está localizado em outro lugar (e é uma VM em si, então na verdade estou fazendo uma virtualização aninhada agora, mas acho que não é relevante para esta questão), tenho seu próprio ip público (abc132/25) e usando um controle remoto porta de entrada (abc129). Portanto, não há roteador 192.168.84.1 para apontar o vms (usando 192.168.84.xxx) para:
(Internet) <--> external router (a.b.c.129) <--> ubuntu host (public IP a.b.c.132/25) <--> vm guests (192.168.84.xxx)
O que eu tentei (editarei a pergunta e fornecerei netplan, ifconfig, ip route e outros dumps, se necessário, mas por enquanto estou apenas perguntando se o que estou tentando fazer é possível):
editei o netplan: removi todas as configurações da interface "eth0", criei a ponte "br0" encapsulando-a e coloquei as configurações lá (endereços, servidores de nomes, rotas). Também adicionei o ip 192.168.84.1 aos endereços, então agora br0 tem dois ips (o público original abc132/25 e o gateway de sub-rede 192.168.84.1/24)
configure a VM para usar o adaptador em ponte (e atribua a eles ips estáticos 192.168.84.x)
instalei o servidor isc dhcp e configurei-o para gerenciar a interface "br0" e a sub-rede 192.168.84.0 (máscara 255.255.255.0), usando o roteador 192.168.84.1
Status atual:
From 192.168.84.1: icmp_seq=3 Redirect Host(New nexthop: a.b.c.129)
Presumo que esteja faltando uma peça conectando o dhcp/roteamento local ao gateway externo, mas estou ficando sem ideias (e permutações) sobre o que mudar e onde.
Qualquer ajuda seria muito apreciada!
Obrigado.
Estou tentando me conectar a um servidor VPN que hospeda um certificado TLS autoassinado usando o cliente VPN OpenConnect. A autenticação na VPN está por trás do Microsoft SSO.
Quando tento me conectar à VPN (Configurações-> Rede-> VPN), aparece um pop-up do navegador (o processo é na verdade /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess) onde posso fazer login usando SSO, mas uma mensagem 'Certificado TLS inaceitável' aparece na janela pop-up.
/usr/local/share/ca-certificates/extra/
e executei sudo update-ca-certificates --fresh
.Clearing symlinks in /etc/ssl/certs...
done.
Updating certificates in /etc/ssl/certs...
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
138 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Eu verifiquei manualmente - o certificado foi anexado a/etc/ssl/certs/ca-certificates.crt
openconnect
ferramenta cli, existe um parâmetro para passar o certificado sha --servercert
. Mas isso está no cli. Não tenho certeza se existe algo semelhante para a GUI do gerenciador de rede openconnect.SO: Ubuntu 23.10
OpenConnect Versão: v9.12-1
. Usando GnuTLS 3.8.1
.
Comprei um mini pc com wifi e bluetooth mas por mais que eu tente o wifi não aparece. Funciona no Windows 10 após a instalação dos drivers, mas infelizmente não no Ubuntu.
drivers do Windows: https://ftp.csl-computer.com/pub/drivers/mini-pc/CSL_Narrow_Box/51194_52233_52852/
Eu tentei algumas coisas, como esta: Driver WiFi não encontrado no Mini PC (Ubuntu 18.04) ou adaptador sem fio PCIe BCM43455 não reconhecido
Mini pc: https://www.amazon.de/-/en/Mini-PC-QuadCore-DDR3-RAM-Bluetooth/dp/B01LT46CVG
Mas não funcionou. Eu não faço ideia. Eu quero usar o Ubuntu, por causa do assistente doméstico. Qualquer ideia? Para ser honesto, não sou um guru do Linux, sou muito novo nisso.
editar: arquivo de log sem fio:
########## wireless info START ##########
Report from: 13 Apr 2024 16:04 CEST +0200
Booted last: 13 Apr 2024 00:00 CEST +0200
Script from: 25 Jan 2020 03:34 UTC +0000
##### release ###########################
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
##### kernel ############################
Linux 6.5.0-27-generic #28~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 15 10:51:06 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Parameters: ro, quiet, splash, vt.handoff=7
##### desktop ###########################
Ubuntu
##### lspci #############################
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:0123]
Kernel driver in use: r8169
##### lsusb #############################
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard
Bus 001 Device 002: ID 1bcf:08a0 Sunplus Innovation Technology Inc. Gaming mouse [Philips SPK9304]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
##### PCMCIA card info ##################
##### rfkill ############################
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
##### secure boot #######################
This system doesn't support Secure Boot
##### lsmod #############################
wl 6488064 0
mac80211 1720320 0
libarc4 12288 1 mac80211
brcmutil 24576 0
cfg80211 1323008 2 wl,mac80211
wmi 40960 1 video
##### interfaces ########################
##### ifconfig ##########################
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback <MAC address> brd <MAC address>
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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether <MAC 'enp1s0' [IF1]> brd <MAC address>
inet 192.168.1.175/24 brd 192.168.1.255 scope global dynamic noprefixroute enp1s0
valid_lft 41280sec preferred_lft 41280sec
inet6 fd0d:3d1f:3198::82c/128 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fd0d:3d1f:3198:0:ac1c:b926:537:1e54/64 scope global temporary dynamic
valid_lft 602881sec preferred_lft 83990sec
inet6 fd0d:3d1f:3198:0:e366:5056:16ca:84ce/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::6fd1:96f8:2d60:10c8/64 scope link noprefixroute
valid_lft forever preferred_lft forever
##### iwconfig ##########################
lo no wireless extensions.
enp1s0 no wireless extensions.
##### route #############################
default via 192.168.1.1 dev enp1s0 proto dhcp metric 100
169.254.0.0/16 dev enp1s0 scope link metric 1000
192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.175 metric 100
##### resolv.conf #######################
[777 root '/etc/resolv.conf' -> '../run/systemd/resolve/stub-resolv.conf']
nameserver 127.0.0.53
options edns0 trust-ad
search lan
##### network managers ##################
Installed:
NetworkManager
Running:
root 495 1 0 15:32 ? 00:00:01 /usr/sbin/NetworkManager --no-daemon
##### NetworkManager info ###############
GENERAL.DEVICE: enp1s0
GENERAL.TYPE: ethernet
GENERAL.NM-TYPE: NMDeviceEthernet
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/Devices/2
GENERAL.VENDOR: Realtek Semiconductor Co., Ltd.
GENERAL.PRODUCT: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
GENERAL.DRIVER: r8169
GENERAL.DRIVER-VERSION: 6.5.0-27-generic
GENERAL.FIRMWARE-VERSION: --
GENERAL.HWADDR: <MAC 'enp1s0' [IF1]>
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.REASON: 0 (No reason given)
GENERAL.IP4-CONNECTIVITY: 4 (full)
GENERAL.IP6-CONNECTIVITY: 3 (limited)
GENERAL.UDI: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/enp1s0
GENERAL.PATH: pci-0000:01:00.0
GENERAL.IP-IFACE: enp1s0
GENERAL.IS-SOFTWARE: no
GENERAL.NM-MANAGED: yes
GENERAL.AUTOCONNECT: yes
GENERAL.FIRMWARE-MISSING: no
GENERAL.NM-PLUGIN-MISSING: no
GENERAL.PHYS-PORT-ID: --
GENERAL.CONNECTION: 1. vezetékes kapcsolat
GENERAL.CON-UUID: 205b93db-b859-333e-bea0-6afef0bedff2
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
GENERAL.METERED: no (guessed)
CAPABILITIES.CARRIER-DETECT: yes
CAPABILITIES.SPEED: 1000 Mb/s
CAPABILITIES.IS-SOFTWARE: no
CAPABILITIES.SRIOV: no
INTERFACE-FLAGS.UP: yes
INTERFACE-FLAGS.LOWER-UP: yes
INTERFACE-FLAGS.CARRIER: yes
INTERFACE-FLAGS.PROMISC: no
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 192.168.1.175/24
IP4.GATEWAY: 192.168.1.1
IP4.ROUTE[1]: dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.ROUTE[3]: dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 100
IP4.DNS[1]: 192.168.1.1
IP4.DOMAIN[1]: lan
DHCP4.OPTION[1]: broadcast_address = 192.168.1.255
DHCP4.OPTION[2]: dhcp_lease_time = 43200
DHCP4.OPTION[3]: dhcp_server_identifier = 192.168.1.1
DHCP4.OPTION[4]: domain_name = lan
DHCP4.OPTION[5]: domain_name_servers = 192.168.1.1
DHCP4.OPTION[6]: expiry = 1713058358
DHCP4.OPTION[7]: host_name = sanyi-Narrow-Box-4K-4GB
DHCP4.OPTION[8]: ip_address = 192.168.1.175
DHCP4.OPTION[9]: next_server = 192.168.1.1
DHCP4.OPTION[10]: requested_broadcast_address = 1
DHCP4.OPTION[11]: requested_domain_name = 1
DHCP4.OPTION[12]: requested_domain_name_servers = 1
DHCP4.OPTION[13]: requested_domain_search = 1
DHCP4.OPTION[14]: requested_host_name = 1
DHCP4.OPTION[15]: requested_interface_mtu = 1
DHCP4.OPTION[16]: requested_ms_classless_static_routes = 1
DHCP4.OPTION[17]: requested_nis_domain = 1
DHCP4.OPTION[18]: requested_nis_servers = 1
DHCP4.OPTION[19]: requested_ntp_servers = 1
DHCP4.OPTION[20]: requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[21]: requested_root_path = 1
DHCP4.OPTION[22]: requested_routers = 1
DHCP4.OPTION[23]: requested_static_routes = 1
DHCP4.OPTION[24]: requested_subnet_mask = 1
DHCP4.OPTION[25]: requested_time_offset = 1
DHCP4.OPTION[26]: requested_wpad = 1
DHCP4.OPTION[27]: routers = 192.168.1.1
DHCP4.OPTION[28]: subnet_mask = 255.255.255.0
IP6.ADDRESS[1]: fd0d:3d1f:3198:0:ac1c:b926:537:1e54/64
IP6.ADDRESS[2]: fd0d:3d1f:3198::82c/128
IP6.ADDRESS[3]: fd0d:3d1f:3198:0:e366:5056:16ca:84ce/64
IP6.ADDRESS[4]: fe80::6fd1:96f8:2d60:10c8/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 1024
IP6.ROUTE[2]: dst = fd0d:3d1f:3198::/64, nh = ::, mt = 100
IP6.ROUTE[3]: dst = fd0d:3d1f:3198::/48, nh = fe80::1a34:afff:fe00:2c88, mt = 100
IP6.ROUTE[4]: dst = fd0d:3d1f:3198::82c/128, nh = ::, mt = 100
IP6.DNS[1]: fd0d:3d1f:3198::1
IP6.SEARCHES[1]: lan
DHCP6.OPTION[1]: dhcp6_domain_search = lan
DHCP6.OPTION[2]: dhcp6_name_servers = fd0d:3d1f:3198::1
DHCP6.OPTION[3]: ip6_address = fd0d:3d1f:3198::82c
CONNECTIONS.AVAILABLE-CONNECTION-PATHS: /org/freedesktop/NetworkManager/Settings/1
CONNECTIONS.AVAILABLE-CONNECTIONS[1]: 205b93db-b859-333e-bea0-6afef0bedff2 | 1. vezetékes kapcsolat
##### NetworkManager.state ##############
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
##### NetworkManager config #############
[[/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf]]
[connection]
wifi.powersave = 3
[[/etc/NetworkManager/NetworkManager.conf]]
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
[device]
wifi.scan-rand-mac-address=no
[[/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf]]
[main]
dns=systemd-resolved
[[/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf]]
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma
[[/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf]]
[connectivity]
uri=http://connectivity-check.ubuntu.com./
[[/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf]]
[device-31-mac-addr-change]
match-device=driver:eagle_sdio,driver:wl
wifi.scan-rand-mac-address=no
##### NetworkManager profiles ###########
##### Netplan config ####################
[/etc/netplan/01-network-manager-all.yaml]
network:
version: 2
renderer: NetworkManager
##### iw reg get ########################
'iw' is not installed (package "iw").
##### iwlist channels ###################
lo no frequency information.
enp1s0 no frequency information.
##### iwlist scan #######################
lo Interface doesn't support scanning.
enp1s0 Interface doesn't support scanning.
##### module infos ######################
[wl]
filename: /lib/modules/6.5.0-27-generic/updates/dkms/wl.ko
license: MIXED/Proprietary
depends: cfg80211
retpoline: Y
name: wl
vermagic: 6.5.0-27-generic SMP preempt mod_unload modversions
parm: passivemode:int
parm: wl_txq_thresh:int
parm: oneonly:int
parm: piomode:int
parm: instance_base:int
parm: nompc:int
parm: intf_name:string
[mac80211]
filename: /lib/modules/6.5.0-27-generic/kernel/net/mac80211/mac80211.ko
license: GPL
description: IEEE 802.11 subsystem
depends: cfg80211,libarc4
retpoline: Y
intree: Y
name: mac80211
vermagic: 6.5.0-27-generic SMP preempt mod_unload modversions
parm: minstrel_vht_only:Use only VHT rates when VHT is supported by sta. (bool)
parm: max_nullfunc_tries:Maximum nullfunc tx tries before disconnecting (reason 4). (int)
parm: max_probe_tries:Maximum probe tries before disconnecting (reason 4). (int)
parm: beacon_loss_count:Number of beacon intervals before we decide beacon was lost. (int)
parm: probe_wait_ms:Maximum time(ms) to wait for probe response before disconnecting (reason 4). (int)
parm: ieee80211_default_rc_algo:Default rate control algorithm for mac80211 to use (charp)
[brcmutil]
filename: /lib/modules/6.5.0-27-generic/kernel/drivers/net/wireless/broadcom/brcm80211/brcmutil/brcmutil.ko
license: Dual BSD/GPL
description: Broadcom 802.11n wireless LAN driver utilities.
depends:
retpoline: Y
intree: Y
name: brcmutil
vermagic: 6.5.0-27-generic SMP preempt mod_unload modversions
[cfg80211]
filename: /lib/modules/6.5.0-27-generic/kernel/net/wireless/cfg80211.ko
description: wireless configuration support
license: GPL
depends:
retpoline: Y
intree: Y
name: cfg80211
vermagic: 6.5.0-27-generic SMP preempt mod_unload modversions
parm: bss_entries_limit:limit to number of scan BSS entries (per wiphy, default 1000) (int)
parm: ieee80211_regdom:IEEE 802.11 regulatory domain code (charp)
parm: cfg80211_disable_40mhz_24ghz:Disable 40MHz support in the 2.4GHz band (bool)
##### module parameters #################
[mac80211]
beacon_loss_count: 7
ieee80211_default_rc_algo: minstrel_ht
max_nullfunc_tries: 2
max_probe_tries: 5
minstrel_vht_only: Y
probe_wait_ms: 500
[cfg80211]
bss_entries_limit: 1000
cfg80211_disable_40mhz_24ghz: N
ieee80211_regdom: 00
##### /etc/modules ######################
##### modprobe options ##################
[/etc/modprobe.d/amd64-microcode-blacklist.conf]
blacklist microcode
[/etc/modprobe.d/blacklist-ath_pci.conf]
blacklist ath_pci
[/etc/modprobe.d/blacklist-bcm43.conf]
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist bcm43xx
blacklist brcm80211
blacklist brcmfmac
blacklist brcmsmac
blacklist bcma
[/etc/modprobe.d/blacklist.conf]
blacklist evbug
blacklist usbmouse
blacklist usbkbd
blacklist eepro100
blacklist de4x5
blacklist eth1394
blacklist snd_intel8x0m
blacklist snd_aw2
blacklist prism54
blacklist bcm43xx
blacklist garmin_gps
blacklist asus_acpi
blacklist snd_pcsp
blacklist pcspkr
blacklist amd76x_edac
blacklist brcmsmac
blacklist bcma
[/etc/modprobe.d/blacklist-rare-network.conf]
alias net-pf-3 off
alias net-pf-6 off
alias net-pf-9 off
alias net-pf-11 off
alias net-pf-12 off
alias net-pf-19 off
alias net-pf-21 off
alias net-pf-36 off
[/etc/modprobe.d/broadcom-sta-common.conf]
blacklist b43
blacklist b43legacy
blacklist b44
blacklist bcma
blacklist brcm80211
blacklist brcmsmac
blacklist ssb
[/etc/modprobe.d/intel-microcode-blacklist.conf]
blacklist microcode
[/etc/modprobe.d/iwlwifi.conf]
remove iwlwifi \
(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \
&& /sbin/modprobe -r mac80211
##### rc.local ##########################
grep: /etc/rc.local: No such file or directory
##### pm-utils ##########################
##### udev rules ########################
##### dmesg #############################
[ 11.926484] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 14.010492] r8169 0000:01:00.0 enp1s0: Link is Down
[ 16.649536] r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control off
[ 560.702923] wl: loading out-of-tree module taints kernel.
[ 560.702942] wl: module license 'MIXED/Proprietary' taints kernel.
[ 560.702950] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 560.702953] wl: module license taints kernel.
########## wireless info END ############
Atualização 04/10/2024: Este não foi um vazamento real. Veja a resposta aceita de mpboden abaixo.
O problema:
Estou conectado a um wifi estrangeiro no Kubuntu Desktop 22.04 e quero configurar o DNS em todo o sistema para 9.9.9.9 (quad9) com DNSOverTLS. No entanto, em dnsleaktest.com ainda recebo um DNS diferente.
Testei com o Firefox com "DNS sobre HTTPS" definido como Desativado.
Em https://on.quad9.net recebo conforme o esperado :YES, You ARE using quad9
No dnsleaktest.com, porém, recebo o resultado não executado :
Aqui está o que eu fiz:
No NetworkManager para o wifi afetado, desabilitei o IPv6 e configurei o IPv4 como Automático (somente endereços) e coloquei uma lista vazia como servidor DNS. A configuração resultante no terminal é:
$ nmcli device
DEVICE TYPE STATE CONNECTION
wlo1 wifi connected TP-LINK_58DE
p2p-dev-wlo1 wifi-p2p disconnected --
lo loopback unmanaged --
$ nmcli device show wlo1
GENERAL.DEVICE: wlo1
GENERAL.TYPE: wifi
GENERAL.HWADDR: xx:xx:xx:xx:xx:xx
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: TP-LINK_58DE
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
IP4.ADDRESS[1]: 192.168.0.112/24
IP4.GATEWAY: 192.168.0.1
IP4.ROUTE[1]: dst = 192.168.0.0/24, nh = 0.0.0.0, mt = 600
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.0.1, mt = 600
IP4.ROUTE[3]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP6.GATEWAY: --
Eu configurei /etc/systemd/resolved.conf como tal (apenas as últimas linhas são relevantes, mas para verificação de integridade/erro forneço o arquivo completo):
$ cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.
[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google: 8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9: 9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
#DNS=
#FallbackDNS=
#Domains=
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=no
#LLMNR=no
#Cache=no-negative
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no
DNS=9.9.9.9#dns.quad9.net
FallbackDNS=9.9.9.9#dns.quad9.net
Domains=~.
DNSSEC=yes
DNSOverTLS=yes
Depois de sudo systemctl restart systemd-resolved
e sudo systemctl restart NetworkManager
, esta é a configuração resultante (toda a saída é colada aqui):
$ resolvectl status
Global
Protocols: -LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported
resolv.conf mode: foreign
Current DNS Server: 9.9.9.9#dns.quad9.net
DNS Servers: 9.9.9.9#dns.quad9.net
Fallback DNS Servers: 9.9.9.9#dns.quad9.net
DNS Domain: ~.
Link 2 (wlo1)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported
Em testes básicos parece funcionar:
$ resolvectl query archlinux.com
archlinux.com: 3.64.163.50 -- link: wlo1
-- Information acquired via protocol DNS in 1.1292s.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: yes
-- Data from: cache network
$ dig archlinux.com
; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> archlinux.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60948
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;archlinux.com. IN A
;; ANSWER SECTION:
archlinux.com. 7200 IN A 3.64.163.50
;; Query time: 331 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sat Apr 06 09:30:08 CEST 2024
;; MSG SIZE rcvd: 58
$ ss -tuna | grep :853
tcp TIME-WAIT 0 0 192.168.0.112:48420 9.9.9.9:853
tcp ESTAB 0 0 192.168.0.112:49032 9.9.9.9:853
A questão restante é: Por que obtenho um DNS diferente em dnsleaktest.com?
Algumas coisas que tentei:
sudo resolvectl flush-caches
sudo resolvconf -u
dns=none
às seções [principais] de /etc/NetworkManager/NetworkManager.conf
e/etc/NetworkManager/conf.d/90-dns-none.conf
sudo systemctl restart systemd-resolved
sudo systemctl restart NetworkManager
cd /etc/
mv resolv.conf resolv.conf-old
ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo dpkg-reconfigure resolvconf
. Isto resulta em:$ ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Apr 8 09:10 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
Nada ainda ajudou. Você pode me ajudar a resolver isso?
Executei o seguinte sudo find / -type f -name "*.network" -not -path "/var/lib/docker/*"
para mostrar todos os .network
arquivos em uma nova instalação do servidor 22.04.
Além dos .network
arquivos abaixo, /run/systemd/network/
não vejo nenhum outro .network
arquivo no sistema.
Dado que /run
é tempfs
, onde está a configuração que posso ver nos .network
arquivos /run/systemd/network/
vindos, padrões codificados no código-fonte do networkd?
Eu tenho um problema desconcertante em uma instalação relativamente nova do Ubuntu 22.04. Percebi hoje que a internet estava muito lenta no meu laptop, mas não no meu telefone ou em outros laptops do apartamento. Depois de algumas investigações, percebi que sempre que a conexão de rede caía, um processo era chamado kworker/28:2+events
usando 100% da CPU quando executava o top
.
Depois de verificar /var/log/kern.log
, percebi que havia uma mensagem sempre que o kworker
processo aparecia:
... ieee80211 phy0: Hardware restart was requested
Isso parece acontecer toda vez que tento fazer qualquer tipo de conexão. Além disso, e de forma um tanto inesperada, sempre que executo um sudo
comando enquanto o kworker
processo está ativo, o sudo
comando trava até que o kworker
processo termine.
Meu entendimento é que esses tipos de problemas geralmente estão relacionados ao kernel e a algum tipo de bug dentro dele. Percebo no meu atualizador de software que há atualizações de kernel disponíveis, então obviamente quero tentar obter essas atualizações, mas... quando tento fazer isso, sou atingido pelo problema de redefinição de hardware.
Estou desesperado para consertar isso o mais rápido possível, mas não tenho ideia de para onde ir a partir daqui. Alguma ideia?
Prezada comunidade Ubuntu,
Estou encontrando um problema persistente com meu sistema Ubuntu 23.10 relacionado à funcionalidade WiFi. Embora a conexão WiFi em si funcione perfeitamente, tentar desligar o WiFi faz com que todo o sistema congele. Quaisquer comandos envolvendo sudo ou NetworkManager fazem com que o terminal pare de responder.
Ao investigar os logs do sistema usando o journalctl, encontro consistentemente a seguinte mensagem de erro:
kernel: iwlwifi 0000:02:00.0: A fila 5 está ativa no fifo 3 e travada por 10.000 ms. SW [6, 7] HW [7, 7] FH TRB=0x080305006
Na tentativa de resolver esse problema, segui uma solução sugerida no Ubuntu Ask, que envolvia modificar a configuração do GRUB. Os passos que segui foram:
Opened the GRUB configuration file using the command: sudo nano /etc/default/grub.
Modified the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to include net.ipv4.tcp_ecn=0.
Saved the changes (Ctrl+o) and exited nano (Ctrl+x).
Updated GRUB using the command: sudo update-grub.
Porém, apesar de implementar esta solução, o problema persiste e o mesmo erro continua ocorrendo.
Uma investigação mais aprofundada me levou a outra solução potencial envolvendo a verificação da integridade do arquivo de firmware iwlwifi-3160-17.ucode. No entanto, encontrei uma discrepância ao descobrir que o arquivo em meu sistema se chama iwlwifi-3160-17.ucode.zst e o hash que obtive (efa40dcbabe15f74f4763d7534419752) difere do hash esperado (fee0d7dddf8437148ab25c4b1a34202c).
Além disso, tentei executar o comando sudo sysctl -w net.ipv4.tcp_ecn=0 como parte de uma solução diferente, mas infelizmente não resolveu o problema.
Percebi que se eu desligar e ligar o WiFi usando o comando sudo systemctl stop NetworkManager e depois sudo systemctl start NetworkManager, ele funciona perfeitamente sem causar congelamento do sistema.
Mais uma coisa a notar é que ao usar um USB inicializável para executar o Ubuntu no modo ‘Try Ubuntu’ sem instalar, posso ligar ou desligar o WiFi normalmente sem encontrar esse problema. Enfrentei esse erro no Ubuntu 22 e depois de apagar todos os meus dados e instalar o Ubuntu 23, encontrei o mesmo erro.
Obrigado pela sua atenção e apoio.
Estou tentando conectar o servidor Ubuntu 22.04 à Internet em um RaspberryPi 3B+ usando um modem USB 4G e netplan.
O dongle USB parece ser reconhecido:
carlo@pi-box:~$ lsusb
Bus 001 Device 008: ID 19d2:0016 ZTE WCDMA Technologies MSM ZTE Mobile Broadband
carlo@pi-box:~$ sudo dmesg | grep usb
[ 423.387073] usb 1-1.3: new high-speed USB device number 10 using dwc2
[ 423.497368] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=0016, bcdDevice=54.24
[ 423.497428] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 423.497452] usb 1-1.3: Product: ZTE Mobile Broadband
[ 423.497474] usb 1-1.3: Manufacturer: ZTE,Incorporated
[ 423.500645] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB0
[ 423.502143] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB1
[ 423.503982] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB2
A configuração do netplan é:
network:
renderer: NetworkManager
ethernets:
eth0:
dhcp4: true
optional: true
usb0:
dhcp4: true
optional: true
modems:
ttyUSB2:
apn: mobile.vodafone.it
dhcp4: true
auto-config: true
version: 2
Com o ifconfig -a
comando não encontro interface.
O gerenciador de modem parece reconhecer o modem:
carlo@pi-box:~$ mmcli -L
/org/freedesktop/ModemManager1/Modem/1 [ZTE CORPORATION] MF833V
carlo@pi-box:~$ mmcli -m 1
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/1
| device id: c22dd449a679d1e0ad941d57c707e8fbabaf3ee4
--------------------------------
Hardware | manufacturer: ZTE CORPORATION
| model: MF833V
| firmware revision: BD_CNGENMF833VV1.0.0B08
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 860493042386496
--------------------------------
System | device: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3
| drivers: option
| plugin: zte
| primary port: ttyUSB2
| ports: ttyUSB0 (qcdm), ttyUSB1 (at), ttyUSB2 (at)
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10)
| state: registered
| power state: on
| access tech: umts
| signal quality: 41% (recent)
--------------------------------
Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g, 4g; preferred: none
| current: allowed: any; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 860493042386496
| operator id: 22288
| operator name: 0046003 0046003
| registration: home
| packet service state: attached
--------------------------------
3GPP EPS | ue mode of operation: csps-1
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1
O gerenciador de rede mostra o dispositivo e a conexão:
carlo@pi-box:~$ nmcli
ttyUSB2: disconnected
"ZTE Mobile Broadband"
1 connection available
gsm (option), hw
carlo@pi-box:~$ nmcli c
NAME UUID TYPE DEVICE
netplan-ttyUSB2 5b6fbb52-0291-359e-aa68-b49f69ba9ff2 gsm --
Se eu forçar a conexão do modem, parece bem-sucedido:
carlo@pi-box:~$ sudo mmcli -m 1 --simple-connect="apn=apn.fastweb.it"
successfully connected the modem
carlo@pi-box:~$ mmcli -m 1
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/1
| device id: c22dd449a679d1e0ad941d57c707e8fbabaf3ee4
--------------------------------
Hardware | manufacturer: ZTE CORPORATION
| model: MF833V
| firmware revision: BD_CNGENMF833VV1.0.0B08
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 860493042386496
--------------------------------
System | device: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3
| drivers: option
| plugin: zte
| primary port: ttyUSB2
| ports: ttyUSB0 (qcdm), ttyUSB1 (at), ttyUSB2 (at)
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10)
| state: connected
| power state: on
| access tech: umts
| signal quality: 38% (recent)
--------------------------------
Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g, 4g; preferred: none
| current: allowed: any; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 860493042386496
| operator id: 22288
| operator name: 0046003 0046003
| registration: home
| packet service state: attached
--------------------------------
3GPP EPS | ue mode of operation: csps-1
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1
--------------------------------
Bearer | paths: /org/freedesktop/ModemManager1/Bearer/0
carlo@pi-box:~$ mmcli -b 0
---------------------------------
General | path: /org/freedesktop/ModemManager1/Bearer/0
| type: default
---------------------------------
Status | connected: yes
| suspended: no
| multiplexed: no
| interface: ttyUSB2
| ip timeout: 20
| profile id: 2
---------------------------------
Properties | apn: apn.fastweb.it
| roaming: allowed
---------------------------------
IPv4 configuration | method: ppp
| prefix: 0
---------------------------------
Statistics | start date: 2024-03-05T21:26:00Z
| attempts: 1
Mas com o ifconfig -a
comando ainda não consegui encontrar nenhuma interface relacionada.
Se eu tentar conectá-lo sinalizará um erro no APN:
carlo@pi-box:~$ sudo nmcli c up netplan-ttyUSB2
Error: Connection activation failed: Failed to select the specified APN
Hint: use 'journalctl -xe NM_CONNECTION=5b6fbb52-0291-359e-aa68-b49f69ba9ff2 + NM_DEVICE=ttyUSB2' to get more details.
As propriedades da conexão são:
carlo@pi-box:~$ sudo nmcli c show netplan-ttyUSB2
connection.id: netplan-ttyUSB2
connection.uuid: 5b6fbb52-0291-359e-aa68-b49f69ba9ff2
connection.stable-id: --
connection.type: gsm
connection.interface-name: ttyUSB2
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.multi-connect: 0 (default)
connection.auth-retries: -1
connection.timestamp: 0
connection.read-only: no
connection.permissions: --
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.metered: unknown
connection.lldp: default
connection.mdns: -1 (default)
connection.llmnr: -1 (default)
connection.dns-over-tls: -1 (default)
connection.wait-device-timeout: -1
ipv4.method: auto
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.addresses: --
ipv4.gateway: --
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.routing-rules: --
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-iaid: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.dhcp-hostname-flags: 0x0 (none)
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.required-timeout: -1 (default)
ipv4.dad-timeout: -1 (default)
ipv4.dhcp-vendor-class-identifier: --
ipv4.dhcp-reject-servers: --
ipv6.method: ignore
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: --
ipv6.dns-priority: 0
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.routing-rules: --
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.required-timeout: -1 (default)
ipv6.ip6-privacy: -1 (unknown)
ipv6.addr-gen-mode: eui64
ipv6.ra-timeout: 0 (default)
ipv6.dhcp-duid: --
ipv6.dhcp-iaid: --
ipv6.dhcp-timeout: 0 (default)
ipv6.dhcp-send-hostname: yes
ipv6.dhcp-hostname: --
ipv6.dhcp-hostname-flags: 0x0 (none)
ipv6.token: --
gsm.auto-config: yes
gsm.number: --
gsm.username: --
gsm.password: <hidden>
gsm.password-flags: 0 (none)
gsm.apn: --
gsm.network-id: --
gsm.pin: <hidden>
gsm.pin-flags: 0 (none)
gsm.home-only: no
gsm.device-id: --
gsm.sim-id: --
gsm.sim-operator-id: --
gsm.mtu: auto
proxy.method: none
proxy.browser-only: no
proxy.pac-url: --
proxy.pac-script: --
O que estou fazendo de errado? Alguém tem experiência nesta configuração?
No servidor, executando Ubuntu 22.04
sudo netstat -tnlp | grep :4000
tcp 0 0 0.0.0.0:4000 0.0.0.0:* LISTEN 10690/nxd
tcp6 0 0 :::4000 :::* LISTEN 10690/nxd
O serviço responde à solicitação HTTP:
curl localhost:4000
curl: (52) Empty reply from server
ufw está desabilitado
sudo ufw status
Status: inactive
Da máquina cliente (mesma sub-rede):
nc -zv 192.168.1.111 4000
nc: connect to 192.168.1.111 port 4000 (tcp) failed: No route to host
SSh está habilitado
nc -zv 192.168.1.111 22
Connection to 192.168.1.111 22 port [tcp/ssh] succeeded!
Ping funciona:
ping 192.168.1.111
PING 192.168.1.111 (192.168.1.111) 56(84) bytes of data.
64 bytes from 192.168.1.111: icmp_seq=1 ttl=64 time=309 ms