# Failed to ping 192.168.2.2 or ssh root@192.168.2.2 on Legato VM

**URL:** https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484
**Category:** mangOH Red
**Created:** [May 20, 2020, 8:39pm UTC](https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484 "2020-05-20T20:39:07Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jeremyzhang](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jeremyzhang](https://mangoh.discourse.group/u/jeremyzhang)
#### Post date: [May 20, 2020, 8:39pm UTC](https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484/1 "2020-05-20T20:39:07Z")

</div>

I have successfully installed the proper drivers on my host machine, Win 10. And ping 192.168.2.2 and ssh [root@192.168.2.2](mailto:root@192.168.2.2) works on my host machine through Powershell (shown in screenshot below).

 ![image](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/2X/2/25b0a369c7da52e3fa35c1708250e593a2bbef89.png)

However, neither ping nor ssh succeeds on my virtual machine, Legato VM under Virtualbox. The device is recognized by VM (screenshot below), and I’m pretty sure it worked before, but when I re-plug in, it just stopped working.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/2X/3/360df8759ab4a691f5a8b75aeb550b9795764468.png)

The screenshot below is the USB settings on Virtual Box.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/2X/2/20b204b370e9336418739590e84d9d76f62b9911.png)

---

<div class="post-metadata">

### 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: [May 21, 2020, 12:19am UTC](https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484/2 "2020-05-21T00:19:00Z")

</div>

Seems you need to type

sudo ifconfig usb0 192.168.2.3

---

<div class="post-metadata">

### Author: ![jeremyzhang](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jeremyzhang](https://mangoh.discourse.group/u/jeremyzhang)
#### Post date: [May 21, 2020, 3:35am UTC](https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484/3 "2020-05-21T03:35:42Z")

</div>

I tried, but it looks not working

 ![image](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/2X/4/4e59a7ec115664412d48d24db994df478ea5f286.png)

---

<div class="post-metadata">

### 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: [May 21, 2020, 3:47am UTC](https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484/4 "2020-05-21T03:47:37Z")

</div>

this is just the naming problem, there is no usb0 on your linux machine.  
You need to find out the naming in dmesg.

---

<div class="post-metadata">

### Author: ![pinst](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pinst](https://mangoh.discourse.group/u/pinst)
#### Post date: [May 22, 2020, 2:01pm UTC](https://mangoh.discourse.group/t/failed-to-ping-192-168-2-2-or-ssh-root-192-168-2-2-on-legato-vm/4484/5 "2020-05-22T14:01:41Z")

</div>

I read in another thread (some time ago) that the problem went away when the USB was not attached to the VM. Sounds counter intuitive but apparently the 192.168.2.0 subnet routes OK though windows. Maybe worth a try.