새로운 IP를 제공한 후 3G 연결을 다시 연결할 수 없습니다

새로운 IP를 제공한 후 3G 연결을 다시 연결할 수 없습니다

저는 Debian Jessie 8.2를 사용하고 있으며 3G 연결을 사용하고 있습니다.화웨이 MU709 미니 PCIe.

3G 연결은 잘 작동하지만 24시간이 지나면 연결이 끊어지고 다시 연결할 수 없습니다. 컴퓨터를 다시 시작하면 연결이 다시 작동합니다.

내 생각엔 내 ISP가 24시간 후에 나에게 새 IP 주소를 제공했지만 내 시스템이 이를 처리할 수 없었던 것 같습니다.

다시 시작하지 않고 3G 연결을 다시 연결하는 방법은 무엇입니까?

다음 명령을 시도했습니다.

sudo service network-manager restart

그리고:

dhclient -r eth0
dhclient eth0

편집 1:

journalctl결과에 대한 내 연결 이름을 grep합니다( 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'

보시 sept 22 at time 17:18다시피 컴퓨터가 부팅되는 순간입니다. 약 24시간이 지나면 재접속이 불가능해집니다.

또한 명령을 실행하는 스크립트가 있다는 점을 언급해야 합니다.

sudo service network-manager restart

컴퓨터가 서버에 대해 ping을 수행할 수 없으면 연결이 끊어집니다.

편집 2:journalctl시스템이 다시 연결을 시도할 때 추가 정보를 추가합니다.

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'.

나는 또한 성공하지 못한 채 Wouter Verhelst의 답변을 시도했습니다.

systemctl restart ModemManager

편집 3:

NetworkManager.conf문서:

[main] plugins=ifupdown,keyfile

[ifupdown] managed=false

편집 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

편집 5:

연결이 작동하는 경우:

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

아무것도 출력하지 않습니다.

편집 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'

마지막 수정:

내가 찾은 유일한 해결책은 MU709 모뎀을 VIA EMIO-2550으로 변경하는 것이었습니다. VIA에 연결 문제가 없습니다.

답변1

GSM 연결에서 어떤 인터페이스를 사용하고 있는지 확실합니까 eth0? 대부분의 경우 이것이 사실 ppp0이거나 최신 MBIM 프로토콜이 사용됩니다 wwan0. 모바일 광대역과의 인터페이스는 매우 드뭅니다.usb0eth0

귀하의 GMS 카드는 이 /dev/ttyUSB0인터페이스를 사용하여 실제 모바일 광대역 네트워크에 연결하고 pppd이 인터페이스를 통해 eth0개인 DHCP 네트워크에 대한 연결을 전달하는 것으로 보입니다. 169.254.xx IP 범위는 간단한 DHCP 연결을 제공하는 데 사용되는 링크-로컬 주소입니다.

따라서 NetworkManager가 pppd 연결을 설정할 수 없으면 모바일 광대역을 사용할 수 없습니다.

내 경험에 따르면 ISP는 연결된 경우 IP 주소를 절대 변경하지 않으며 적어도 모바일 광대역의 경우 다시 연결할 때마다 항상 다른 IP 주소를 제공합니다.

지금 무슨 일이 일어나고 있는 걸까요(다시 말하지만, 제 개인적인 경험입니다) 모뎀안녕, 미니 PCIe 카드이므로 간단히 꽂았다가 뺄 수 없습니다. 여기는 구식이야존재하다명령이 유용합니다.

즐겨 사용하는 직렬 연결 애플리케이션으로 포트를 연결해 보십시오 /dev/ttyUSB0. Putty저는 원본을 사용하고 있어요.minicomcutecomcubusybox microcombusybox microcom

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

여기에 AT 명령을 입력하세요.

ATZ
AT+CFUN=0

10초 동안 기다립니다. 그리고 다시 연결하세요.

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

이제 종료하고 NetworkManager 애플릿을 통해 다시 연결해 보십시오.

모바일 광대역 연결이 활성화되면 다음 명령을 실행하고 질문을 업데이트하십시오.

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

귀하의 GSM 카드는 훌륭하고 많은 고급 기능을 갖추고 있지만 안타깝게도 제대로 작동하지 않습니다.

답변2

NetworkManager는 3G 모뎀 처리에 관여하지만 작은 부분일 뿐입니다. 모뎀과 통신하는 실제 프로그램은 ModemManager라고 합니다. 내 노트북도 가끔 연결이 끊어지는 것을 발견했습니다.

systemctl restart ModemManager

충분한.

답변3

로그 출력에서는 journalctl이러한 일이 발생하는 원인이 무엇인지 명확하게 밝히지 않습니다. 다음을 순서대로 수행하는 것이 좋습니다.

1). 이 경우 인터페이스를 수동으로 설정해 보십시오.

ifconfig eth0 up

또는 ifconfig아직 설치하지 않은 경우 다음 명령을 사용하여 설치할 수 있습니다 ip.

ip link set dev eth0 up

2). 그래도 도움이 되지 않으면 /var/log/syslog관련 메시지를 확인하세요.

경험을 바탕으로 추측해야 한다면 이는 모뎀 자체와 관련된 구성 문제입니다. NetworkManager 구성 파일 자체를 게시하고 여기에 포함될 수 있는 민감한 정보를 제거할 수 있습니까?

관련 정보