Cannot ping WP7700 module (MangOH red) from Ubuntu-VM

IoT Modules WP Series
1

Ubuntu 16.04 VM (Win10 host) can serially connect to module and login but cannot Ping 192.168.2.2. Can ping from Win10 (no VM running) so Module is ok.
Sierra Wireless USB ports are enabled to Ubuntu VM and GobiSerial/GobiNet is running.

…I’ve googled for 3 days and tried everything, but:
“ping 192.168.2.2” - always gets no response.

The infoconfig -a cmd does indicate the Sierra Module ports;
enp0s11u1i8 Link encap:Ethernet HWaddr 2a:6c:e1:8f:34:4e
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)

enp0s11u1i19 Link encap:Ethernet HWaddr ca:04:c4:04:89:be
inet6 addr: fe80::3c81:8cf0:2da9:d5a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:120 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

furthermore a dmesg indicates that enp0s11u1i8 renamed from eth0 and enp0s11u1i19 renamed from usb0
…also this:
[ 1041.405521] usb 1-1: New USB device found, idVendor=1199, idProduct=68c0
[ 1041.405524] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1041.405526] usb 1-1: Product: Sierra Wireless WP7700
[ 1041.405527] usb 1-1: Manufacturer: Sierra Wireless, Incorporated
[ 1041.405529] usb 1-1: SerialNumber: W881038511031015
[ 1041.413307] GobiSerial 1-1:1.0: GobiSerial converter detected
[ 1041.413395] usb 1-1: GobiSerial converter now attached to ttyUSB2
[ 1041.417183] GobiSerial 1-1:1.2: GobiSerial converter detected
[ 1041.417248] usb 1-1: GobiSerial converter now attached to ttyUSB3
[ 1041.423998] GobiSerial 1-1:1.3: GobiSerial converter detected
[ 1041.424072] usb 1-1: GobiSerial converter now attached to ttyUSB4
[ 1041.429120] QMAP Disabled
[ 1041.432308] GobiNet 1-1:1.8 eth0: register ‘GobiNet’ at usb-0000:00:0b.0-1, GobiNet Ethernet Device, 2a:6c:e1:8f:34:4e
[ 1041.435820] USB Speed : USB 2.0
[ 1041.450739] cdc_ether 1-1:1.19 usb0: register ‘cdc_ether’ at usb-0000:00:0b.0-1, CDC Ethernet Device, ca:04:c4:04:89:be
[ 1041.481633] cdc_ether 1-1:1.19 enp0s11u1i19: renamed from usb0
[ 1041.496966] GobiNet 1-1:1.8 enp0s11u1i8: renamed from eth0
[ 1041.520568] IPv6: ADDRCONF(NETDEV_UP): enp0s11u1i19: link is not ready
…
[ 1041.556615] IPv6: ADDRCONF(NETDEV_UP): enp0s11u1i8: link is not ready

What the heck am I missing?

HELP!

2

Sudo ifconfig usb0 192.168.2.3

3

Thank you

  • can you please explain why setting usb0 to 192.168.2.3 would impact 192.168.2.2? (or was the 3 a typo?)

thanks!

4

Is your wp77 module having Ip 192.168.2.2?

5

Yes. This particular WP7700 is installed in a MangOH red eval platform.

6

So if you set the pc to have ip add 192.168.2.3, then they are within same subnet and able to ping each other.

7

Thanks - so just to clarify: I’m setting the PC-VM’s usb port to 192.168.2.3 so it is on the same subnet - thus I can ping the module’s 192.168.2.2 port.
thanks again,
mike

8

It is a no-go:
mbp@ubuntu:~$ sudo ifconfig usb0 192.168.2.3
SIOCSIFADDR: No such device
usb0: ERROR while getting interface flags: No such device

I also tried:
mbp@ubuntu:~ sudo ifconfig enp0s11u1i19 192.168.2.3 mbp@ubuntu:~ ping 192.168.2.2
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
From 192.168.2.3 icmp_seq=1 Destination Host Unreachable
From 192.168.2.3 icmp_seq=2 Destination Host Unreachable
From 192.168.2.3 icmp_seq=3 Destination Host Unreachable

…as you can see NO-GO.

Finally I tried updating the /etc/network/interfaces file with
auto enp0s11u1i19
iface enp0s11u1i19 inet static
address 192.168.2.5
broadcast 255.255.255.0

as can be verified by:
enp0s11u1i19 Link encap:Ethernet HWaddr 42:df:84:c8:2f:dc
inet addr:192.168.2.5 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::40df:84ff:fec8:2fdc/64 Scope:Link
UP BROADCAST RUNNING 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)

Still yields this:
mbp@ubuntu:~$ ping 192.168.2.2
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
From 192.168.2.5 icmp_seq=1 Destination Host Unreachable
From 192.168.2.5 icmp_seq=2 Destination Host Unreachable
…
()tried with 192.168.2.3 as well - no different, still fails).

Completely befuddled! :confused:

9

Maybe you can try disable the network manager and set the default network interface to be usb0.
Also you can check the correct name of usb0 in dmesg.

10

jyijyi,
Thanks for your continued support.

I have stumbled across the issue. When the VM (Ubuntu) owns the port it cannot ping that port. When the host (Win10) owns the port the VM can ping through that port.

COMPLETELY counter-intuitive. …in the future I may analyze to discover why this is. For now, however, I will move along.

Thanks for your help & input.