Não é possível reconectar a conexão 3G após o novo IP ter sido dado

Navegue suas respostas
4

Eu uso Debian Jessie 8.2 e estou usando uma conexão 3G usando Huawei MU709 Mini PCIe .

A conexão 3G funciona bem, exceto depois de 24 horas a conexão cai e não consigo me reconectar. Se eu reiniciar o computador, a conexão funcionará novamente.

Meu palpite é que meu ISP me fornece um novo endereço IP depois de 24 horas e, de alguma forma, meu sistema não consegue lidar com isso.

Como posso reconectar minha conexão 3G sem reiniciar?

Já experimentei os seguintes comandos: 

sudo service network-manager restart

e também: 

dhclient -r eth0
dhclient eth0

EDIT 1:

Resultados de journalctl e grepping meu nome de conexão ( SFR ) 

sept. 22 17:58:19 ark1 NetworkManager[512]: <info> Policy set 'SFR Web / Prepaid 1' (eth0) as default for IPv4 routing and DNS.
sept. 23 18:17:07 ark1 NetworkManager[9446]: <info> new connection /etc/NetworkManager/system-connections/SFR Web * Prepaid 1
sept. 23 18:17:08 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR Web / Prepaid 1'.
sept. 23 18:17:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR Web / Prepaid 1'
sept. 23 18:17:53 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR Web / Prepaid 1'
sept. 23 18:17:53 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR Web / Prepaid 1'.
sept. 23 18:17:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR Web / Prepaid 1'
sept. 23 18:18:03 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR Web / Prepaid 1'
sept. 23 18:18:03 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR Web / Prepaid 1'.
sept. 23 18:18:03 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR Web / Prepaid 1'
sept. 23 18:18:13 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR Web / Prepaid 1'

Como você pode ver, sept 22 at time 17:18 é quando o computador é inicializado. E aproximadamente 24 horas depois que ele não conseguiu se reconectar.

Também devo mencionar que existe um script para executar o comando: 

sudo service network-manager restart

se o computador não puder fazer ping em um servidor, ou seja, se a conexão for perdida.

EDIT 2: Adicionado mais journalctl info quando o sistema tentar se reconectar: 

sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR'
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
sept. 23 23:52:53 ark1 ModemManager[518]: <info>  Simple connect started...
sept. 23 23:52:53 ark1 ModemManager[518]: <info>  Simple connect state (4/8): Wait to get fully enabled
sept. 23 23:52:53 ark1 ModemManager[518]: <info>  Simple connect state (5/8): Register
sept. 23 23:52:53 ark1 ModemManager[518]: <info>  Simple connect state (6/8): Bearer
sept. 23 23:52:53 ark1 ModemManager[518]: <info>  Simple connect state (7/8): Connect
sept. 23 23:52:53 ark1 ModemManager[518]: <info>  Simple connect state (8/8): All done
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: prepare -> config (reason 'none') [40 50 0]
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: config -> ip-config (reason 'none') [50 70 0]
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> dhclient started with pid 13212
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) started...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> (eth0): DHCPv4 state changed nbi -> preinit
sept. 23 23:52:53 ark1 dhclient[13212]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
sept. 23 23:52:59 ark1 dhclient[13212]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
sept. 23 23:53:09 ark1 dhclient[13212]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
sept. 23 23:53:14 ark1 dhclient[13212]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
sept. 23 23:53:22 ark1 dhclient[13212]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
sept. 23 23:53:32 ark1 dhclient[13212]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
sept. 23 23:53:38 ark1 NetworkManager[9446]: <warn> (eth0): DHCPv4 request timed out.
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> (eth0): canceled DHCP transaction, DHCP client pid 13212
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) started...
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
sept. 23 23:53:38 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR'
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0]
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> (ttyUSB0): deactivating device (reason 'none') [0]
sept. 23 23:53:38 ark1 avahi-daemon[528]: Withdrawing address record for 169.254.1.156 on eth0.
sept. 23 23:53:38 ark1 avahi-daemon[528]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.1.156.
sept. 23 23:53:38 ark1 avahi-daemon[528]: Interface eth0.IPv4 no longer relevant for mDNS.
sept. 23 23:53:38 ark1 dhclient[11114]: receive_packet failed on eth0: Network is down
sept. 23 23:53:38 ark1 ModemManager[518]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> disconnecting)
sept. 23 23:53:38 ark1 ModemManager[518]: <warn>  Couldn't find associated cdc-wdm port for 'net/eth0'
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR'
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
sept. 23 23:53:38 ark1 NetworkManager[9446]: <info> (ttyUSB0): modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
sept. 23 23:53:38 ark1 avahi-autoipd(eth0)[13202]: SIOCSIFFLAGS failed: Operation not permitted
sept. 23 23:53:38 ark1 avahi-autoipd(eth0)[13202]: Callout STOP, address 169.254.1.156 on interface eth0
sept. 23 23:53:39 ark1 ModemManager[518]: <info>  Simple connect started...
sept. 23 23:53:39 ark1 ModemManager[518]: <info>  Simple connect state (4/8): Wait to get fully enabled
sept. 23 23:53:39 ark1 avahi-autoipd(eth0)[13203]: client: RTNETLINK answers: No such process
sept. 23 23:53:39 ark1 avahi-autoipd(eth0)[13203]: client: RTNETLINK answers: Cannot assign requested address
sept. 23 23:53:39 ark1 avahi-autoipd(eth0)[13203]: Script execution failed with return value 2
sept. 23 23:53:48 ark1 NetworkManager[9446]: <warn> (ttyUSB0) failed to connect modem: Too much time waiting to get to a final state
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: prepare -> failed (reason '(null)') [40 120 1]
sept. 23 23:53:48 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR'
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0]
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> (ttyUSB0): deactivating device (reason 'none') [0]
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR'
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
sept. 23 23:53:48 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
sept. 23 23:53:48 ark1 ModemManager[518]: <info>  Simple connect started...
sept. 23 23:53:48 ark1 ModemManager[518]: <info>  Simple connect state (4/8): Wait to get fully enabled
sept. 23 23:53:58 ark1 NetworkManager[9446]: <warn> (ttyUSB0) failed to connect modem: Too much time waiting to get to a final state
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: prepare -> failed (reason '(null)') [40 120 1]
sept. 23 23:53:58 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR'
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0]
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> (ttyUSB0): deactivating device (reason 'none') [0]
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR'
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
sept. 23 23:53:58 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
sept. 23 23:53:58 ark1 ModemManager[518]: <info>  Simple connect started...
sept. 23 23:53:58 ark1 ModemManager[518]: <info>  Simple connect state (4/8): Wait to get fully enabled
sept. 23 23:54:08 ark1 NetworkManager[9446]: <warn> (ttyUSB0) failed to connect modem: Too much time waiting to get to a final state
sept. 23 23:54:08 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: prepare -> failed (reason '(null)') [40 120 1]
sept. 23 23:54:08 ark1 NetworkManager[9446]: <info> Disabling autoconnect for connection 'SFR'.
sept. 23 23:54:08 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR'
sept. 23 23:54:08 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0]
sept. 23 23:54:08 ark1 NetworkManager[9446]: <info> (ttyUSB0): deactivating device (reason 'none') [0]
sept. 23 23:54:39 ark1 ModemManager[518]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disconnecting -> connected)
sept. 23 23:54:39 ark1 NetworkManager[9446]: <info> (ttyUSB0): modem state changed, 'disconnecting' --> 'connected' (reason: user-requested)
sept. 23 23:55:31 ark1 noip2[1786]: Can't get our visible IP address from ip1.dynupdate.no-ip.com
sept. 23 23:55:50 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
sept. 23 23:55:50 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:55:50 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:55:54 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
sept. 23 23:55:54 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:55:54 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:56:02 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
sept. 23 23:56:02 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:56:02 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:56:13 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
sept. 23 23:56:13 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:56:13 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:56:23 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
sept. 23 23:56:23 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:56:23 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:56:34 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
sept. 23 23:56:34 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:56:34 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:56:43 ark1 dhclient[11114]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
sept. 23 23:56:43 ark1 dhclient[11114]: send_packet: Network is down
sept. 23 23:56:43 ark1 dhclient[11114]: dhclient.c:1966: Failed to send 300 byte long packet over eth0 interface.
sept. 23 23:56:51 ark1 dhclient[11114]: No DHCPOFFERS received.
sept. 23 23:56:51 ark1 dhclient[11114]: No working leases in persistent database - sleeping.
sept. 23 23:56:51 ark1 avahi-autoipd(eth0)[13229]: Found user 'avahi-autoipd' (UID 109) and group 'avahi-autoipd' (GID 118).
sept. 23 23:56:51 ark1 avahi-autoipd(eth0)[13229]: Successfully called chroot().
sept. 23 23:56:51 ark1 avahi-autoipd(eth0)[13229]: Successfully dropped root privileges.
sept. 23 23:56:51 ark1 avahi-autoipd(eth0)[13229]: Starting with address 169.254.1.156
sept. 23 23:56:57 ark1 avahi-autoipd(eth0)[13229]: Callout BIND, address 169.254.1.156 on interface eth0
sept. 23 23:56:57 ark1 avahi-daemon[528]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.1.156.
sept. 23 23:56:57 ark1 avahi-daemon[528]: New relevant interface eth0.IPv4 for mDNS.
sept. 23 23:56:57 ark1 avahi-daemon[528]: Registering new address record for 169.254.1.156 on eth0.IPv4.
sept. 23 23:57:01 ark1 avahi-autoipd(eth0)[13229]: Successfully claimed IP address 169.254.1.156
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR'
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
sept. 23 23:59:08 ark1 ModemManager[518]: <info>  Simple connect started...
sept. 23 23:59:08 ark1 ModemManager[518]: <info>  Simple connect state (4/8): Wait to get fully enabled
sept. 23 23:59:08 ark1 ModemManager[518]: <info>  Simple connect state (5/8): Register
sept. 23 23:59:08 ark1 ModemManager[518]: <info>  Simple connect state (6/8): Bearer
sept. 23 23:59:08 ark1 ModemManager[518]: <info>  Simple connect state (7/8): Connect
sept. 23 23:59:08 ark1 ModemManager[518]: <info>  Simple connect state (8/8): All done
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: prepare -> config (reason 'none') [40 50 0]
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful.
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled.
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete.
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: config -> ip-config (reason 'none') [50 70 0]
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> dhclient started with pid 13236
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete.
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) started...
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
sept. 23 23:59:08 ark1 NetworkManager[9446]: <info> (eth0): DHCPv4 state changed nbi -> preinit
sept. 23 23:59:09 ark1 dhclient[13236]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
sept. 23 23:59:17 ark1 dhclient[13236]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
sept. 23 23:59:31 ark1 dhclient[13236]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
sept. 23 23:59:34 ark1 dhclient[13236]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
sept. 23 23:59:38 ark1 dhclient[13236]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
sept. 23 23:59:49 ark1 dhclient[13236]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
sept. 23 23:59:53 ark1 NetworkManager[9446]: <warn> (eth0): DHCPv4 request timed out.
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> (eth0): canceled DHCP transaction, DHCP client pid 13236
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) started...
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
sept. 23 23:59:53 ark1 NetworkManager[9446]: <warn> Activation (ttyUSB0) failed for connection 'SFR'
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0]
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): deactivating device (reason 'none') [0]
sept. 23 23:59:53 ark1 avahi-daemon[528]: Withdrawing address record for 169.254.1.156 on eth0.
sept. 23 23:59:53 ark1 avahi-daemon[528]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.1.156.
sept. 23 23:59:53 ark1 avahi-daemon[528]: Interface eth0.IPv4 no longer relevant for mDNS.
sept. 23 23:59:53 ark1 dhclient[11114]: receive_packet failed on eth0: Network is down
sept. 23 23:59:53 ark1 avahi-autoipd(eth0)[13229]: SIOCSIFFLAGS failed: Operation not permitted
sept. 23 23:59:53 ark1 avahi-autoipd(eth0)[13229]: Callout STOP, address 169.254.1.156 on interface eth0
sept. 23 23:59:53 ark1 ModemManager[518]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> disconnecting)
sept. 23 23:59:53 ark1 ModemManager[518]: <warn>  Couldn't find associated cdc-wdm port for 'net/eth0'
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> (ttyUSB0): modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
sept. 23 23:59:53 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.

Eu também tentei a resposta de Wouter Verhelst, mas não funcionou: 

systemctl restart ModemManager

EDIT 3:

NetworkManager.conf file: 

[main] plugins=ifupdown,keyfile

[ifupdown] managed=false

EDIT 4: 

$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:0b:ab:9d:7c:20 brd ff:ff:ff:ff:ff:ff
3: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:0b:ab:9c:29:84 brd ff:ff:ff:ff:ff:ff
4: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:0b:ab:9c:29:85 brd ff:ff:ff:ff:ff:ff
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff

EDIT 5:

Quando a conexão está funcionando: 

ps ax | grep 'pppd' | grep -v 'grep'

não produz nada.

EDIT 6: 

~$ mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id 'cd32f4358dd82cdb976fcc9df44df11737726856')
  -------------------------
  Hardware |   manufacturer: 'Huawei Technologies Co., Ltd.'
           |          model: 'MU709s-2'
           |       revision: '11.651.67.00.00'
           |      supported: 'gsm-umts'
           |        current: 'gsm-umts'
           |   equipment id: '864881021266208'
  -------------------------
  System   |         device: '/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-6'
           |        drivers: 'option1, cdc_ether'
           |         plugin: 'Huawei'
           |   primary port: 'ttyUSB0'
           |          ports: 'ttyUSB0 (at), ttyUSB2 (at), ttyUSB3 (at), eth0 (net)'
  -------------------------
  Numbers  |           own : 'unknown'
  -------------------------
  Status   |           lock: 'none'
           | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
           |          state: 'connected'
           |    power state: 'on'
           |    access tech: 'umts'
           | signal quality: '32' (recent)
  -------------------------
  Modes    |      supported: 'allowed: 2g, 3g; preferred: none
           |                  allowed: 2g, 3g; preferred: 2g
           |                  allowed: 2g, 3g; preferred: 3g
           |                  allowed: 2g; preferred: none
           |                  allowed: 3g; preferred: none'
           |        current: 'allowed: 2g, 3g; preferred: 3g'
  -------------------------
  Bands    |      supported: 'unknown'
           |        current: 'unknown'
  -------------------------
  IP       |      supported: 'ipv4'
  -------------------------
  3GPP     |           imei: '864881021266208'
           |  enabled locks: 'none'
           |    operator id: '20810'
           |  operator name: 'F SFR'
           |   subscription: 'unknown'
           |   registration: 'home'
  -------------------------
  SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'

  -------------------------
  Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'

LAST EDIT:

A única solução que encontrei foi alterar o modem MU709 para o VIA EMIO-2550. Eu não tenho problemas de conexão com o VIA.

    
por Romain 23.09.2015 / 19:30

3 respostas

3

Tem certeza de que sua conexão GSM usa a interface eth0 ? Na maioria dos casos, é ppp0 , wwan0 ou usb0 com o protocolo MBIM mais recente. A interface eth0 com banda larga móvel é bastante incomum.

Parece que sua placa GMS usa a interface /dev/ttyUSB0 para se conectar à rede de banda larga móvel real via pppd e transfere essa conexão para uma rede DHCP privada por meio da interface eth0 . O intervalo de IP 169.254.x.x é o endereço local de link, usado para fornecer conexão DHCP simples.

Portanto, a banda larga móvel não estará disponível se o NetworkManager não conseguir discar a conexão do pppd.

Minha experiência, os ISPs nunca alteram o endereço IP se você estiver conectado, e eles sempre fornecem endereços IP diferentes após cada reconexão, pelo menos com banda larga móvel.

Agora, o que acontece, (novamente, minha experiência pessoal), o modem desliga , já que esta é uma placa mini PCIe, você não pode simplesmente conectá-la e conectá-la. Aqui os comandos AT antiquados são úteis.

Tente conectar a /dev/ttyUSB0 port com seu aplicativo de conexão serial favorito, como Putty , minicom , cutecom , cu , busybox microcom etc. etc. Estou usando o% co_de bruto %. 

nmcli radio wwan off
sudo busybox microcom -t 10000 /dev/ttyUSB0

Coloque esses comandos AT lá. 

ATZ
AT+CFUN=0

Aguarde 10 segundos. e conecte-o novamente. 

sudo busybox microcom -t 10000 /dev/ttyUSB0
AT+CFUN=1

Agora saia e tente conectar-se por meio do applet NetworkManager novamente.

Quando a conexão de banda larga móvel estiver ativa, execute o comando abaixo e atualize sua pergunta. 

ps ax | grep 'pppd' | grep -v 'grep'

Seu cartão GSM é ótimo, com muitos recursos avançados, mas infelizmente não está funcionando corretamente.

    
por 30.09.2015 / 19:36
2

O NetworkManager está envolvido em lidar com o modem 3G, mas apenas de maneira pequena. O programa atual que fala com o seu modem é chamado ModemManager. Eu notei no meu laptop que às vezes perde a conexão também, e então 

systemctl restart ModemManager

é suficiente.

    
por 24.09.2015 / 00:26
1

A saída de log de journalctl não está clara sobre o que está causando isso. Eu recomendaria fazer o seguinte na ordem:

1). Tente configurar manualmente a interface quando isso acontecer: 

ifconfig eth0 up

Como alternativa, se você não tiver o ifconfig instalado, poderá fazer isso com ip : 

ip link set dev eth0 up

2). Se isso não ajudar, verifique /var/log/syslog para mensagens relacionadas.

Se eu tivesse que dar um palpite, esta é uma questão de configuração associada ao próprio modem. Você pode postar o arquivo de configuração do NetworkManager, retirando qualquer informação sensível que possa estar nele?

    
por 30.09.2015 / 16:07

Tags

Atualize Debian de 7.3 para 7.5 (NÃO para 7.9 ou 8) Como verificar no terminal se alguma GUI instalada no UBUNTU