# Unable to SSH or fwupdate to new Mangoh red **URL:** \ **Category:** mangOH Red\ **Created:** [September 22, 2020, 5:41pm UTC](https://mangoh.discourse.group/t/unable-to-ssh-or-fwupdate-to-new-mangoh-red/5274 "2020-09-22T17:41:10Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jameswollaeger](https://avatars.discourse-cdn.com/v4/letter/j/e495f1/32.png) [@jameswollaeger](https://mangoh.discourse.group/u/jameswollaeger)\ **Post date:** [September 22, 2020, 5:41pm UTC](https://mangoh.discourse.group/t/unable-to-ssh-or-fwupdate-to-new-mangoh-red/5274/1 "2020-09-22T17:41:10Z")
Hello, I’m fairly new to Mango Red and trying to connect via SSH to the board from the Mangoh provided Ubuntu image. I cannot get the board to respond to ssh in Ubuntu and I also get a no route to host when trying to fwupdate a build that I completed after going through the tutorials online. mangoh@mangoh-dev:~/Documents/MangohTutorial/mangOH/build$ fwupdate download red\_wp77xx.spk 192.168.2.2 \*\*\*ERROR: Device address 192.168.2.2 seems to be unreachable. Try ‘fwupdate --help’ for usage instructions. mangoh@mangoh-dev:~/Documents/MangohTutorial/mangOH/build$ ifconfig enp0s3: flags=4163\ mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::82b:3d94:da65:d15a prefixlen 64 scopeid 0x20 ether 08:00:27:73:ea:26 txqueuelen 1000 (Ethernet) RX packets 15667 bytes 16364305 (16.3 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5361 bytes 501654 (501.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s6u2i19: flags=4163\ mtu 1500 inet 192.168.2.4 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fe80::50a5:e9ff:fe6a:ddd4 prefixlen 64 scopeid 0x20 ether 52:a5:e9:6a:dd:d4 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 25135 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 140 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 (Local Loopback) RX packets 2437 bytes 216131 (216.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2437 bytes 216131 (216.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 When I connect the Mangoh CF3 usb to my laptop host (running windows 10) i then proceeded to create a rule with Virutualbox so that the Sierra Wireless WP7700 shows as checked and Ubuntu sees this as a USB network adapter. I manually changed the IPV6 config to disabled and then IPV4 set to 192.168.2.4 (so they reside on the same subnet), DNS automatic, Routes Automatic (but I did check the box to only use this for resources on its network). To no avail can I get this working after reading forum topics like 2 days. I’m stuck. mangoh@mangoh-dev:~/Documents/MangohTutorial/mangOH/build$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default \_gateway 0.0.0.0 UG 100 0 0 enp0s3 10.0.2.0 0.0.0.0 255.255.255.0 U 100 0 0 enp0s3 link-local 0.0.0.0 255.255.0.0 U 1000 0 0 enp0s3 192.168.2.0 0.0.0.0 255.255.255.0 U 101 0 0 enp0s6u2i19 I can also say that when I check the config of the board via the serial console (in my windows machine) I see, so it looks good. root@swi-mdm9x28-wp:~# ifconfig bridge0 Link encap:Ethernet HWaddr EE:3F:60:F1:25:BE inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0 inet6 addr: fe80::ec3f:60ff:feee:22bb/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:152 (152.0 B) ecm0 Link encap:Ethernet HWaddr 4A:53:EC:87:07:68 inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) ---
**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:** [September 22, 2020, 11:04pm UTC](https://mangoh.discourse.group/t/unable-to-ssh-or-fwupdate-to-new-mangoh-red/5274/2 "2020-09-22T23:04:33Z")
you can shut down the firewall by the following command input to wp77 module console and see if the problem still exists. iptables -I INPUT -j ACCEPT ---
**Author:** ![pinst](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pinst](https://mangoh.discourse.group/u/pinst)\ **Post date:** [September 23, 2020, 7:41pm UTC](https://mangoh.discourse.group/t/unable-to-ssh-or-fwupdate-to-new-mangoh-red/5274/3 "2020-09-23T19:41:53Z")
> [@jameswollaeger](#): > > enp0s6u2i19: flags=4163\ mtu 1500 > inet 192.168.2.4 netmask 255.255.255.0 broadcast 192.168.2.255 For some reason your side of the link to the mangOH is showing an IP address of 192.168.2.4 rather than the normal value of 192.168.2.3. If you’re using VirtualBox you might try not assigning the USB to the guest machine. Sounds strange but I’ve heard it can work. Windows driver would probably have to be installed. ---
**Author:** ![jameswollaeger](https://avatars.discourse-cdn.com/v4/letter/j/e495f1/32.png) [@jameswollaeger](https://mangoh.discourse.group/u/jameswollaeger)\ **Post date:** [September 29, 2020, 10:20pm UTC](https://mangoh.discourse.group/t/unable-to-ssh-or-fwupdate-to-new-mangoh-red/5274/4 "2020-09-29T22:20:12Z")
Thanks! Yes, i didn’t think that if I leave it connected to windows, that my Linux VM would still be able to talk to it as the traffic is all NAT’d.