Non hai allegato un file di testo (.txt) . Hai allegato un file Open Document Text (.odt) e io in questo momento non posso aprirlo ...pepox [url=http://forum.ubuntu-it.org/viewtopic.php?p=4982743#p4982743][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto: ho allegato il file di testo come mi ha detto. non va bene??
[Risolto]wireless : problema di connessione
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
Codice: Seleziona tutto
nmcli connection
Dai il comando
Codice: Seleziona tutto
nmcli connection show "NOME DELLA CONNESSIONE"
Postami solo quest'ultimo output
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
Codice: Seleziona tutto
nmcli connection show "Digicom_A3D4"
connection.id: Digicom_A3D4
connection.uuid: 5e9f7b8e-9efb-4aab-a416-95ada4b9fe20
connection.interface-name: --
connection.type: 802-11-wireless
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.timestamp: 1495009383
connection.read-only: no
connection.permissions:
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (predefinito)
connection.secondaries:
connection.gateway-ping-timeout: 0
connection.metered: sconosciuto
connection.lldp: -1 (default)
802-11-wireless.ssid: Digicom_A3D4
802-11-wireless.mode: infrastructure
802-11-wireless.band: --
802-11-wireless.channel: 0
802-11-wireless.bssid: --
802-11-wireless.rate: 0
802-11-wireless.tx-power: 0
802-11-wireless.mac-address: B0:C0:90:8E:92:DD
802-11-wireless.cloned-mac-address: --
802-11-wireless.mac-address-blacklist:
802-11-wireless.mac-address-randomization:predefinito
802-11-wireless.mtu: auto
802-11-wireless.seen-bssids: 00:A0:A2:91:A3:D4
802-11-wireless.hidden: no
802-11-wireless.powersave: default (0)
802-11-wireless-security.key-mgmt: wpa-psk
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg: --
802-11-wireless-security.proto:
802-11-wireless-security.pairwise:
802-11-wireless-security.group:
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0: <nascosta>
802-11-wireless-security.wep-key1: <nascosta>
802-11-wireless-security.wep-key2: <nascosta>
802-11-wireless-security.wep-key3: <nascosta>
802-11-wireless-security.wep-key-flags: 0 (nessuno)
802-11-wireless-security.wep-key-type: 0 (sconosciuto)
802-11-wireless-security.psk: <nascosta>
802-11-wireless-security.psk-flags: 0 (nessuno)
802-11-wireless-security.leap-password: <nascosta>
802-11-wireless-security.leap-password-flags:0 (nessuno)
ipv4.method: auto
ipv4.dns:
ipv4.dns-search:
ipv4.dns-options: (predefinito)
ipv4.dns-priority: 0
ipv4.addresses:
ipv4.gateway: --
ipv4.routes:
ipv4.route-metric: -1
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (predefinito)
ipv6.method: ignore
ipv6.dns:
ipv6.dns-search:
ipv6.dns-options: (predefinito)
ipv6.dns-priority: 0
ipv6.addresses:
ipv6.gateway: --
ipv6.routes:
ipv6.route-metric: -1
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.ip6-privacy: -1 (sconosciuto)
ipv6.addr-gen-mode: stable-privacy
ipv6.dhcp-send-hostname: yes
ipv6.dhcp-hostname: --
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
Codice: Seleziona tutto
nmcli connection mod "Digicom_A3D4" connection.autoconnect false
Proviamo a disattivare il protocollo di rete IPv6 a livello di sistema ( a livello di connessione lo hai già fatto). Con un editor di testo in modalità amministratore apri il file /etc/sysctl.conf
Codice: Seleziona tutto
sudo gedit /etc/sysctl.conf
Codice: Seleziona tutto
# Disabilito IPv6 globalmente
net.ipv6.conf.all.disable_ipv6=1
Postami l'output di
Codice: Seleziona tutto
ifconfig
Codice: Seleziona tutto
cat /var/log/syslog | grep -i networkmanager
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
Codice: Seleziona tutto
ifconfig
enp2s0 Link encap:Ethernet IndirizzoHW d0:17:c2:2c:2b:d1
indirizzo inet:192.168.1.5 Bcast:192.168.1.255 Maschera:255.255.255.0
indirizzo inet6: fe80::7b03:cf96:2ce1:4e41/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:2572 (2.5 KB) Byte TX:8610 (8.6 KB)
lo Link encap:Loopback locale
indirizzo inet:127.0.0.1 Maschera:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:198 errors:0 dropped:0 overruns:0 frame:0
TX packets:198 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1
Byte RX:15188 (15.1 KB) Byte TX:15188 (15.1 KB)
wlp3s0 Link encap:Ethernet IndirizzoHW b0:c0:90:8e:92:dd
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:0 (0.0 B) Byte TX:0 (0.0 B)
Codice: Seleziona tutto
May 17 12:40:49 qwerty NetworkManager[845]: <info> [1495017649.6273] keyfile: update /etc/NetworkManager/system-connections/Digicom_A3D4 (5e9f7b8e-9efb-4aab-a416-95ada4b9fe20,"Digicom_A3D4")
May 17 12:40:49 qwerty NetworkManager[845]: <info> [1495017649.6282] audit: op="connection-update" uuid="5e9f7b8e-9efb-4aab-a416-95ada4b9fe20" name="Digicom_A3D4" pid=3580 uid=1000 result="success"
May 17 12:43:50 qwerty kernel: [ 13.370499] audit: type=1400 audit(1495017826.788:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=643 comm="apparmor_parser"
May 17 12:43:50 qwerty kernel: [ 13.370507] audit: type=1400 audit(1495017826.788:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=643 comm="apparmor_parser"
May 17 12:43:53 qwerty whoopsie[815]: [12:43:53] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.1861] NetworkManager (version 1.2.6) is starting...
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.2581] Read config: /etc/NetworkManager/NetworkManager.conf (etc: default-wifi-powersave-on.conf)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.3382] manager[0x101f1c0]: monitoring kernel firmware directory '/lib/firmware'.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.3383] monitoring ifupdown state file '/run/network/ifstate'.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.3545] dns-mgr[0xffe160]: init: dns=dnsmasq, rc-manager=resolvconf, plugin=dnsmasq
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.4611] rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/ieee80211/phy0/rfkill1) (driver rtl8821ae)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.4614] rfkill2: found WiFi radio killswitch (at /sys/devices/platform/asus-nb-wmi/rfkill/rfkill2) (platform driver asus-nb-wmi)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7543] init!
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7545] management mode: unmanaged
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7550] devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/enp2s0, iface: enp2s0)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7550] device added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/net/enp2s0, iface: enp2s0): no ifupdown configuration found.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7550] devices added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/net/wlp3s0, iface: wlp3s0)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7550] device added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/net/wlp3s0, iface: wlp3s0): no ifupdown configuration found.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7550] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7550] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7551] end _init.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7551] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.7551] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.8045] SettingsPlugin-Ofono: init!
May 17 12:43:55 qwerty NetworkManager[843]: <warn> [1495017835.8046] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.8046] SettingsPlugin-Ofono: end _init.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.8046] settings: loaded plugin ofono: (C) 2013-2016 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ofono.so)
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.8046] (17099600) ... get_connections.
May 17 12:43:55 qwerty NetworkManager[843]: <info> [1495017835.8046] (17099600) ... get_connections (managed=false): return empty list.
May 17 12:43:56 qwerty NetworkManager[843]: <info> [1495017836.0172] keyfile: new connection /etc/NetworkManager/system-connections/Digicom_A3D4 (5e9f7b8e-9efb-4aab-a416-95ada4b9fe20,"Digicom_A3D4")
May 17 12:43:56 qwerty NetworkManager[843]: <info> [1495017836.1637] keyfile: new connection /etc/NetworkManager/system-connections/Hotspot (d7fa1c8d-2912-40c3-8f52-cbdd07d91417,"Hotspot")
May 17 12:43:56 qwerty NetworkManager[843]: <info> [1495017836.2012] keyfile: new connection /etc/NetworkManager/system-connections/ASUS (d407710b-fc1e-4b81-98bc-c9561fd2644a,"ASUS")
May 17 12:43:56 qwerty NetworkManager[843]: <info> [1495017836.5716] keyfile: new connection /etc/NetworkManager/system-connections/Wireless-Cirillo (b781a4b6-f0eb-489c-9189-9072d3430a72,"Wireless-Cirillo")
May 17 12:43:57 qwerty NetworkManager[843]: <info> [1495017837.3865] keyfile: new connection /etc/NetworkManager/system-connections/Cirillo-Second (e524cea1-748a-499e-9b42-9171bd325c9c,"Cirillo-Second")
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.1213] keyfile: new connection /etc/NetworkManager/system-connections/Cirillo-School (191445c5-d918-4323-83d8-5cf8d1a7acfb,"Cirillo-School")
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5078] keyfile: new connection /etc/NetworkManager/system-connections/Cirillo-Wifi (cfdbe2b0-0f07-4d13-8ab9-c415a67b8e37,"Cirillo-Wifi")
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5096] SettingsPlugin-Ofono: (17099824) ... get_connections.
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5096] SettingsPlugin-Ofono: (17099824) connections count: 0
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5097] get unmanaged devices count: 0
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5115] settings: hostname: using hostnamed
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5115] settings: hostname changed from (none) to "qwerty"
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5117] Using DHCP client 'dhclient'
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5118] manager: WiFi enabled by radio killswitch; enabled by state file
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5118] manager: WWAN enabled by radio killswitch; enabled by state file
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5119] manager: Networking is enabled by state file
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5119] Loaded device plugin: NMVxlanFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5120] Loaded device plugin: NMVlanFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5120] Loaded device plugin: NMVethFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5120] Loaded device plugin: NMTunFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5120] Loaded device plugin: NMMacvlanFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5121] Loaded device plugin: NMIPTunnelFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5121] Loaded device plugin: NMInfinibandFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5121] Loaded device plugin: NMEthernetFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5122] Loaded device plugin: NMBridgeFactory (internal)
May 17 12:43:58 qwerty NetworkManager[843]: <info> [1495017838.5122] Loaded device plugin: NMBondFactory (internal)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.3753] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.3759] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.3769] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.4295] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.4299] (wlp3s0): using nl80211 for WiFi device control
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.4311] device (wlp3s0): driver supports Access Point (AP) mode
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.4732] manager: (wlp3s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/0)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.4747] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.7432] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.7732] keyfile: add connection in-memory (ca480e7e-0eaf-3fe5-9c89-e2cf42cb51f2,"Connessione via cavo 1")
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.7739] settings: (enp2s0): created default wired connection 'Connessione via cavo 1'
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.7750] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 17 12:44:00 qwerty NetworkManager[843]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.8355] device (lo): link connected
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.8366] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/2)
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.9104] urfkill disappeared from the bus
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.9119] bluez: use BlueZ version 5
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.9124] ofono is now available
May 17 12:44:00 qwerty NetworkManager[843]: <warn> [1495017840.9132] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
May 17 12:44:00 qwerty NetworkManager[843]: <info> [1495017840.9133] ModemManager available in the bus
May 17 12:44:01 qwerty NetworkManager[843]: <info> [1495017841.0625] supplicant: wpa_supplicant running
May 17 12:44:01 qwerty NetworkManager[843]: <info> [1495017841.0626] device (wlp3s0): supplicant interface state: init -> starting
May 17 12:44:01 qwerty NetworkManager[843]: <info> [1495017841.1259] device (wlp3s0): supplicant interface state: starting -> ready
May 17 12:44:01 qwerty NetworkManager[843]: <info> [1495017841.1260] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0946] device (enp2s0): link connected
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0951] device (enp2s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0959] policy: auto-activating connection 'Connessione via cavo 1'
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0973] device (enp2s0): Activation: starting connection 'Connessione via cavo 1' (ca480e7e-0eaf-3fe5-9c89-e2cf42cb51f2)
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0975] device (enp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0976] manager: NetworkManager state is now CONNECTING
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0983] device (enp2s0): state change: prepare -> config (reason 'none') [40 50 0]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.0990] device (enp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.1335] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.2806] dhcp4 (enp2s0): dhclient started with pid 997
May 17 12:44:03 qwerty NetworkManager[843]: <warn> [1495017843.2812] platform-linux: support: kernel-extended-ifa-flags: unable to detect kernel support for handling IPv6 temporary addresses. Assume support
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7111] address 192.168.1.5
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7111] plen 24 (255.255.255.0)
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7111] gateway 192.168.1.1
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7111] server identifier 192.168.1.1
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7111] lease time 86400
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7112] nameserver '192.168.1.1'
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7112] wins '192.168.1.1'
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7112] wins '192.168.1.1'
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7112] dhcp4 (enp2s0): state changed unknown -> bound
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7126] device (enp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7133] device (enp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7137] device (enp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.7138] manager: NetworkManager state is now CONNECTED_LOCAL
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.9773] manager: NetworkManager state is now CONNECTED_GLOBAL
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.9775] policy: set 'Connessione via cavo 1' (enp2s0) as default for IPv4 routing and DNS
May 17 12:44:03 qwerty NetworkManager[843]: <info> [1495017843.9776] dns-plugin[0x102d900]: starting dnsmasq...
May 17 12:44:04 qwerty NetworkManager[843]: <info> [1495017844.0187] dns-mgr: Writing DNS information to /sbin/resolvconf
May 17 12:44:04 qwerty NetworkManager[843]: <info> [1495017844.7500] device (enp2s0): Activation: successful, device activated.
May 17 12:44:04 qwerty NetworkManager[843]: <info> [1495017844.7527] device (wlp3s0): supplicant interface state: ready -> inactive
May 17 12:44:04 qwerty NetworkManager[843]: <info> [1495017844.7605] dnsmasq[0x102d900]: dnsmasq appeared as :1.28
May 17 12:44:04 qwerty whoopsie[815]: [12:44:04] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0
May 17 12:44:04 qwerty whoopsie[815]: [12:44:04] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0
May 17 12:44:04 qwerty whoopsie[815]: [12:44:04] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0
May 17 12:44:05 qwerty NetworkManager[843]: <info> [1495017845.4332] manager: WiFi hardware radio set enabled
May 17 12:44:05 qwerty NetworkManager[843]: <info> [1495017845.4332] manager: WWAN hardware radio set enabled
May 17 12:44:08 qwerty NetworkManager[843]: <info> [1495017848.4334] manager: startup complete
May 17 12:46:25 qwerty NetworkManager[843]: <info> [1495017985.8149] device (enp2s0): link disconnected (deferring action for 4 seconds)
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4362] device (enp2s0): link disconnected (calling deferred action)
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4368] device (enp2s0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4530] dhcp4 (enp2s0): canceled DHCP transaction, DHCP client pid 997
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4531] dhcp4 (enp2s0): state changed bound -> done
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4547] dns-mgr: Writing DNS information to /sbin/resolvconf
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4640] manager: NetworkManager state is now CONNECTED_LOCAL
May 17 12:46:30 qwerty NetworkManager[843]: <info> [1495017990.4644] manager: NetworkManager state is now DISCONNECTED
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
Hai il protocollo di rete IPv6 ancora attivo a livello di configurazione sulla connessione Ethernet. Se lo vuoi disabilitare puoi dare il comando
Codice: Seleziona tutto
nmcli connection mod "NOME DELLA CONNESSIONE" ipv6.method ignore
Codice: Seleziona tutto
ifconfig
[/Semi OT]
Mi serve un pò di tempo e calma per guardare il log, ci risentiamo ...
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
Codice: Seleziona tutto
ifconfig
enp2s0 Link encap:Ethernet IndirizzoHW d0:17:c2:2c:2b:d1
indirizzo inet:192.168.1.5 Bcast:192.168.1.255 Maschera:255.255.255.0
indirizzo inet6: fe80::7b03:cf96:2ce1:4e41/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:531 errors:0 dropped:0 overruns:0 frame:0
TX packets:555 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:296591 (296.5 KB) Byte TX:74702 (74.7 KB)
lo Link encap:Loopback locale
indirizzo inet:127.0.0.1 Maschera:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:318 errors:0 dropped:0 overruns:0 frame:0
TX packets:318 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1
Byte RX:31325 (31.3 KB) Byte TX:31325 (31.3 KB)
wlp3s0 Link encap:Ethernet IndirizzoHW b0:c0:90:8e:92:dd
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:0 (0.0 B) Byte TX:0 (0.0 B)
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
pepox [url=http://forum.ubuntu-it.org/viewtopic.php?p=4982798#p4982798][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto:ifconfig
enp2s0 Link encap:Ethernet IndirizzoHW d0:17:c2:2c:2b:d1
indirizzo inet:192.168.1.5 Bcast:192.168.1.255 Maschera:255.255.255.0
indirizzo inet6: fe80::7b03:cf964e41/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
...
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
rifaccio??
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
No, prima di "rifare" si controlla. Vediamo la configurazione della connessione di Ethernet, posta l'output
Codice: Seleziona tutto
nmcli connection show "NOME DELLA CONNESSIONE"
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
Te l'ho già detto ...pepox [url=http://forum.ubuntu-it.org/viewtopic.php?p=4982814#p4982814][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto: come faccio a conoscere il nome della connessione ethernet?
Codice: Seleziona tutto
nmcli connection
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
Codice: Seleziona tutto
nmcli connection show "Connessione via cavo 1"
connection.id: Connessione via cavo 1
connection.uuid: ca480e7e-0eaf-3fe5-9c89-e2cf42cb51f2
connection.interface-name: --
connection.type: 802-3-ethernet
connection.autoconnect: yes
connection.autoconnect-priority: -999
connection.timestamp: 1495026815
connection.read-only: no
connection.permissions:
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (predefinito)
connection.secondaries:
connection.gateway-ping-timeout: 0
connection.metered: sconosciuto
connection.lldp: -1 (default)
802-3-ethernet.port: --
802-3-ethernet.speed: 0
802-3-ethernet.duplex: --
802-3-ethernet.auto-negotiate: yes
802-3-ethernet.mac-address: D0:17:C2:2C:2B:D1
802-3-ethernet.cloned-mac-address: --
802-3-ethernet.mac-address-blacklist:
802-3-ethernet.mtu: auto
802-3-ethernet.s390-subchannels:
802-3-ethernet.s390-nettype: --
802-3-ethernet.s390-options:
802-3-ethernet.wake-on-lan: 1 (default)
802-3-ethernet.wake-on-lan-password: --
ipv4.method: auto
ipv4.dns:
ipv4.dns-search:
ipv4.dns-options: (predefinito)
ipv4.dns-priority: 0
ipv4.addresses:
ipv4.gateway: --
ipv4.routes:
ipv4.route-metric: -1
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (predefinito)
ipv6.method: auto
ipv6.dns:
ipv6.dns-search:
ipv6.dns-options: (predefinito)
ipv6.dns-priority: 0
ipv6.addresses:
ipv6.gateway: --
ipv6.routes:
ipv6.route-metric: -1
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.ip6-privacy: -1 (sconosciuto)
ipv6.addr-gen-mode: stable-privacy
ipv6.dhcp-send-hostname: yes
ipv6.dhcp-hostname: --
GENERAL.NOME: Connessione via cavo 1
GENERAL.UUID: ca480e7e-0eaf-3fe5-9c89-e2cf42cb51f2
GENERAL.DISPOSITIVI: enp2s0
GENERAL.STATO: attivata
GENERAL.PREDEFINITO: sì
GENERAL.PREDEFINITO6: no
GENERAL.VPN: no
GENERAL.ZONA: --
GENERAL.PERCORSO-DBUS: /org/freedesktop/NetworkManager/ActiveConnection/0
GENERAL.PERCORSO-CON: /org/freedesktop/NetworkManager/Settings/7
GENERAL.SPEC-OGGETTO: /
GENERAL.PERCORSO-MASTER: --
IP4.INDIRIZZO[1]: 192.168.1.5/24
IP4.GATEWAY: 192.168.1.1
IP4.INSTRADAMENTO[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]: 192.168.1.1
IP4.WINS[1]: 192.168.1.1
DHCP4.OPZIONE[1]: requested_routers = 1
DHCP4.OPZIONE[2]: requested_domain_search = 1
DHCP4.OPZIONE[3]: requested_time_offset = 1
DHCP4.OPZIONE[4]: requested_domain_name = 1
DHCP4.OPZIONE[5]: requested_rfc3442_classless_static_routes = 1
DHCP4.OPZIONE[6]: requested_broadcast_address = 1
DHCP4.OPZIONE[7]: requested_wpad = 1
DHCP4.OPZIONE[8]: requested_netbios_scope = 1
DHCP4.OPZIONE[9]: next_server = 0.0.0.0
DHCP4.OPZIONE[10]: expiry = 1495112624
DHCP4.OPZIONE[11]: requested_interface_mtu = 1
DHCP4.OPZIONE[12]: requested_subnet_mask = 1
DHCP4.OPZIONE[13]: dhcp_lease_time = 86400
DHCP4.OPZIONE[14]: dhcp_message_type = 5
DHCP4.OPZIONE[15]: ip_address = 192.168.1.5
DHCP4.OPZIONE[16]: requested_static_routes = 1
DHCP4.OPZIONE[17]: requested_domain_name_servers = 1
DHCP4.OPZIONE[18]: routers = 192.168.1.1
DHCP4.OPZIONE[19]: broadcast_address = 192.168.1.255
DHCP4.OPZIONE[20]: domain_name_servers = 192.168.1.1
DHCP4.OPZIONE[21]: requested_ntp_servers = 1
DHCP4.OPZIONE[22]: requested_netbios_name_servers = 1
DHCP4.OPZIONE[23]: netbios_name_servers = 192.168.1.1 192.168.1.1
DHCP4.OPZIONE[24]: requested_ms_classless_static_routes = 1
DHCP4.OPZIONE[25]: subnet_mask = 255.255.255.0
DHCP4.OPZIONE[26]: network_number = 192.168.1.0
DHCP4.OPZIONE[27]: requested_host_name = 1
DHCP4.OPZIONE[28]: dhcp_server_identifier = 192.168.1.1
IP6.INDIRIZZO[1]: fe80::7b03:cf96:2ce1:4e41/64
IP6.GATEWAY:
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
Codice: Seleziona tutto
nmcli connection mod "Connessione via cavo 1" ipv6.method ignore
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
thece [url=http://forum.ubuntu-it.org/viewtopic.php?p=4982811#p4982811][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto:No, prima di "rifare" si controlla. Vediamo la configurazione della connessione di Ethernet, posta l'output
devi sostituire NOME DELLA CONNESSIONE ( tra " ... " ) con il nome della tua connessione Ethernet ... bla bla bla ...Codice: Seleziona tutto
nmcli connection show "NOME DELLA CONNESSIONE"
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: wireless : problema di connessione
Intendevo in questo postpepox [url=http://forum.ubuntu-it.org/viewtopic.php?p=4982825#p4982825][img]http://forum.ubuntu-it.org/images/icons/icona-cita.gif[/img][/url] ha scritto: mi hai detto tu di dare quel comando, o sbaglio?
thece ha scritto:[Semi OT]
Hai il protocollo di rete IPv6 ancora attivo a livello di configurazione sulla connessione Ethernet. Se lo vuoi disabilitare puoi dare il comando
in modo del tutto analogo a quanto hai già fatto in precedenza. Poi il solito riavvio e il comandoCodice: Seleziona tutto
nmcli connection mod "NOME DELLA CONNESSIONE" ipv6.method ignore
per (ri)controllareCodice: Seleziona tutto
ifconfig
[/Semi OT]
Mi serve un pò di tempo e calma per guardare il log, ci risentiamo ...
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
- pepox
- Scoppiettante Seguace
- Messaggi: 464
- Iscrizione: giovedì 14 febbraio 2008, 16:38
- Desktop: Gnome 3.28.2
- Distribuzione: Ubuntu 20.04 LTS 64 bit
- Località: Olbia
Re: wireless : problema di connessione
Codice: Seleziona tutto
ifconfig
enp2s0 Link encap:Ethernet IndirizzoHW d0:17:c2:2c:2b:d1
indirizzo inet:192.168.1.5 Bcast:192.168.1.255 Maschera:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:2196 (2.1 KB) Byte TX:3430 (3.4 KB)
lo Link encap:Loopback locale
indirizzo inet:127.0.0.1 Maschera:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:184 errors:0 dropped:0 overruns:0 frame:0
TX packets:184 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1
Byte RX:13863 (13.8 KB) Byte TX:13863 (13.8 KB)
wlp3s0 Link encap:Ethernet IndirizzoHW b0:c0:90:8e:92:dd
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:0 (0.0 B) Byte TX:0 (0.0 B)
Chi c’è in linea
Visualizzano questa sezione: 0 utenti iscritti e 7 ospiti