Subnet 192.168.2.0 interface not created on Ubuntu Linux system or VM


#1

I have starting using MangOH Red with WP8548, and when I connect it to my windows 10 laptop, and interface with address 192.168.2.3 is created and I can ping. But when I connect it a PC with UBUNTU 16.04 or to the VM, the interface is not created and no routing table entry is setup. So cannot ping or connect using ssh. Appreciate if anybody has seen this and have a fix/workaround.


#2

Hi,

How about “ifconfig -a” and “lsusb -t” in the Ubuntu? What did you see?


#3

Hello Jyijyi,

Thanks for checking. Below are the output for ifconfig and lsusb commands.

mangoh@mangoh-virtualbox:~$ ifconfig -a
enp0s3 Link encap:Ethernet HWaddr 08:00:27:25:62:45
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe25:6245/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:438789 errors:0 dropped:0 overruns:0 frame:0
TX packets:204309 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:366191476 (366.1 MB) TX bytes:12309273 (12.3 MB)

enp0s6u2i19 Link encap:Ethernet HWaddr 22:64:ff:f7:e4:56
inet6 addr: fe80::1bae:5625:d87a:69a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:5110 dropped:0 overruns:0 frame:0
TX packets:0 errors:52 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:8632 (8.6 KB) TX bytes:8632 (8.6 KB)

wwp0s6u2i8 Link encap:Ethernet HWaddr a2:b0:cf:c4:58:87
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)

mangoh@mangoh-virtualbox:~ lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 12, If 0, Class=Vendor Specific Class, Driver=qcserial, 12M |__ Port 2: Dev 12, If 2, Class=Vendor Specific Class, Driver=qcserial, 12M |__ Port 2: Dev 12, If 3, Class=Vendor Specific Class, Driver=qcserial, 12M |__ Port 2: Dev 12, If 4, Class=Vendor Specific Class, Driver=, 12M |__ Port 2: Dev 12, If 8, Class=Vendor Specific Class, Driver=qmi_wwan, 12M |__ Port 2: Dev 12, If 19, Class=Communications, Driver=cdc_ether, 12M |__ Port 2: Dev 12, If 20, Class=CDC Data, Driver=cdc_ether, 12M |__ Port 3: Dev 13, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M mangoh@mangoh-virtualbox:~

Regards,
Ajit


#4

Hi,

I guess “Port 2: Dev 12” is the module WP8 as I can see cdc_ether for the ECM port.
Can you check in dmesg whether "enp0s3 ", "enp0s6u2i19 " or "wwp0s6u2i8 " is the interface of the module?
You can unplug and compare the “ifconfig -a” to see which interface has been removed.

After that you can use “sudo dhclient <interface_name_here>” command to get IP address for the interface.


#5

Hello Jyijyi,

enp0s3 is the host interface address. The other 2 are created when the mangOH is connected.

I tried the dhclient command, and the address is not being assigned.

Below is the output of dmesg.

91036.327506] usb 1-2: Product: WP8548

[91036.327508] usb 1-2: Manufacturer: Sierra Wireless, Incorporated

[91036.327510] usb 1-2: SerialNumber: 0123456789ABCDEF

[91036.334993] qcserial 1-2:1.0: Qualcomm USB modem converter detected

[91036.335439] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0

[91036.338568] qcserial 1-2:1.2: Qualcomm USB modem converter detected

[91036.338888] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB1

[91036.344328] qcserial 1-2:1.3: Qualcomm USB modem converter detected

[91036.344649] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB2

[91036.348593] qmi_wwan 1-2:1.8: cdc-wdm0: USB WDM device

[91036.349002] qmi_wwan 1-2:1.8 wwan0: register ‘qmi_wwan’ at usb-0000:00:06.0-2, WWAN/QMI device, c2:00:30:15:be:11

[91036.367654] cdc_ether 1-2:1.19 usb0: register ‘cdc_ether’ at usb-0000:00:06.0-2, CDC Ethernet Device, 22:64:ff:f7:e4:56

[91036.400993] qmi_wwan 1-2:1.8 wwp0s6u2i8: renamed from wwan0

[91036.419523] cdc_ether 1-2:1.19 enp0s6u2i19: renamed from usb0

[91036.463998] IPv6: ADDRCONF(NETDEV_UP): enp0s6u2i19: link is not ready

[91036.464146] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91036.470220] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91036.481379] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91064.266924] usb 1-3: new full-speed USB device number 13 using ohci-pci

[91064.738205] usb 1-3: New USB device found, idVendor=0403, idProduct=6015

[91064.738209] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[91064.738212] usb 1-3: Product: FT230X Basic UART

[91064.738213] usb 1-3: Manufacturer: FTDI

[91064.738215] usb 1-3: SerialNumber: DM006GL4

[91064.750206] ftdi_sio 1-3:1.0: FTDI USB Serial Device converter detected

[91064.750234] usb 1-3: Detected FT-X

[91064.764029] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB3

[91081.918182] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91081.940364] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91126.839823] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91126.856556] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91171.845702] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91171.863503] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91191.034888] ftdi_sio ttyUSB3: usb_serial_generic_read_bulk_callback - urb stopped: -32

[91216.836559] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91516.854951] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91561.842941] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91561.861627] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

[91606.845731] cdc_ether 1-2:1.19 enp0s6u2i19: kevent 12 may have been dropped

mangoh@mangoh-virtualbox:~$


#6

Hi,

Can you try “sudo dhclient enp0s6u2i19” ?
Does this work?

I am using this FW:https://source.sierrawireless.com/resources/legato/wpfirmwarerelease13_1/

Maybe you can try the same as my test.


#7

I have tried the dhclient command on the enp0s6u2i19. That did not work. As for the firmware, I believe you need the network connectivity to install it. Would not we have the install the full environment so that we have a compatible set (OS, Firmware, Legato, …)?


#8

For the FW, you can just download the one click exe file which is combined file for OS, Firmware, Legato.
After that you can run it in Windows to upgrade the FW.


#9

You should also check if you config the ECM interface in UART console:
root@swi-mdm9x15:~# configEcm show
target.ipV4: 192.168.2.2
host.ipV4: 192.168.2.3
netmask.ipV4: 255.255.255.0
DONE