iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 5:43 am

Bonjour , j' utilise un pi3B avec debian buster configuré comme une box ( eth0 et wlan0 sont bridgés sur le reseau local 192.168.1.1 ) sur lequel un dongle USB 4G est connecté avec une carte sim et qui me donne donc accés a internet .

Tout donne l' impression de bien marché , sauf que ca dure toujours moins de 24 Heures , le dongle ne donne plus l' acces a internet
il est bien sous tension bien reconnu , mais plus d' acces .
je suis obligé de faire :

Code: Select all

sudo ip link set wwan0 down
puis de relancer mon script de connexion automatique , et la connexion repars pour moins e 24 heures .

j ' utilise modem-manager , pour la configuration du modem et le mettre en route .
j ' ai donc affiné le shmilblik : un script permet de mettre en route au demarrage la connection et de la relancer lorsqu ' elle ci s' avere non fonctionnelle , mais je ne trouve pas la cause du probleme et donc ne peut pas le corriger .


voici le journal et le dmesg en esperant que ca puisse donner des indications sur l' origine du probleme :

Code: Select all

pi@rasphomefi:~ $ cat /var/log/syslog | tail -200
May 17 09:02:58 rasphomefi dnsmasq-dhcp[617]: DHCPDISCOVER(br0) 192.168.1.2 2c:f0:5d:29:20:f2
May 17 09:02:58 rasphomefi dnsmasq-dhcp[617]: DHCPOFFER(br0) 192.168.1.2 2c:f0:5d:29:20:f2
May 17 09:02:58 rasphomefi dnsmasq-dhcp[617]: DHCPREQUEST(br0) 192.168.1.2 2c:f0:5d:29:20:f2
May 17 09:02:58 rasphomefi dnsmasq-dhcp[617]: DHCPACK(br0) 192.168.1.2 2c:f0:5d:29:20:f2 iznobe-PC
May 17 09:05:52 rasphomefi systemd[1]: Starting Cleanup of Temporary Directories...
May 17 09:05:52 rasphomefi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
May 17 09:05:52 rasphomefi systemd[1]: Started Cleanup of Temporary Directories.
May 17 09:11:42 rasphomefi colord[519]: failed to get session [pid 15947]: Aucune donnée disponible
May 17 09:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4420064
May 17 09:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4349216
May 17 09:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4349216
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 220
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 09:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=824.669; max=894.575)Kibits/s
May 17 09:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.223; max=14.287)Mibits/s
May 17 09:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 09:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 09:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 10:08:26 rasphomefi dnsmasq[617]: le serveur de nom 172.20.2.10 a refusé de faire une recherche récursive
May 17 10:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4440064
May 17 10:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4379456
May 17 10:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4379456
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 221
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 10:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=824.382; max=894.575)Kibits/s
May 17 10:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.211; max=14.287)Mibits/s
May 17 10:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 10:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 10:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 11:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4480064
May 17 11:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4409216
May 17 11:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4409216
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 223
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 11:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=824.657; max=894.575)Kibits/s
May 17 11:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.221; max=14.287)Mibits/s
May 17 11:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 11:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 11:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 12:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4500064
May 17 12:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4439456
May 17 12:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4439456
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 224
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 12:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=824.402; max=894.575)Kibits/s
May 17 12:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.209; max=14.287)Mibits/s
May 17 12:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 12:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 12:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 13:12:52 rasphomefi systemd[1]: Starting Daily apt download activities...
May 17 13:13:22 rasphomefi systemd-networkd-wait-online[17256]: Event loop failed: Connection timed out
May 17 13:13:22 rasphomefi apt-helper[17254]: E: Le sous-processus /lib/systemd/systemd-networkd-wait-online a renvoyé un code d'erreur (1)
May 17 13:13:24 rasphomefi systemd[1]: apt-daily.service: Succeeded.
May 17 13:13:24 rasphomefi systemd[1]: Started Daily apt download activities.
May 17 13:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4540064
May 17 13:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4469216
May 17 13:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4469216
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 226
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 13:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=823.876; max=894.575)Kibits/s
May 17 13:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.185; max=14.287)Mibits/s
May 17 13:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 13:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 13:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 13:52:43 rasphomefi hostapd: wlan0: STA 80:35:c1:65:ca:28 IEEE 802.11: disassociated
May 17 13:52:43 rasphomefi hostapd: wlan0: STA 80:35:c1:65:ca:28 IEEE 802.11: disassociated
May 17 14:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4560064
May 17 14:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4499456
May 17 14:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4499456
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 227
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 14:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=824.140; max=894.575)Kibits/s
May 17 14:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.187; max=14.287)Mibits/s
May 17 14:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 14:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 14:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 15:12:20 rasphomefi hostapd: wlan0: STA 80:35:c1:65:ca:28 IEEE 802.11: associated
May 17 15:12:20 rasphomefi hostapd: wlan0: STA 80:35:c1:65:ca:28 RADIUS: starting accounting session 7FB33C1B692EA783
May 17 15:12:20 rasphomefi hostapd: wlan0: STA 80:35:c1:65:ca:28 WPA: pairwise key handshake completed (RSN)
May 17 15:12:20 rasphomefi dnsmasq-dhcp[617]: DHCPDISCOVER(br0) 80:35:c1:65:ca:28
May 17 15:12:20 rasphomefi dnsmasq-dhcp[617]: DHCPOFFER(br0) 192.168.1.39 80:35:c1:65:ca:28
May 17 15:12:20 rasphomefi dnsmasq-dhcp[617]: DHCPREQUEST(br0) 192.168.1.39 80:35:c1:65:ca:28
May 17 15:12:20 rasphomefi dnsmasq-dhcp[617]: DHCPACK(br0) 192.168.1.39 80:35:c1:65:ca:28 RedmiNote5-Redminote
May 17 15:46:01 rasphomefi rngd[687]: stats: bits received from HRNG source: 4600064
May 17 15:46:01 rasphomefi rngd[687]: stats: bits sent to kernel pool: 4528704
May 17 15:46:01 rasphomefi rngd[687]: stats: entropy added to kernel pool: 4528704
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 successes: 229
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2 failures: 1
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Runs: 1
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 17 15:46:01 rasphomefi rngd[687]: stats: HRNG source speed: (min=438.274; avg=823.706; max=894.575)Kibits/s
May 17 15:46:01 rasphomefi rngd[687]: stats: FIPS tests speed: (min=6.788; avg=9.171; max=14.287)Mibits/s
May 17 15:46:01 rasphomefi rngd[687]: stats: Lowest ready-buffers level: 2
May 17 15:46:01 rasphomefi rngd[687]: stats: Entropy starvations: 0
May 17 15:46:01 rasphomefi rngd[687]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 17 16:13:12 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (home -> idle)
May 17 16:13:12 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> searching)
May 17 16:13:13 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (searching -> registering)
May 17 16:13:13 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
May 17 16:13:16 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> registered)
May 17 16:20:38 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: disassociated
May 17 16:20:38 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: associated
May 17 16:20:38 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 RADIUS: starting accounting session 8A6A1B8E308E0FC3
May 17 16:20:38 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 WPA: pairwise key handshake completed (RSN)
May 17 16:20:38 rasphomefi dnsmasq-dhcp[617]: DHCPDISCOVER(br0) 70:2c:09:f1:71:b9
May 17 16:20:38 rasphomefi dnsmasq-dhcp[617]: DHCPOFFER(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 17 16:20:38 rasphomefi dnsmasq-dhcp[617]: DHCPREQUEST(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 17 16:20:38 rasphomefi dnsmasq-dhcp[617]: DHCPACK(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 17 16:20:47 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: disassociated
May 17 16:20:51 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: associated
May 17 16:20:51 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 RADIUS: starting accounting session 4600C24410DC68D2
May 17 16:20:51 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 WPA: pairwise key handshake completed (RSN)
May 17 16:20:51 rasphomefi dnsmasq-dhcp[617]: DHCPDISCOVER(br0) 70:2c:09:f1:71:b9
May 17 16:20:51 rasphomefi dnsmasq-dhcp[617]: DHCPOFFER(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 17 16:20:51 rasphomefi dnsmasq-dhcp[617]: DHCPREQUEST(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 17 16:20:51 rasphomefi dnsmasq-dhcp[617]: DHCPACK(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 17 16:21:00 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: disassociated
May 17 16:21:34 rasphomefi systemd[1]: Started Session 47 of user pi.
May 17 16:21:50 rasphomefi avahi-daemon[375]: Interface wwan0.IPv6 no longer relevant for mDNS.
May 17 16:21:50 rasphomefi avahi-daemon[375]: Leaving mDNS multicast group on interface wwan0.IPv6 with address fe80::a67c:bb65:bb61:2732.
May 17 16:21:50 rasphomefi dhcpcd[600]: wwan0: carrier lost
May 17 16:21:50 rasphomefi dhcpcd[600]: wwan0: deleting address fe80::a67c:bb65:bb61:2732
May 17 16:21:50 rasphomefi avahi-daemon[375]: Interface wwan0.IPv4 no longer relevant for mDNS.
May 17 16:21:50 rasphomefi avahi-daemon[375]: Leaving mDNS multicast group on interface wwan0.IPv4 with address 100.76.177.147.
May 17 16:21:50 rasphomefi avahi-daemon[375]: Withdrawing address record for fe80::a67c:bb65:bb61:2732 on wwan0.
May 17 16:21:50 rasphomefi avahi-daemon[375]: Withdrawing address record for 100.76.177.147 on wwan0.
May 17 16:21:50 rasphomefi systemd-networkd[415]: wwan0: Lost carrier
May 17 16:21:50 rasphomefi dhcpcd[600]: wwan0: deleting route to 100.76.177.144/29
May 17 16:21:50 rasphomefi dhcpcd[600]: wwan0: deleting default route via 100.76.177.145
May 17 16:21:50 rasphomefi dnsmasq[617]: aucun serveur trouvé dans /run/dnsmasq/resolv.conf, va réessayer
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Simple connect started...
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Simple connect state (4/8): Wait to get fully enabled
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Simple connect state (5/8): Register
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Simple connect state (6/8): Bearer
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Simple connect state (7/8): Connect
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
May 17 16:21:59 rasphomefi ModemManager[370]: <warn>  Couldn't find associated cdc-wdm port for 'net/wwan0'
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
May 17 16:21:59 rasphomefi ModemManager[370]: <info>  Simple connect state (8/8): All done
May 17 16:22:00 rasphomefi dhcpcd[600]: wwan0: carrier acquired
May 17 16:22:00 rasphomefi dhcpcd[600]: wwan0: IAID 10:1f:00:00
May 17 16:22:00 rasphomefi dhcpcd[600]: wwan0: adding address fe80::a67c:bb65:bb61:2732
May 17 16:22:00 rasphomefi avahi-daemon[375]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::a67c:bb65:bb61:2732.
May 17 16:22:00 rasphomefi avahi-daemon[375]: New relevant interface wwan0.IPv6 for mDNS.
May 17 16:22:00 rasphomefi avahi-daemon[375]: Registering new address record for fe80::a67c:bb65:bb61:2732 on wwan0.*.
May 17 16:22:00 rasphomefi systemd-networkd[415]: wwan0: Gained carrier
May 17 16:22:01 rasphomefi dhcpcd[600]: wwan0: soliciting an IPv6 router
May 17 16:22:01 rasphomefi dhcpcd[600]: wwan0: rebinding lease of 100.76.177.147
May 17 16:22:01 rasphomefi dhcpcd[600]: wwan0: NAK: from 100.126.220.25
May 17 16:22:01 rasphomefi dhcpcd[600]: wwan0: soliciting a DHCP lease
May 17 16:22:01 rasphomefi dhcpcd[600]: wwan0: offered 100.126.220.26 from 100.126.220.25
May 17 16:22:02 rasphomefi dhcpcd[600]: wwan0: probing address 100.126.220.26/30
May 17 16:22:02 rasphomefi systemd-networkd[415]: wwan0: Gained IPv6LL
May 17 16:22:02 rasphomefi dhcpcd[600]: ipv6nd_sendrsprobe: Operation not permitted
May 17 16:22:06 rasphomefi dhcpcd[600]: ipv6nd_sendrsprobe: Operation not permitted
May 17 16:22:06 rasphomefi dhcpcd[600]: wwan0: leased 100.126.220.26 for 518400 seconds
May 17 16:22:06 rasphomefi avahi-daemon[375]: Joining mDNS multicast group on interface wwan0.IPv4 with address 100.126.220.26.
May 17 16:22:06 rasphomefi avahi-daemon[375]: New relevant interface wwan0.IPv4 for mDNS.
May 17 16:22:06 rasphomefi avahi-daemon[375]: Registering new address record for 100.126.220.26 on wwan0.IPv4.
May 17 16:22:06 rasphomefi dhcpcd[600]: wwan0: adding route to 100.126.220.24/30
May 17 16:22:06 rasphomefi dhcpcd[600]: wwan0: adding default route via 100.126.220.25
May 17 16:22:06 rasphomefi dnsmasq[617]: Lecture de /run/dnsmasq/resolv.conf
May 17 16:22:06 rasphomefi dnsmasq[617]: utilise le serveur de nom 172.20.2.39#53
May 17 16:22:06 rasphomefi dnsmasq[617]: utilise le serveur de nom 172.20.2.10#53
May 17 16:22:10 rasphomefi dhcpcd[600]: ipv6nd_sendrsprobe: Operation not permitted
May 17 16:22:14 rasphomefi dhcpcd[600]: ipv6nd_sendrsprobe: Operation not permitted
May 17 16:22:14 rasphomefi dhcpcd[600]: wwan0: no IPv6 Routers available
pi@rasphomefi:~ $

Code: Select all

pi@rasphomefi:~ $ sudo dmesg |tail -40
[137667.485516] device wlan0 left promiscuous mode
[137667.485677] br0: port 2(wlan0) entered disabled state
[162867.386251] br0: port 2(wlan0) entered blocking state
[162867.386265] br0: port 2(wlan0) entered disabled state
[162867.386981] device wlan0 entered promiscuous mode
[162867.546222] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[162867.546452] br0: port 2(wlan0) entered blocking state
[162867.546462] br0: port 2(wlan0) entered forwarding state
[224067.917051] device wlan0 left promiscuous mode
[224067.917160] br0: port 2(wlan0) entered disabled state
[249267.957906] br0: port 2(wlan0) entered blocking state
[249267.957923] br0: port 2(wlan0) entered disabled state
[249267.958417] device wlan0 entered promiscuous mode
[249268.131265] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[249268.131507] br0: port 2(wlan0) entered blocking state
[249268.131517] br0: port 2(wlan0) entered forwarding state
[310468.502941] device wlan0 left promiscuous mode
[310468.503078] br0: port 2(wlan0) entered disabled state
[335668.396268] br0: port 2(wlan0) entered blocking state
[335668.396300] br0: port 2(wlan0) entered disabled state
[335668.398023] device wlan0 entered promiscuous mode
[335668.569196] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[335668.569411] br0: port 2(wlan0) entered blocking state
[335668.569422] br0: port 2(wlan0) entered forwarding state
[396868.917531] device wlan0 left promiscuous mode
[396868.917670] br0: port 2(wlan0) entered disabled state
[422069.003664] br0: port 2(wlan0) entered blocking state
[422069.003678] br0: port 2(wlan0) entered disabled state
[422069.004958] device wlan0 entered promiscuous mode
[422069.163066] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[422069.163311] br0: port 2(wlan0) entered blocking state
[422069.163321] br0: port 2(wlan0) entered forwarding state
[483269.394270] device wlan0 left promiscuous mode
[483269.394361] br0: port 2(wlan0) entered disabled state
[508469.275353] br0: port 2(wlan0) entered blocking state
[508469.275368] br0: port 2(wlan0) entered disabled state
[508469.275939] device wlan0 entered promiscuous mode
[508469.435019] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[508469.435244] br0: port 2(wlan0) entered blocking state
[508469.435253] br0: port 2(wlan0) entered forwarding state
pi@rasphomefi:~ $

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 8:26 am

Ce qu'il faudrait, ce sont les messages au moment du plantage et au moment du redémarrage parce que là on voit un certain nombre de choses sans savoir les commandes saisies ou ce qui se passait à ce moment là.

Eventuellement augmenter le niveau de verbosité des services concernés.

Mais selon l'opérateur, je me demande si ça n'est pas un simple timeout. Donc il faudrait éventuellement pouvoir tester avec une autre carte SIM.

epoch1970
Posts: 6486
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 9:36 am

A la fin du log attaché, ça fonctionne ou pas?
Je parie que ça fonctionne.

NM a l'air d'avoir un peu de mou dans le genou. Il met le modem en état "registered" alors qu'il devrait essayer de l'amener jusqu'à l'état état "connected".
Une fois en état "registered" il y a un temps de latence (?), et l'interface www0 tombe.
Une fois tombée, NM arrive à l'état "connected" et tout reprend son cours (je crois).

Si l'interface tombait tout de suite, ou bien ne tombait jamais, il n'y aurait pas de problème on dirait. Problème de réglage côté NM ?
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 9:45 am

Bonjour epoch1970 , a la fin du log , effectivement ca fonctionne .

epoch1970 wrote:NM a l'air d'avoir un peu de mou dans le genou. Il met le modem en état "registered" alors qu'il devrait essayer de l'amener jusqu'à l'état état "connected".
Une fois en état "registered" il y a un temps de latence (?), et l'interface www0 tombe.
Une fois tombée, NM arrive à l'état "connected" et tout reprend son cours (je crois).
Le network manager , je ne l' ai pas configuré a priori il ne prend pas en charge la connection .
le temps de latence si c ' est cela dure moins de 24 heures , du coup je refais un initialisation complete du dongle et ca repars .
vu que NM ne gere pas la connection , ca ne repars pas seul .

Plus d' info avec MM sur le dongle :

Code: Select all

pi@rasphomefi:~ $ mmcli --modem=0 --bearer=0
  --------------------------------
  General            |  dbus path: /org/freedesktop/ModemManager1/Bearer/0
                     |       type: default
  --------------------------------
  Status             |  connected: yes
                     |  suspended: no
                     |  interface: wwan0
                     | ip timeout: 20
  --------------------------------
  Properties         |        apn: sl2sfr
                     |    roaming: allowed
                     |    ip type: ipv4
  --------------------------------
  IPv4 configuration |     method: static
                     |    address: 100.126.220.26
                     |     prefix: 30
                     |    gateway: 100.126.220.25
                     |        dns: 172.20.2.39, 172.20.2.10
  --------------------------------
  Statistics         |   duration: 69630
pi@rasphomefi:~ $ mmcli --modem=0
  --------------------------------
  General  |            dbus path: /org/freedesktop/ModemManager1/Modem/0
           |            device id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  --------------------------------
  Hardware |         manufacturer: huawei
           |                model: MS2372h-153
           |             revision: 21.327.07.00.00
           |            supported: gsm-umts
           |              current: gsm-umts
           |         equipment id: xxxxxxxxxxxxx
  --------------------------------
  System   |               device: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5
           |              drivers: huawei_cdc_ncm, option1
           |               plugin: Huawei
           |         primary port: ttyUSB2
           |                ports: ttyUSB0 (at), ttyUSB2 (at), wwan0 (net)
  --------------------------------
  Status   |       unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)
           |                state: connected
           |          power state: on
           |          access tech: lte
           |       signal quality: 54% (recent)
  --------------------------------
  Modes    |            supported: allowed: 2g; preferred: none
           |                       allowed: 3g; preferred: none
           |                       allowed: 4g; preferred: none
           |                       allowed: 2g, 3g, 4g; preferred: none
           |              current: allowed: 4g; preferred: none
  --------------------------------
  IP       |            supported: ipv4
  --------------------------------
  3GPP     |                 imei: xxxxxxxxxxxxxx
           |        enabled locks: sim
           |          operator id: 20810
           |        operator name: F SFR
           |         registration: home
  --------------------------------
  3GPP EPS | ue mode of operation: csps-2
  --------------------------------
  SIM      |            dbus path: /org/freedesktop/ModemManager1/SIM/0
  --------------------------------
  Bearer   |            dbus path: /org/freedesktop/ModemManager1/Bearer/0
pi@rasphomefi:~ $
tu m ' avais donner il y a un moment un tuto pour etablir une connection via le telephone en USB , j ' ai remplace le telephone par le dongle en ajoutant un fichier comme suit :

Code: Select all

sudo nano /etc/systemd/network/dongle.network
dans lequel il y a:

Code: Select all

pi@rasphomefi:~ $ cat /etc/systemd/network/dongle.network
[Match]
Name=wwan0
pi@rasphomefi:~ $
si besoin je peux mettre a nouveau le detail des operations effectuées mais je n' ai rien changer dans les manipulations , juste l' ajout de ce fichier .

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 10:09 am

Et tu peux dater le plantage? Il y a quelque chose dans les logs ou rien?

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 10:18 am

ce matin c ' etait vers les 9 heures et des brouettes . le dmesg ne donnant pas l' heure , au prochain plantage je posterai celui-ci avec la periode corespondante la plus courte possible , mais logiquement , cette periode etait incluse dans le log precedent , sinon ca n ' aurait pas vraiment de sens .

avec cette commande , j' obtiens peut etre un debut de piste :

Code: Select all

pi@rasphomefi:~ $ cat /var/log/syslog | grep err
May 18 06:00:47 rasphomefi apt-helper[19087]: E: Le sous-processus /lib/systemd/systemd-networkd-wait-online a renvoyé un code d'erreur (1)
May 18 08:57:15 rasphomefi apt-helper[19921]: E: Le sous-processus /lib/systemd/systemd-networkd-wait-online a renvoyé un code d'erreur (1)
pi@rasphomefi:~ $
c ' est peut etre lié a mon fichier crontab pour l' erreur de 6 heures du mat qui remet en route le wifi :

Code: Select all

pi@rasphomefi:~ $ crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h  dom mon dow   command

# arret du point d' acces wifi a 23 heures
    00           23             *               *               *       sudo systemctl stop hostapd
# demarrage du point d' acces wifi a 6 heures
    00           6              *               *               *       sudo systemctl start hostapd

# redemarrage de la connection
# arret
    01          23              *               *               *       sudo ip link set wwan0 down
# redemarrage
    01          23              *               *               *       sudo bash /etc/rc.local

# arret
    15          06              *               *               *       sudo ip link set wwan0 down
# redemarrage
    15          06              *               *               *       sudo bash /etc/rc.local
pi@rasphomefi:~ $

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 10:56 am

Donc tu es sûr que ça fonctionnait avant 9h et que subitement ça s'est arrêté disons entre 9 et 10?

Dans ton log d'hier, le MM se réveille à 16h13, c'est là qu'il y a eu le plantage et à 16h22 tu as redémarré?
Faudrait le rendre plus verbeux, genre log-level à DEBUG.

Et l'erreur que tu pointes pose question en effet. Il faudrait aussi voir les logs à l'heure des commandes crontab.

Au passage, dans ta crontab, tu passes carrément par le rc.local. Quelles sont les commandes lancées?

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 11:04 am

Quand il y a plantage je ne redemarre pas .
je fais juste ca :

Code: Select all

sudo ip link set wwan0 down
suivi de

Code: Select all

sudo bash /etc/rc.local
voici mon fichier rc.local :

Code: Select all

pi@rasphomefi:~ $ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.



# lancer le script d' initialisation du modem 4G
sudo bash /home/pi/Scripts/dongle_init.sh

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi

exit 0
pi@rasphomefi:~ $
qui contient mon script d' initialisation du modem que voici :

Code: Select all

pi@rasphomefi:~ $ cat /home/pi/Scripts/dongle_init.sh
#!/bin/sh
sudo mmcli --modem=0 --sim=0 --pin=xxxx
sleep 1
sudo mmcli --modem=0 --enable
sleep 1
sudo mmcli -m 0 --simple-connect='apn=sl2sfr,ip-type=ipv4'

mmcli --modem=0 --bearer=0
sleep 1
sudo ip link set wwan0 up
pi@rasphomefi:~ $
et tout fonctionne normalement jusqu ' au prochain arret , ou je relance les 2 meme commandes , je ne redemarre quasiement jamais le pi .

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 11:13 am

Je voulais dire redémarrer le service. C'est bien ça l'horodatage des logs d'hier?

epoch1970
Posts: 6486
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 11:19 am

Desolé, j'ai confondu modem manager et network manager... je vois tout ça d'assez loin.

Je parlais d'un temps de latence de quelques minutes entre 16:13:16 et 16:21:50. Je ne sais pas si le changement de statut du modem est lié au changement du statut de l'interface (j'imagine) mais le délai semble un peu long. D'autant que tout redémarre correctement ensuite.

EDIT: ce qui suit non applicable, l’interface n’est pas de type point-to-point.

Est-ce qu'on a un truc de ce genre dans dhcpcd.conf ?

Code: Select all

interface wwlan0
static ip_address=
destination routers
Because...
https://manpages.debian.org/buster/dhcpcd5/dhcpcd.8.en.html wrote:3RDPARTY LINK MANAGEMENT
Some interfaces require configuration by 3rd parties, such as PPP or VPN. When an interface configuration in dhcpcd is marked as STATIC or INFORM without an address then dhcpcd will monitor the interface until an address is added or removed from it and act accordingly. For point to point interfaces (like PPP), a default route to its destination is automatically added to the configuration. If the point to point interface is configured for INFORM, then dhcpcd unicasts INFORM to the destination, otherwise it defaults to STATIC.
Last edited by epoch1970 on Wed May 19, 2021 6:41 am, edited 1 time in total.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 11:48 am

voici mon fichier dhcpcd.conf:

Code: Select all

pi@rasphomefi:~ $ cat /etc/dhcpcd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
denyinterfaces wlan0 eth0

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private

# Example static IP configuration:
#interface eth0
#static ip_address=192.168.0.10/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=192.168.0.1
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1

# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1

# fallback to static profile on eth0
#interface eth0
#fallback static_eth0


interface br0
        static ip_address=192.168.1.1/24

pi@rasphomefi:~ $

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 12:31 pm

il faudrait que j' ajoute des lignes de ce type pour la connection wwan0 dans mon fichier dhcpcd.conf ?

la commande :

Code: Select all

pi@rasphomefi:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether b8:27:eb:da:92:e1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ba27:ebff:feda:92e1/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether b8:27:eb:8f:c7:b4 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ba27:ebff:fe8f:c7b4/64 scope link
       valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b8:27:eb:8f:c7:b4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global noprefixroute br0
       valid_lft forever preferred_lft forever
    inet6 fe80::e169:a2a1:b2d6:55c9/64 scope link
       valid_lft forever preferred_lft forever
5: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff
    inet 100.126.220.26/30 brd 100.126.220.27 scope global dynamic noprefixroute wwan0
       valid_lft 490778sec preferred_lft 425978sec
    inet6 fe80::a67c:bb65:bb61:2732/64 scope link
       valid_lft forever preferred_lft forever
pi@rasphomefi:~ $
que penser de :
5: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff
inet 100.126.220.26/30 brd 100.126.220.27 scope global dynamic noprefixroute wwan0
valid_lft 490778sec preferred_lft 425978sec
inet6 fe80::a67c:bb65:bb61:2732/64 scope link
valid_lft forever preferred_lft forever

ca ne serait pas ca qui fait que ma connexion devienne non fonctionnelle apres un certain temps ?

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 6:52 pm

Je dois avouer que je n'aime pas la config réseau via dhcpcd et préfère le bon vieux fichier interfaces.
Cela étant, je ne vois rien qui explique le problème.

Et plus de 400000s pour le lifetime, c'est 5 jours, on est loin des 24h.

Ca peut par contre donner une piste pour un test simple: as-tu besoin d'IPv6? Si non, tu peux le désactiver dans le sysctl.conf.

Et je persiste sur MM: tu devrais augmenter le niveau de log, il y aura peut être quelque chose qui en sortira. Je doute que le modem se mette en erreur sans que quelque chose n'apparaisse.

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 8:59 pm

je veux bien augmenter la verbosité de MM , mais comment proceder stp ?

Pour l' ipv6 le modem en question ne le supporte pas , donc logiquement pas besoin , mais pareil comment faire ca proprement ?

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Tue May 18, 2021 10:07 pm

Pour la verbosité, mmcli accepte le paramètre --set-logging=DEBUG

Pour ipv6, ajouter ça dans sysctl.conf:
net.ipv6.conf.all.disable_ipv6 = 1

epoch1970
Posts: 6486
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Wed May 19, 2021 6:38 am

iznobe wrote:
Tue May 18, 2021 8:59 pm
Pour l' ipv6 le modem en question ne le supporte pas , donc logiquement pas besoin , mais pareil comment faire ca proprement ?
Dans dhcpcd.conf:

Code: Select all

interface www0
noarp
noipv6rs
noipv6
Le noarp va faire un peu accélérer la configuration et les 2 autres options désactivent la recherche d’une IPv6

(Hier j’ai parlé de ppp, c’était hors sujet.)
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Wed May 19, 2021 10:40 am

Bonjour , j ' ai effectué les changements dans le fichier dhcpcd.conf et mis le level de verbosité a debug pour MM .

je me demandais comment faire pour memoriser la connection vu que le network manager qui est installé par defaut ne gere pas la connection ? et si justement ce n' est pas a cause de ca que je suis obligé de relancer la connection ...
Ai je toujours besoin de faire les manips pour mettre en route le modem manuellement ?

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Wed May 19, 2021 1:20 pm

Pour moi il valait mieux désactiver complètement ipv6 via sysctl.conf

Comme tu utilises mmcli dans un script, j'aurais modifié le script. Tu as vérifié, les logs se remplissent? Parce qu'a priori tu devrais tout de suite avoir beaucoup plus de logs.

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Wed May 19, 2021 6:52 pm

Bonsoir , pour la desactivation de l' IPV6 , je prefere que ca ne soit pas definitif , on ne sait jamais ce que l' avenir nous reserve :?:
surtout que ce fichier là je n' y touche jamais , j ' aurais oublié d' ici un moment .

je ne connais pas du tout MM , et je n' ai pas trouvé ou est placé le log de clui ci :oops:

illydone
Posts: 47
Joined: Fri Jun 26, 2020 6:38 am
Location: Near Strasbourg

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Thu May 20, 2021 7:30 am

Pour ipv6, ce n'est évidemment pas définitif: un commentaire sur la ligne dans le sysctl.conf et une commande/un reboot et ça repart. ;)

Pour les logs, modifie ton rc.local en ajoutant --set-logging=DEBUG à tes commandes mmcli.

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Thu May 20, 2021 11:21 am

Bonjour , pour le log level c ' est fait ;)

j' ai eu une coupure ce matin , voici le log :

Code: Select all

pi@rasphomefi:~ $ cat /var/log/syslog | tail -200
May 20 07:40:24 rasphomefi dnsmasq-dhcp[604]: 1435870390 sent size:  4 option:  1 netmask  255.255.255.0
May 20 07:40:24 rasphomefi dnsmasq-dhcp[604]: 1435870390 sent size:  4 option: 28 broadcast  192.168.1.255
May 20 07:40:24 rasphomefi dnsmasq-dhcp[604]: 1435870390 sent size:  4 option:  3 router  192.168.1.1
May 20 07:40:24 rasphomefi dnsmasq-dhcp[604]: 1435870390 sent size:  4 option:  6 dns-server  192.168.1.1
May 20 07:40:24 rasphomefi dnsmasq-dhcp[604]: 1435870390 sent size:  4 option: 15 domain-name  home
May 20 07:40:24 rasphomefi dnsmasq-dhcp[604]: 1435870390 sent size:  9 option: 12 hostname  iznobe-PC
May 20 07:45:05 rasphomefi dnsmasq[604]: le serveur de nom 172.20.2.10 a refusé de faire une recherche récursive
May 20 08:14:10 rasphomefi systemd[1]: Started Session 12 of user pi.
May 20 08:14:14 rasphomefi dhclient[2877]: Internet Systems Consortium DHCP Client 4.4.1
May 20 08:14:14 rasphomefi dhclient[2877]: Copyright 2004-2018 Internet Systems Consortium.
May 20 08:14:14 rasphomefi dhclient[2877]: All rights reserved.
May 20 08:14:14 rasphomefi dhclient[2877]: For info, please visit https://www.isc.org/software/dhcp/
May 20 08:14:14 rasphomefi dhclient[2877]:
May 20 08:14:14 rasphomefi dhclient[2877]: Listening on LPF/wwan0/00:1e:10:1f:00:00
May 20 08:14:14 rasphomefi dhclient[2877]: Sending on   LPF/wwan0/00:1e:10:1f:00:00
May 20 08:14:14 rasphomefi dhclient[2877]: Sending on   Socket/fallback
May 20 08:14:14 rasphomefi dhclient[2877]: DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 7
May 20 08:14:14 rasphomefi dhclient[2877]: DHCPOFFER of 10.146.238.38 from 10.146.238.37
May 20 08:14:14 rasphomefi dhclient[2877]: DHCPREQUEST for 10.146.238.38 on wwan0 to 255.255.255.255 port 67
May 20 08:14:14 rasphomefi dhclient[2877]: DHCPACK of 10.146.238.38 from 10.146.238.37
May 20 08:14:14 rasphomefi systemd[1]: Reloading Samba SMB Daemon.
May 20 08:14:14 rasphomefi systemd[1]: Reloaded Samba SMB Daemon.
May 20 08:14:14 rasphomefi dhclient[2877]: bound to 10.146.238.38 -- renewal in 256669 seconds.
May 20 08:35:59 rasphomefi rngd[677]: stats: bits received from HRNG source: 660064
May 20 08:35:59 rasphomefi rngd[677]: stats: bits sent to kernel pool: 602048
May 20 08:35:59 rasphomefi rngd[677]: stats: entropy added to kernel pool: 602048
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 successes: 33
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 failures: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Runs: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: HRNG source speed: (min=395.979; avg=784.707; max=893.838)Kibits/s
May 20 08:35:59 rasphomefi rngd[677]: stats: FIPS tests speed: (min=5.057; avg=7.931; max=14.245)Mibits/s
May 20 08:35:59 rasphomefi rngd[677]: stats: Lowest ready-buffers level: 2
May 20 08:35:59 rasphomefi rngd[677]: stats: Entropy starvations: 0
May 20 08:35:59 rasphomefi rngd[677]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 20 08:43:44 rasphomefi colord[955]: failed to get session [pid 2217]: Aucune donnée disponible
May 20 08:51:47 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: disassociated
May 20 09:20:31 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 IEEE 802.11: associated
May 20 09:20:31 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 RADIUS: starting accounting session 87FCA02754EF75E7
May 20 09:20:31 rasphomefi hostapd: wlan0: STA 70:2c:09:f1:71:b9 WPA: pairwise key handshake completed (RSN)
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 la gamme DHCP disponible est : 192.168.1.20 -- 192.168.1.100
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 DHCPDISCOVER(br0) 70:2c:09:f1:71:b9
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 options: br0
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 DHCPOFFER(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 options demandées : 1:netmask, 3:router, 6:dns-server, 28:broadcast
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 serveur suivant : 192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  1 option: 53 message-type  2
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 54 server-identifier  192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 51 lease-time  1d
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 58 T1  12h
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 59 T2  21h
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option:  1 netmask  255.255.255.0
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 28 broadcast  192.168.1.255
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option:  3 router  192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option:  6 dns-server  192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 la gamme DHCP disponible est : 192.168.1.20 -- 192.168.1.100
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 DHCPREQUEST(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 options: br0
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 DHCPACK(br0) 192.168.1.83 70:2c:09:f1:71:b9
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 options demandées : 1:netmask, 3:router, 6:dns-server, 28:broadcast
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 serveur suivant : 192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  1 option: 53 message-type  5
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 54 server-identifier  192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 51 lease-time  1d
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 58 T1  12h
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 59 T2  21h
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option:  1 netmask  255.255.255.0
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option: 28 broadcast  192.168.1.255
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option:  3 router  192.168.1.1
May 20 09:20:31 rasphomefi dnsmasq-dhcp[604]: 3830783192 sent size:  4 option:  6 dns-server  192.168.1.1
May 20 09:34:38 rasphomefi hostapd: wlan0: STA e0:cc:f8:81:77:18 IEEE 802.11: disassociated
May 20 09:34:38 rasphomefi hostapd: wlan0: STA e0:cc:f8:81:77:18 IEEE 802.11: disassociated
May 20 09:35:59 rasphomefi rngd[677]: stats: bits received from HRNG source: 680064
May 20 09:35:59 rasphomefi rngd[677]: stats: bits sent to kernel pool: 632288
May 20 09:35:59 rasphomefi rngd[677]: stats: entropy added to kernel pool: 632288
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 successes: 34
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 failures: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Runs: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: HRNG source speed: (min=395.979; avg=787.385; max=893.838)Kibits/s
May 20 09:35:59 rasphomefi rngd[677]: stats: FIPS tests speed: (min=5.057; avg=8.033; max=14.245)Mibits/s
May 20 09:35:59 rasphomefi rngd[677]: stats: Lowest ready-buffers level: 2
May 20 09:35:59 rasphomefi rngd[677]: stats: Entropy starvations: 0
May 20 09:35:59 rasphomefi rngd[677]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 20 10:35:59 rasphomefi rngd[677]: stats: bits received from HRNG source: 720064
May 20 10:35:59 rasphomefi rngd[677]: stats: bits sent to kernel pool: 662048
May 20 10:35:59 rasphomefi rngd[677]: stats: entropy added to kernel pool: 662048
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 successes: 36
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 failures: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Runs: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: HRNG source speed: (min=395.979; avg=792.069; max=893.838)Kibits/s
May 20 10:35:59 rasphomefi rngd[677]: stats: FIPS tests speed: (min=5.057; avg=8.164; max=14.245)Mibits/s
May 20 10:35:59 rasphomefi rngd[677]: stats: Lowest ready-buffers level: 2
May 20 10:35:59 rasphomefi rngd[677]: stats: Entropy starvations: 0
May 20 10:35:59 rasphomefi rngd[677]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 20 11:35:59 rasphomefi rngd[677]: stats: bits received from HRNG source: 740064
May 20 11:35:59 rasphomefi rngd[677]: stats: bits sent to kernel pool: 692288
May 20 11:35:59 rasphomefi rngd[677]: stats: entropy added to kernel pool: 692288
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 successes: 37
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 failures: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Runs: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: HRNG source speed: (min=395.979; avg=791.420; max=893.838)Kibits/s
May 20 11:35:59 rasphomefi rngd[677]: stats: FIPS tests speed: (min=5.057; avg=8.132; max=14.245)Mibits/s
May 20 11:35:59 rasphomefi rngd[677]: stats: Lowest ready-buffers level: 2
May 20 11:35:59 rasphomefi rngd[677]: stats: Entropy starvations: 0
May 20 11:35:59 rasphomefi rngd[677]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 20 12:32:54 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (home -> idle)
May 20 12:32:54 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> searching)
May 20 12:32:55 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (searching -> registering)
May 20 12:32:55 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
May 20 12:32:58 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> registered)
May 20 12:35:59 rasphomefi rngd[677]: stats: bits received from HRNG source: 780064
May 20 12:35:59 rasphomefi rngd[677]: stats: bits sent to kernel pool: 722048
May 20 12:35:59 rasphomefi rngd[677]: stats: entropy added to kernel pool: 722048
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 successes: 39
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2 failures: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Runs: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: HRNG source speed: (min=395.979; avg=795.583; max=893.838)Kibits/s
May 20 12:35:59 rasphomefi rngd[677]: stats: FIPS tests speed: (min=5.057; avg=8.253; max=14.245)Mibits/s
May 20 12:35:59 rasphomefi rngd[677]: stats: Lowest ready-buffers level: 2
May 20 12:35:59 rasphomefi rngd[677]: stats: Entropy starvations: 0
May 20 12:35:59 rasphomefi rngd[677]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 20 12:52:09 rasphomefi systemd[1]: Starting Cleanup of Temporary Directories...
May 20 12:52:09 rasphomefi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
May 20 12:52:09 rasphomefi systemd[1]: Started Cleanup of Temporary Directories.
May 20 13:05:09 rasphomefi systemd-timesyncd[350]: Timed out waiting for reply from 51.68.180.82:123 (0.debian.pool.ntp.org).
May 20 13:05:19 rasphomefi systemd-timesyncd[350]: Timed out waiting for reply from 147.78.229.141:123 (0.debian.pool.ntp.org).
May 20 13:05:29 rasphomefi systemd-timesyncd[350]: Timed out waiting for reply from 136.243.7.20:123 (0.debian.pool.ntp.org).
May 20 13:05:40 rasphomefi systemd-timesyncd[350]: Timed out waiting for reply from 195.13.1.153:123 (0.debian.pool.ntp.org).
May 20 13:11:08 rasphomefi hostapd: wlan0: STA e0:cc:f8:81:77:18 IEEE 802.11: associated
May 20 13:11:08 rasphomefi hostapd: wlan0: STA e0:cc:f8:81:77:18 RADIUS: starting accounting session F2A341B98D98D0C6
May 20 13:11:08 rasphomefi hostapd: wlan0: STA e0:cc:f8:81:77:18 WPA: pairwise key handshake completed (RSN)
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 la gamme DHCP disponible est : 192.168.1.20 -- 192.168.1.100
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 Classe de vendeur ('Vendor Class') : android-dhcp-10
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: le client 1903564772 fourni le nom : RedmiNote8T-RedmiNot
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 DHCPDISCOVER(br0) e0:cc:f8:81:77:18
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options: br0
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 DHCPOFFER(br0) 192.168.1.92 e0:cc:f8:81:77:18
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options demandées : 1:netmask, 3:router, 6:dns-server, 15:domain-name,
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options demandées : 26:mtu, 28:broadcast, 51:lease-time, 58:T1,
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options demandées : 59:T2, 43:vendor-encap
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 serveur suivant : 192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  1 option: 53 message-type  2
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 54 server-identifier  192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 51 lease-time  1d
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 58 T1  12h
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 59 T2  21h
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option:  1 netmask  255.255.255.0
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 28 broadcast  192.168.1.255
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option:  3 router  192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option:  6 dns-server  192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 15 domain-name  home
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 la gamme DHCP disponible est : 192.168.1.20 -- 192.168.1.100
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 Classe de vendeur ('Vendor Class') : android-dhcp-10
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: le client 1903564772 fourni le nom : RedmiNote8T-RedmiNot
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 DHCPREQUEST(br0) 192.168.1.92 e0:cc:f8:81:77:18
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options: br0
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 DHCPACK(br0) 192.168.1.92 e0:cc:f8:81:77:18 RedmiNote8T-RedmiNot
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options demandées : 1:netmask, 3:router, 6:dns-server, 15:domain-name,
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options demandées : 26:mtu, 28:broadcast, 51:lease-time, 58:T1,
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 options demandées : 59:T2, 43:vendor-encap
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 serveur suivant : 192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  1 option: 53 message-type  5
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 54 server-identifier  192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 51 lease-time  1d
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 58 T1  12h
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 59 T2  21h
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option:  1 netmask  255.255.255.0
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 28 broadcast  192.168.1.255
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option:  3 router  192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option:  6 dns-server  192.168.1.1
May 20 13:11:08 rasphomefi dnsmasq-dhcp[604]: 1903564772 sent size:  4 option: 15 domain-name  home
May 20 13:12:20 rasphomefi systemd[1]: Started Session 13 of user pi.
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Simple connect started...
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Simple connect state (4/8): Wait to get fully enabled
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Simple connect state (5/8): Register
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Simple connect state (6/8): Bearer
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Simple connect state (7/8): Connect
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
May 20 13:13:16 rasphomefi ModemManager[361]: <warn>  Couldn't find associated cdc-wdm port for 'net/wwan0'
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
May 20 13:13:16 rasphomefi ModemManager[361]: <info>  Simple connect state (8/8): All done
pi@rasphomefi:~ $
j ' ai passé cette commande et hop connection a nouveau operationnelle :

Code: Select all

sudo dhclient -v wwan0
comme si il n' y avait pas de configuration pour relancer une demande d ' IP aupres du serveur de mon FAI .

epoch1970
Posts: 6486
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Thu May 20, 2021 1:41 pm

dhclient est redondant avec dhcpcd...
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Thu May 20, 2021 4:05 pm

Bonjour epoch1970 , il faut donc que je le deinstalle ( dhclient ) ?

epoch1970
Posts: 6486
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Thu May 20, 2021 5:23 pm

Non, il suffit de ne pas l'utiliser, et dhcpcd s'occupera de l'interface.
dhcpcd est un client DHCP, comme (le vieux) dhclient.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

iznobe
Posts: 673
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: Connection 4G qui se bloque tous les jours sur pi3B avec debian buster

Thu May 20, 2021 9:22 pm

ben pour le moment j' ai pas l' impression qu ' il fasse son travail correctement :roll:
ou alors il y a un probleme ailleurs , mais je ne vois pas grand chose dans le journal malheusement , a part peut etre cela :

Code: Select all

May 20 12:32:54 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (home -> idle)
May 20 12:32:54 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> searching)
May 20 12:32:55 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (searching -> registering)
May 20 12:32:55 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
May 20 12:32:58 rasphomefi ModemManager[361]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> registered)
Pourquoi le modem passe de l' etat connecté a l ' etat enregistré ?

Return to “Français”