Newsgroup: it.comp.os.linux.iniziare
Titolo: wlan0 crasha

Premessa: Normalmente uso una debian stretch aggiornata ad alcuni giorni fa. E
fino ad un paio di settimane fa (dopo non l'ho più uato), il wifi funzionava
perfettamente.
 
Ho avuto la malaugurata idea di installare l'altro giorno, modem-manager-gui
per usare delle chiavette internet ed il sever ssh.
 
Oggi provo a connettermi al wifi e non ci riesco.
Come programma uso il wicd di default.
 
Nei log (wicd.log), non noto differenze tra le connesioni funzionanti e quelle attuali.
Si blocca con la scritta di autenticazione poi dopo parecchio tempo, esce.
Con wireshark, sembra che la wlan0 crashi.
 
Una cosa che ho notato che /etc/resolv.conf viene sostituito con un link rotto
a /run/network-manager/resolv.conf che non esiste.
 
Ho ripristinato /etc/resolv.conf con i miei valori, ma non cambia nulla.
 
Cosa cavolo mi è successo?
 

vedi errori in:
 
dmesg | grep wlan0
 
oppure in: journalctl -b -p err

In date: Thu, 12 Sep 2019 16:39:05 on group: it.comp.os.linux.iniziare,

Posso rispondere solo adesso che ho la connessione ethernet.
 
L'errore bluetooth è ricorrente in modalità random, ma non mi ha mai dato
problemi wifi, ma solo sul bluetooth.
 
 
sudo journalctl -b -p err
-- Logs begin at Fri 2019-09-13 08:51:09 CEST, end at Fri 2019-09-13 08:54:29 CEST. --
Sep 13 08:51:09 debian systemd-fstab-generator[787]: Failed to create mount unit file /run/systemd/generator/-.mount, as it already exists. 
Sep 13 08:51:14 debian kernel: intel_soc_dts_thermal: request_threaded_irq ret -22
Sep 13 08:51:14 debian kernel: intel_soc_dts_thermal: request_threaded_irq ret -22
Sep 13 08:51:21 debian kernel: Bluetooth: hci0 command 0x1001 tx timeout
Sep 13 08:51:27 debian pulseaudio[7030]: [pulseaudio] pid.c: Daemon already running.
Sep 13 08:51:29 debian kernel: Bluetooth: hci0: BCM: Reading local version info failed (-110)
Sep 13 08:52:19 debian dhclient[9178]: send_packet: Network is unreachable
Sep 13 08:52:19 debian dhclient[9178]: send_packet: please consult README file regarding broadcast address.
Sep 13 08:52:19 debian dhclient[9178]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 13 08:52:19 debian dhclient[9206]: send_packet: Network is unreachable
Sep 13 08:52:19 debian dhclient[9206]: send_packet: please consult README file regarding broadcast address.
Sep 13 08:52:19 debian dhclient[9206]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 13 08:52:19 debian dhclient[9235]: send_packet: Network is unreachable
Sep 13 08:52:19 debian dhclient[9235]: send_packet: please consult README file regarding broadcast address.
Sep 13 08:52:19 debian dhclient[9235]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 13 08:53:02 debian dhclient[9324]: send_packet: Network is unreachable
Sep 13 08:53:02 debian dhclient[9324]: send_packet: please consult README file regarding broadcast address.
Sep 13 08:53:02 debian dhclient[9324]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 13 08:53:03 debian dhclient[9351]: send_packet: Network is unreachable
Sep 13 08:53:03 debian dhclient[9351]: send_packet: please consult README file regarding broadcast address.
Sep 13 08:53:03 debian dhclient[9351]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
 
 
sudo dmesg | grep wlan0
[   25.329310] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
[   28.395939] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   28.937040] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   76.534741] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   90.273341] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   90.357517] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  134.039015] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  134.101987] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
 
 
Credevo di essermelo tolto dalle palle l'ipv6.
Non sara micca lui a farmi i casini?
 
 
 
 
-- 
--- Maximus 2.01wb
 * Origin: Euforia (2:331/308)

- per l'ipv6 prova a passare al kernel: ipv6.disable=1
 
 
- che vedi dal comando: inxi -n
 
(ovvero che driver usi per la BCM4365)
 
 
- che vedi da: rfkill list

 - che vedi da: rfkill list
 
sudo rfkill list
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: yes
    Hard blocked: no
 
Si, il bluetooth non lo uso perciò lo tengo sempre spento.
 
 
******************
 
 
Un cosa da aggiungere; su una chiavetta sempre con la stesso linux, ma vecchia
(kernel 4.9.0-4) con solo il modem-manager inserito non ha problemi di
connessione (ma è anche piuttosto vecchia).
 
Un precedente backup di questa chiavetta che sto usando, con il kernel 4.9.0-8,
con installato i 2 programmi di cui sopra, ha lo stesso problema di questa.
 
 
Il wicd.log, fatto ora sul mio paleolitico AP in casa (che uso in casi sporadici, praticamente mai):
Però stranamente, non crasha, come nella connessione dell'hotel.
Per inciso in quell'hotel ci sono stato lo scorso anno con questo sistema, e tutto era ok.
Sono stato nel frattempo il altri hotel, senza avere problemi.
Ci sono tornato nell'hotel a metà agosto di quest'anno ed era ok.
Ci sono tornato in questi giorni, dopo aver installato, a casa con rete
cablata, come detto all'inizio, il modem-manager per chiavette 3g-4g ed il
server ssh ed il wifi ha smesso di andare.
 
wicd.log
2019/09/16 22:45:27 :: Connecting to wireless network Alice
2019/09/16 22:45:27 :: iwconfig wlan0
2019/09/16 22:45:27 :: Executing /etc/network/if-down.d/avahi-autoipd with params 
2019/09/16 22:45:27 :: /etc/network/if-down.d/avahi-autoipd returned 0
2019/09/16 22:45:27 :: Executing /etc/network/if-down.d/upstart with params 
2019/09/16 22:45:27 :: /etc/network/if-down.d/upstart returned 0
2019/09/16 22:45:27 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2019/09/16 22:45:27 :: /etc/network/if-down.d/wpasupplicant returned 0
2019/09/16 22:45:27 :: /sbin/dhclient -v -r wlan0
2019/09/16 22:45:27 :: ifconfig wlan0 0.0.0.0 
2019/09/16 22:45:27 :: /sbin/ip route flush dev wlan0
2019/09/16 22:45:27 :: ifconfig wlan0 down
2019/09/16 22:45:27 :: ifconfig wlan0 up
2019/09/16 22:45:27 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2019/09/16 22:45:27 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2019/09/16 22:45:27 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2019/09/16 22:45:27 :: /etc/network/if-post-down.d/wireless-tools returned 0
2019/09/16 22:45:27 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2019/09/16 22:45:27 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2019/09/16 22:45:27 :: wpa_cli -i wlan0 terminate
2019/09/16 22:45:27 :: Executing /etc/network/if-down.d/avahi-autoipd with params 
2019/09/16 22:45:27 :: /etc/network/if-down.d/avahi-autoipd returned 0
2019/09/16 22:45:27 :: Executing /etc/network/if-down.d/upstart with params 
2019/09/16 22:45:27 :: /etc/network/if-down.d/upstart returned 0
2019/09/16 22:45:27 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2019/09/16 22:45:27 :: /etc/network/if-down.d/wpasupplicant returned 0
2019/09/16 22:45:27 :: /sbin/dhclient -v -r eth0
2019/09/16 22:45:27 :: ifconfig eth0 0.0.0.0 
2019/09/16 22:45:27 :: /sbin/ip route flush dev eth0
2019/09/16 22:45:27 :: ifconfig eth0 down
2019/09/16 22:45:27 :: ifconfig eth0 up
2019/09/16 22:45:28 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2019/09/16 22:45:28 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2019/09/16 22:45:28 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2019/09/16 22:45:28 :: /etc/network/if-post-down.d/wireless-tools returned 0
2019/09/16 22:45:28 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2019/09/16 22:45:28 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2019/09/16 22:45:28 :: wpa_cli -i eth0 terminate
2019/09/16 22:45:28 :: Executing /etc/network/if-pre-up.d/ethtool with params 
2019/09/16 22:45:28 :: /etc/network/if-pre-up.d/ethtool returned 0
2019/09/16 22:45:28 :: Executing /etc/network/if-pre-up.d/wireless-tools with params 
2019/09/16 22:45:28 :: /etc/network/if-pre-up.d/wireless-tools returned 0
2019/09/16 22:45:28 :: Executing /etc/network/if-pre-up.d/wpasupplicant with params 
2019/09/16 22:45:28 :: /etc/network/if-pre-up.d/wpasupplicant returned 0
2019/09/16 22:45:28 :: Putting interface down
2019/09/16 22:45:28 :: ifconfig wlan0 down
2019/09/16 22:45:28 :: Releasing DHCP leases...
2019/09/16 22:45:28 :: /sbin/dhclient -v -r wlan0
2019/09/16 22:45:28 :: Setting false IP...
2019/09/16 22:45:28 :: ifconfig wlan0 0.0.0.0 
2019/09/16 22:45:28 :: Stopping wpa_supplicant
2019/09/16 22:45:28 :: wpa_cli -i wlan0 terminate
2019/09/16 22:45:28 :: Flushing the routing table...
2019/09/16 22:45:28 :: /sbin/ip route flush dev wlan0
2019/09/16 22:45:28 :: iwconfig wlan0 mode managed
2019/09/16 22:45:28 :: Putting interface up...
2019/09/16 22:45:28 :: ifconfig wlan0 up
2019/09/16 22:45:30 :: enctype is wpa
2019/09/16 22:45:30 :: Generating psk...
2019/09/16 22:45:30 :: ['/usr/bin/wpa_passphrase', 'Alice *******************']
2019/09/16 22:45:30 :: Attempting to authenticate...
2019/09/16 22:45:30 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/1caff7ce43cd', '-Dwext']
2019/09/16 22:45:30 :: ['iwconfig', 'wlan0', 'essid', '--', 'Alice']
2019/09/16 22:45:30 :: iwconfig wlan0 channel 1
2019/09/16 22:45:30 :: iwconfig wlan0 ap 1C:*:*:*:*:*
2019/09/16 22:45:30 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:31 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2019/09/16 22:45:32 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2019/09/16 22:45:33 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2019/09/16 22:45:34 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:35 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:36 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:37 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:38 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:39 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:40 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:41 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:42 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:43 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:43 :: wpa_supplicant rescan forced...
2019/09/16 22:45:44 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2019/09/16 22:45:45 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2019/09/16 22:45:46 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2019/09/16 22:45:47 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:48 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:49 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:50 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:51 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:52 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:53 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:54 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:55 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:56 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:57 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:45:58 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:45:59 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:00 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:01 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:02 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:03 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:04 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:46:05 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:46:06 :: WPA_CLI RESULT IS SCANNING
2019/09/16 22:46:07 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:08 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:09 :: WPA_CLI RESULT IS DISCONNECTED
2019/09/16 22:46:10 :: wpa_supplicant authentication may have failed.
2019/09/16 22:46:10 :: connect result is failed
2019/09/16 22:46:10 :: exiting connection thread
2019/09/16 22:46:10 :: Sending connection attempt result bad_pass
2019/09/16 22:46:10 :: ifconfig eth0
2019/09/16 22:46:10 :: ifconfig wlan0
2019/09/16 22:46:10 :: Forced disconnect on
2019/09/16 22:46:10 :: iwconfig wlan0
2019/09/16 22:46:10 :: Executing /etc/network/if-down.d/avahi-autoipd with params 
2019/09/16 22:46:10 :: /etc/network/if-down.d/avahi-autoipd returned 0
2019/09/16 22:46:10 :: Executing /etc/network/if-down.d/upstart with params 
2019/09/16 22:46:10 :: /etc/network/if-down.d/upstart returned 0
2019/09/16 22:46:10 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2019/09/16 22:46:10 :: /etc/network/if-down.d/wpasupplicant returned 0
2019/09/16 22:46:10 :: /sbin/dhclient -v -r wlan0
2019/09/16 22:46:11 :: ifconfig wlan0 0.0.0.0 
2019/09/16 22:46:11 :: /sbin/ip route flush dev wlan0
2019/09/16 22:46:11 :: ifconfig wlan0 down
2019/09/16 22:46:11 :: ifconfig wlan0 up
2019/09/16 22:46:11 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2019/09/16 22:46:11 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2019/09/16 22:46:11 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2019/09/16 22:46:11 :: /etc/network/if-post-down.d/wireless-tools returned 0
2019/09/16 22:46:11 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2019/09/16 22:46:11 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2019/09/16 22:46:11 :: wpa_cli -i wlan0 terminate
2019/09/16 22:46:11 :: Executing /etc/network/if-down.d/avahi-autoipd with params 
2019/09/16 22:46:11 :: /etc/network/if-down.d/avahi-autoipd returned 0
2019/09/16 22:46:11 :: Executing /etc/network/if-down.d/upstart with params 
2019/09/16 22:46:11 :: /etc/network/if-down.d/upstart returned 0
2019/09/16 22:46:11 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2019/09/16 22:46:11 :: /etc/network/if-down.d/wpasupplicant returned 0
2019/09/16 22:46:11 :: /sbin/dhclient -v -r eth0
2019/09/16 22:46:11 :: ifconfig eth0 0.0.0.0 
2019/09/16 22:46:11 :: /sbin/ip route flush dev eth0
2019/09/16 22:46:11 :: ifconfig eth0 down
2019/09/16 22:46:11 :: ifconfig eth0 up
2019/09/16 22:46:11 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2019/09/16 22:46:11 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2019/09/16 22:46:11 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2019/09/16 22:46:11 :: /etc/network/if-post-down.d/wireless-tools returned 0
2019/09/16 22:46:11 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2019/09/16 22:46:11 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2019/09/16 22:46:11 :: wpa_cli -i eth0 terminate
2019/09/16 22:46:12 :: ifconfig eth0
2019/09/16 22:46:12 :: ifconfig wlan0
2019/09/16 22:46:15 :: ifconfig eth0
2019/09/16 22:46:15 :: ifconfig wlan0
2019/09/16 22:46:17 :: ifconfig eth0
2019/09/16 22:46:17 :: ifconfig wlan0
2019/09/16 22:46:20 :: ifconfig eth0
2019/09/16 22:46:20 :: ifconfig wlan0
2019/09/16 22:46:22 :: ifconfig eth0
2019/09/16 22:46:22 :: ifconfig wlan0
 
 
sudo dmesg | grep wlan0
wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
[   28.558927] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   29.430458] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  371.237676] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  686.361593] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1001.485293] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1316.601075] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1631.725888] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1946.875345] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2261.977735] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2577.094405] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2892.209797] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3207.336960] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3522.449445] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3837.568559] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4152.687808] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4467.808016] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 4782.942309] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 5098.049060] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 5413.172517] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 5728.303941] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6043.410623] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6358.533950] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6673.657102] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6988.773810] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7303.906657] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7619.020893] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7934.137733] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8249.258310] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8564.375033] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8879.513329] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9194.617696] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9331.537038] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9331.665595] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[10592.270962] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[10592.341649] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[10831.338686] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[10831.399221] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
 
 
sudo journalctl -b -p err
Sep 16 22:41:29 debian dhclient[14274]: receive_packet failed on eth0: Network is down
Sep 16 22:41:33 debian dhclient[15366]: send_packet: Network is unreachable
Sep 16 22:41:33 debian dhclient[15366]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:41:33 debian dhclient[15366]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:41:34 debian dhclient[15393]: send_packet: Network is unreachable
Sep 16 22:41:34 debian dhclient[15393]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:41:34 debian dhclient[15393]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:41:34 debian dhclient[15431]: send_packet: Network is unreachable
Sep 16 22:41:34 debian dhclient[15431]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:41:34 debian dhclient[15431]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:42:12 debian dhclient[15517]: send_packet: Network is unreachable
Sep 16 22:42:12 debian dhclient[15517]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:42:12 debian dhclient[15517]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:42:12 debian dhclient[15584]: send_packet: Network is unreachable
Sep 16 22:42:12 debian dhclient[15584]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:42:12 debian dhclient[15584]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:45:27 debian dhclient[15821]: send_packet: Network is unreachable
Sep 16 22:45:27 debian dhclient[15821]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:45:27 debian dhclient[15821]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:45:27 debian dhclient[15848]: send_packet: Network is unreachable
Sep 16 22:45:27 debian dhclient[15848]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:45:27 debian dhclient[15848]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:45:28 debian dhclient[15877]: send_packet: Network is unreachable
Sep 16 22:45:28 debian dhclient[15877]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:45:28 debian dhclient[15877]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:46:11 debian dhclient[15975]: send_packet: Network is unreachable
Sep 16 22:46:11 debian dhclient[15975]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:46:11 debian dhclient[15975]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
Sep 16 22:46:11 debian dhclient[16004]: send_packet: Network is unreachable
Sep 16 22:46:11 debian dhclient[16004]: send_packet: please consult README file regarding broadcast address.
Sep 16 22:46:11 debian dhclient[16004]: dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
 
 
 
-- 
--- Maximus 2.01wb
 * Origin: A.R.I. "Augusto Righi" & Elettronica Flash BBS (2:332/413)

 Non sara micca lui a farmi i casini?
 
direi che non c'entra niente, l'errore è l'analogo del dhcp client non 
riesce ad assegnare l'indirizzo ipv6 local. sembra ci sia un problema a 
livello più basso cioè sul link radio.
 
iwconfig wlan0 che dice? 

 authentication may have failed.
 
questo mi sembra abbastanza esplicativo.

 iwconfig wlan0 che dice? 
 
Adesso, non collegato:
sudo iwconfig wlan0
wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
 
 
 
-- 
... Short Wave Listening somewhere in brianza!
--- Blue Wave/RA v2.12 [NR]
 * Origin: -=[ Virtual Image Board ]=- ++39-341-3xxxxx (2:331/120.0)

e farla a mano?
 
https://wiki.debian.org/it/WiFi/HowToUse#Riga_di_comando
 

 
https://wiki.debian.org/it/WiFi/HowToUse#Riga_di_comando
 
 
Stavo provando a falo a mano, quando ho visto in una nota di quel wiki dice che
wicd è allergico al network-manager.
 
Infatti quel fottuto di modem-manager che deve permettere l'uso delle chiavette
3g, installa ANCHE il network-manager.  (Ma che intrippo di nomi...)
 
Dando un: sudo /etc/init.d/network-manager stop, il wifi ha funzionato.
 
Ora devo capire come gestire le cose.
 
Per ora ho messo i link in /etc/rc2.d eccetera di network-manager in K anzichè
in S.
 
 
P.S.   La firma è automatica e casuale, ma in questo caso è azzeccata!
 
-- 
--- Msged/sq
 * Origin: "Il primo passo per risolvere un problema e' capirlo." (2:331/308.2)

 
 
Cazzo c'è quel porcaio di systemd!!!
Messo lo stop in /etc/rc.local (e che si inc...o quelli che lo vogliono togliere).


 togliere).
 
lol :-)
 
chkconfig network-manager off
 
oppure, se è systemd a comandare:
 
systemctl disable network-manager
 
è un servizio, se non lo disabiliti è ovvio che poi riparta. systemd o 
non systemd :-)
 
 

non so se e' scritto proprio cosi' ma devi dare:
 
 
 
sudo systemctl disable network-manager.service

 Messo lo stop in /etc/rc.local (e che si inc...o quelli che lo vogliono togliere).
 
Che problemi hai con systemd?
io lo uso da almeno 5 anni senza problemi,ovviamente dopo essermi 
documentato...

 non systemd :-)
 
Non proprio.
 
Col vecchio sistema, i servizi installati ma che non uso sempre, li ho sempre
messi con K in /etc/rc2.d e seguenti. E mi riferisco, nel mio caso, al server
web, server ssh, server sftp.
Li abilito al bisogno con il solito /etc/init.d/nome-servizio start. E questo
sin dalla vecchia debian potato.
 
Con systemd, lo stesso metodo di NON avviare un servizio non funziona.
Ho dovuto (per il momento) stopparlo in /etc/rc.local.
 
Concordo che facendo come dici tu "systemctl disable network-manager" si
disabilita.
Ma se io ho bisogno di fare "qualche cosa" allo start o stop di un servizio
abilitato o meno, col vecchio sistema mi bastava modificare lo script in
/etc/init.d.
 
Per esempio, in un caso che non riesco a risolvere:
Ho un log gestito da rsyslog che viene salvato in ramfs, ad allo shutdown od al
reboot lo debbo salvare nel regolare fs in modo da averlo disponibile al
prossimo riavvio.
Allo start di rsyslog devo prima recuperare il vecchio log e metterlo nel
ramfs, e dopo lo stop di rsyslog lo devo salvare.
 
Con systemd non sono assolutamente riuscito a farlo!
 
 
 
-- 
 X SLMR 2.1a X All hope abandon, ye who enter messages here.

 sudo systemctl disable network-manager.service
 
Circa, vedi anche risposta a rootkit.
 
Approposito, grazie per il suggerimento di fare la procedura in manuale!
 
 
-- 
--- PointMail 2.b8Demo
 * Origin: Il Raf... Point 12 di "The Rocky Horror BBS Show" (2:332/212.12)

In date: Wed, 18 Sep 2019 04:08:32 on group: it.comp.os.linux.iniziare,

Vedi la parte finale della risposta a rootkit.


 script in /etc/init.d.
 
lì è ancora più semplice e pulito. nel file di definizione dello unit 
puoi impostare un ExecStartPre e/o ExecStopPost dove fai quello che devi 
fare senza "sporcare" gli script.