# Can't ping/ssh anymore my mangOH Red **URL:** \ **Category:** mangOH Red\ **Created:** [December 1, 2020, 11:45am UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756 "2020-12-01T11:45:18Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sebastienmaviel](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sebastienmaviel](https://mangoh.discourse.group/u/sebastienmaviel)\ **Post date:** [December 1, 2020, 11:45am UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/1 "2020-12-01T11:45:18Z")
I changed my Linux Distro on my mangOH to add ext4 support, and since then I can’t ping/ssh my mangOH. Here is some infos: > **dmesg** > > ``` > [2424.575806] usb 1-3: New USB device found, idVendor=1199, idProduct=68c0, bcdDevice= 3.18 > [2424.575812] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [2424.575816] usb 1-3: Product: Sierra Wireless WP7702 > [2424.575819] usb 1-3: Manufacturer: Sierra Wireless, Incorporated > [2424.575821] usb 1-3: SerialNumber: VU81038517021013 > [2424.600407] qcserial 1-3:1.0: Qualcomm USB modem converter detected > [2424.600651] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0 > [2424.601534] qcserial 1-3:1.2: Qualcomm USB modem converter detected > [2424.601722] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB1 > [2424.603442] qcserial 1-3:1.3: Qualcomm USB modem converter detected > [2424.603686] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB2 > [2424.605523] qmi_wwan 1-3:1.8: cdc-wdm1: USB WDM device > [2424.615611] qmi_wwan 1-3:1.8 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-3, WWAN/QMI device, 5e:56:15:d0:fa:d1 > [2424.623801] cdc_ether 1-3:1.19 usb0: register 'cdc_ether' at usb-0000:00:14.0-3, CDC Ethernet Device, 5e:24:37:40:fd:8c > [2424.644341] qmi_wwan 1-3:1.8 wwp0s20f0u3i8: renamed from wwan0 > [2424.674078] cdc_ether 1-3:1.19 enp0s20f0u3i19: renamed from usb0 > > ``` > **ifconfig -a** > > ``` > docker0: flags=4099 mtu 1500 > inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 > ether 02:42:a2:8d:01:79 txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > enp0s20f0u3i19: flags=4098 mtu 1500 > ether 52:d8:54:86:99:3c txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > enp59s0: flags=4098 mtu 1500 > ether 70:b5:e8:a7:b9:c5 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1000 (Boucle locale) > RX packets 5953 bytes 596166 (596.1 KB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 5953 bytes 596166 (596.1 KB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > wlp0s20f3: flags=4163 mtu 1500 > inet 192.168.0.39 netmask 255.255.255.0 broadcast 192.168.0.255 > inet6 fe80::36fd:9c2a:3a3:e9c4 prefixlen 64 scopeid 0x20 > ether f8:ac:65:ff:24:c7 txqueuelen 1000 (Ethernet) > RX packets 20897 bytes 16551370 (16.5 MB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 14983 bytes 3118428 (3.1 MB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > wwp0s20f0u3i8: flags=4098 mtu 1500 > ether 36:86:5d:b7:dd:bb txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > ``` My modem interface and my ethernet interface looks well. I tried then to renew my IP address from my ethernet interface > **sudo dhclient -r -v enp0s20f0u3i19** > > ``` > Internet Systems Consortium DHCP Client 4.3.5 > Copyright 2004-2016 Internet Systems Consortium. > All rights reserved. > For info, please visit https://www.isc.org/software/dhcp/ > > Listening on LPF/enp0s20f0u3i19/ce:4b:de:3e:d5:1a > Sending on LPF/enp0s20f0u3i19/ce:4b:de:3e:d5:1a > Sending on Socket/fallback > DHCPRELEASE on enp0s20f0u3i19 to 192.168.2.2 port 67 (xid=0x2ce2709) > > ``` Still doesn’t work … Any ideas to resolve that ? Thanks a lot ! ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [December 1, 2020, 12:10pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/2 "2020-12-01T12:10:26Z")
You can manually set the ip address: sudo ifconfig enp0s20f0u3i19 192.168.2.3 ---
**Author:** ![sebastienmaviel](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sebastienmaviel](https://mangoh.discourse.group/u/sebastienmaviel)\ **Post date:** [December 1, 2020, 12:16pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/3 "2020-12-01T12:16:37Z")
Thanks for your answer. Done that, but still can’t ping and ssh into it (“Connection refused”) ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [December 1, 2020, 12:20pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/4 "2020-12-01T12:20:13Z")
you can shut down the firewall by the following command in module’s UART console and see if the problem still exists. iptables -I INPUT -j ACCEPT ---
**Author:** ![sebastienmaviel](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sebastienmaviel](https://mangoh.discourse.group/u/sebastienmaviel)\ **Post date:** [December 1, 2020, 12:48pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/5 "2020-12-01T12:48:00Z")
Hmm, I can’t type anything with minicom, looks like I can’t connect ? Here is what i see (nothing change after a reboot). > **sudo minicom -D /dev/ttyUSB0** > > ``` > Bienvenue avec minicom 2.7.1 > > OPTIONS: I18n > Compilé le Aug 13 2017, 15:25:34. > Port /dev/ttyUSB0, 13:39:04 > > Tapez CTRL-A Z pour voir l'aide concernant les touches spéciales > > ``` > **dmesg** > > [7577.911111] usb 1-2: new full-speed USB device number 52 using xhci\_hcd > [7578.070604] usb 1-2: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00 > [7578.070610] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [7578.070614] usb 1-2: Product: FT230X Basic UART > [7578.070617] usb 1-2: Manufacturer: FTDI > [7578.070619] usb 1-2: SerialNumber: DM01A3IT > [7578.075735] ftdi\_sio 1-2:1.0: FTDI USB Serial Device converter detected > [7578.075802] usb 1-2: Detected FT-X > [7578.077019] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [December 1, 2020, 1:02pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/6 "2020-12-01T13:02:13Z")
try baud rate 115200 and disable flow control. Also if you connect USB cable to PC, it should enumerate /dev/ttyUSB port. One of it is AT command port, you can check there and see if the UART has been mapped to linux console by AT!MAPUART? ---
**Author:** ![sebastienmaviel](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sebastienmaviel](https://mangoh.discourse.group/u/sebastienmaviel)\ **Post date:** [December 1, 2020, 1:08pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/7 "2020-12-01T13:08:38Z")
Still not working with the flow control disabled. I can’t find this AT port, where is it ? Only got this. maviel@smaviel-g5:~$ ls /dev/ttyUSB\* /dev/ttyUSB0 ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [December 1, 2020, 1:20pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/8 "2020-12-01T13:20:42Z")
at beginning, you have /dev/ttyUSB0 /dev/ttyUSB1, /dev/ttyUSB2, but now only having one port… what have you done? [2424.575816] usb 1-3: Product: Sierra Wireless WP7702 [2424.575819] usb 1-3: Manufacturer: Sierra Wireless, Incorporated [2424.575821] usb 1-3: SerialNumber: VU81038517021013 [2424.600407] qcserial 1-3:1.0: Qualcomm USB modem converter detected [2424.600651] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0 [2424.601534] qcserial 1-3:1.2: Qualcomm USB modem converter detected [2424.601722] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB1 [2424.603442] qcserial 1-3:1.3: Qualcomm USB modem converter detected [2424.603686] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB2 ---
**Author:** ![sebastienmaviel](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sebastienmaviel](https://mangoh.discourse.group/u/sebastienmaviel)\ **Post date:** [December 1, 2020, 2:58pm UTC](https://mangoh.discourse.group/t/cant-ping-ssh-anymore-my-mangoh-red/5756/9 "2020-12-01T14:58:14Z")
Yes, sorry about that, only my CON USB was plugged at this moment. I then succeed to connect to the console but shutting down the firewall solved nothing. I solved this issue by resetting completely the mangOH. Thanks for your support.