* Booted on network 1: root@SKYE20001:~# ip a 1: lo: mtu 65536 qdisc noqueue qlen 1 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: dummy0: mtu 1500 qdisc noop qlen 1000 link/ether 16:cd:4e:e0:cf:e3 brd ff:ff:ff:ff:ff:ff 3: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fc:69:47:dd:9f:62 brd ff:ff:ff:ff:ff:ff inet 172.27.0.183/22 brd 172.27.3.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::fe69:47ff:fedd:9f62/64 scope link valid_lft forever preferred_lft forever 4: wlan0: mtu 1500 qdisc mq qlen 1000 link/ether 00:e0:4c:3a:85:b3 brd ff:ff:ff:ff:ff:ff inet 192.168.99.1/24 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::2e0:4cff:fe3a:85b3/64 scope link valid_lft forever preferred_lft forever root@SKYE20001:~# ping renson-iot-dev-iotcloudcore-ioth.azure-devices.net PING renson-iot-dev-iotcloudcore-ioth.azure-devices.net (40.113.153.50): 56 data bytes traceroute renson-iot-dev-iotcloudcore-ioth.azure-devices.net traceroute to renson-iot-dev-iotcloudcore-ioth.azure-devices.net (40.113.153.50), 30 hops max, 38 byte packets 1 172.27.0.1 (172.27.0.1) 0.378 ms 0.365 ms 0.246 ms 2 172.28.0.1 (172.28.0.1) 1.147 ms 0.954 ms 0.833 ms 3 6.255-243-81.adsl-static.isp.belgacom.be (81.243.255.6) 7.941 ms 7.852 ms 8.185 ms 4 * * svc10030.epemar7.isp.proximus.com (91.183.246.197) 9.787 ms 5 ae-28-1000.idrstr2.isp.belgacom.be (91.183.246.70) 12.845 ms lag-28-1000.idrmar2.isp.belgacom.be (91.183.246.196) 10.735 ms ae-28-1000.idrstr2.isp.belgacom.be (91.183.246.70) 9.111 ms 6 ae-21-1000.ibrstr6.isp.belgacom.be (91.183.246.106) 15.610 ms lag-20-1000.ibrmar6.isp.proximus.be (91.183.246.137) 9.618 ms 9.026 ms 7 microsoft.bnix.net (194.53.172.34) 9.718 ms 10.761 ms 9.436 ms 8 ae28-0.icr01.ams21.ntwk.msn.net (104.44.233.17) 12.686 ms 12.258 ms 12.418 ms 9 * * * Connection to iot-hub is ok here. * switched to network 2 root@SKYE20001:~# ip a 1: lo: mtu 65536 qdisc noqueue qlen 1 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: dummy0: mtu 1500 qdisc noop qlen 1000 link/ether 16:cd:4e:e0:cf:e3 brd ff:ff:ff:ff:ff:ff 3: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fc:69:47:dd:9f:62 brd ff:ff:ff:ff:ff:ff inet 192.168.3.18/20 brd 192.168.15.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::fe69:47ff:fedd:9f62/64 scope link valid_lft forever preferred_lft forever 4: wlan0: mtu 1500 qdisc mq qlen 1000 link/ether 00:e0:4c:3a:85:b3 brd ff:ff:ff:ff:ff:ff inet 192.168.99.1/24 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::2e0:4cff:fe3a:85b3/64 scope link valid_lft forever preferred_lft forever root@SKYE20001:~# ping renson-iot-dev-iotcloudcore-ioth.azure-devices.net PING renson-iot-dev-iotcloudcore-ioth.azure-devices.net (40.113.153.50): 56 data bytes root@SKYE20001:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=117 time=11.710 ms traceroute to renson-iot-dev-iotcloudcore-ioth.azure-devices.net (40.113.153.50), 30 hops max, 38 byte packets 1 192.168.9.252 (192.168.9.252) 0.176 ms 0.048 ms 0.187 ms 2 192.168.9.254 (192.168.9.254) 0.302 ms 1.620 ms 0.344 ms 3 211.12-246-81.adsl-static.isp.belgacom.be (81.246.12.211) 0.566 ms 0.236 ms 0.264 ms 4 172.22.131.205 (172.22.131.205) 2.916 ms 3.010 ms 2.943 ms 5 svc10030.epemar7.isp.proximus.com (91.183.246.197) 4.496 ms * * 6 lag-28-1000.idrmar2.isp.belgacom.be (91.183.246.196) 4.216 ms ae-28-1000.idrstr2.isp.belgacom.be (91.183.246.70) 4.247 ms 4.449 ms 7 lag-20-1000.ibrmar6.isp.proximus.be (91.183.246.137) 4.221 ms 4.161 ms ae-21-1000.ibrstr6.isp.belgacom.be (91.183.246.106) 4.239 ms 8 microsoft.bnix.net (194.53.172.34) 4.783 ms 4.707 ms 4.677 ms 9 ae28-0.icr01.ams21.ntwk.msn.net (104.44.233.17) 7.936 ms 7.744 ms 7.589 ms 10 * * * After switching to network 2, connection to iot-hub fails 2020-07-07T10:22:27.623Z skye2 azure.iot.device.common.mqtt_transport INFO mqtt_transport(299): _cleanup_transport_on_error: Forcing paho disconnect to prevent it from automatically reconnecting 2020-07-07T10:22:27.626Z skye2 azure.iot.device.common.pipeline.pipeline_stages_mqtt ERROR pipeline_stages_mqtt(184): _run_op: transport.connect raised error 2020-07-07T10:22:27.632Z skye2 azure.iot.device.common.pipeline.pipeline_stages_mqtt ERROR pipeline_stages_mqtt(185): _run_op: Traceback (most recent call last): File "azure/iot/device/common/mqtt_transport.py", line 389, in connect File "paho/mqtt/client.py", line 937, in connect File "paho/mqtt/client.py", line 1071, in reconnect File "paho/mqtt/client.py", line 3522, in _create_socket_connection File "socket.py", line 707, in create_connection File "socket.py", line 752, in getaddrinfo socket.gaierror: [Errno -2] Name or service not known The above exception was the direct cause of the following exception: Traceback (most recent call last): File "azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 182, in _run_op File "azure/iot/device/common/mqtt_transport.py", line 411, in connect azure.iot.device.common.transport_exceptions.ConnectionFailedError: ConnectionFailedError(None) caused by gaierror(-2, 'Name or service not known') 2020-07-07T10:22:27.634Z skye2 azure.iot.device.common.pipeline.pipeline_ops_base ERROR pipeline_ops_base(107): complete: ConnectOperation: completing with error ConnectionFailedError(None) caused by gaierror(-2, 'Name or service not known') 2020-07-07T10:22:27.636Z skye2 azure.iot.device.common.pipeline.pipeline_stages_base ERROR pipeline_stages_base(520): on_operation_complete: ConnectionLockStage(ConnectOperation): op failed. Unblocking queue with error: ConnectionFailedError(None) caused by gaierror(-2, 'Name or service not known') 2020-07-07T10:22:27.638Z skye2 azure.iot.device.common.pipeline.pipeline_stages_base INFO pipeline_stages_base(553): _unblock: ConnectionLockStage(ConnectOperation): processing 0 items in queue 2020-07-07T10:22:37.646Z skye2 azure.iot.device.common.pipeline.pipeline_stages_mqtt INFO pipeline_stages_mqtt(170): _run_op: MQTTTransportStage(ConnectOperation): connecting 2020-07-07T10:22:37.650Z skye2 azure.iot.device.common.mqtt_transport INFO mqtt_transport(376): connect: connecting to mqtt broker 2020-07-07T10:22:37.652Z skye2 azure.iot.device.common.mqtt_transport INFO mqtt_transport(387): connect: Connect using port 8883 (TCP)