AFAIK we have not tested any LTE configurations as none of the relevant Chromebooks have an LTE modem built in.

If this is necessary, could you please send me the aircard adapter + activated SIM?

Thanks!

If this objective here is to expose the cellular connectivity from ChromeOS to the Android container as a generic network connectivity (i.e. without specifically having Android to realize it's on cellular), it can probably be handled like how we expose Ethernet from ChromeOS to the Android container.

As this issue isn't specifically related to  Sierra Wireless Aircard 340U, we can test it using any external USB modem supported by ChromeOS.

Correct, it's general network connectivity for the Android container when the Chromebook has a 3G/4G USB dongle. Any dongle should be able to reproduce this issue.

Abhishek has volunteered to look at this next week.

Hi all,

We have a technical case with this issue and it looks like that certain 3g/4g modems are detected as ethernet and Android Apps work fine, while others are detected as cellular and the issue is present.

Is there any updates on this issue, or is there something we can help with through the tech case?

Thanks!

They should just be seeing TYPE_ETHERNET inside the container. If you give me the dongle I can see what's happening.

This is what I see in the arc-bugreport.txt. The first USB device is detected as  'cdc_ether' and connection succeeds while the second is detected as modem and connections fails:
1:
<6>[ 1826.217341] usb 1-1: New USB device found, idVendor=12d1, idProduct=14db 
<6>[ 1826.217361] usb 1-1: New USB device strings: Mfr=4, Product=3, SerialNumber=0 
<6>[ 1826.217373] usb 1-1: Product: HUAWEI Mobile 
<6>[ 1826.217382] usb 1-1: Manufacturer: Huawei Technologies 
<6>[ 1826.222147] platform vpd: Driver vpd requests probe deferral 
<6>[ 1826.300352] platform vpd: Driver vpd requests probe deferral 
<6>[ 1826.303295] cdc_ether 1-1:1.0 eth0: register 'cdc_ether' at usb-0000:00:14.0-1, CDC Ethernet Device, MA:Cx:xx:xx:xx:xx  
<6>[ 1826.303409] usbcore: registered new interface driver cdc_ether 
<6>[ 1826.306991] platform vpd: Driver vpd requests probe deferral 

2:
<6>[ 4248.847635] usb 1-1: new high-speed USB device number 7 using xhci_hcd 
<6>[ 4249.012470] usb 1-1: New USB device found, idVendor=12d1, idProduct=14fe 
<6>[ 4249.012489] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 
<6>[ 4249.012502] usb 1-1: Product: HUAWEI_MOBILE 
<6>[ 4249.012519] usb 1-1: Manufacturer: HUAWEI_MOBILE 
<6>[ 4249.012533] usb 1-1: SerialNumber: 0123456789ABCDEF 
<6>[ 4249.064607] usb-storage 1-1:1.0: USB Mass Storage device detected 
<6>[ 4249.065095] scsi host1: usb-storage 1-1:1.0 
<6>[ 4249.065541] platform vpd: Driver vpd requests probe deferral 
<6>[ 4249.152828] platform vpd: Driver vpd requests probe deferral 
<6>[ 4249.184389] usb 1-1: USB disconnect, device number 7 
<6>[ 4249.949622] usb 1-1: new high-speed USB device number 8 using xhci_hcd 
<6>[ 4250.114456] usb 1-1: New USB device found, idVendor=12d1, idProduct=1506 
<6>[ 4250.114475] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 
<6>[ 4250.114488] usb 1-1: Product: HUAWEI_MOBILE 
<6>[ 4250.114496] usb 1-1: Manufacturer: HUAWEI_MOBILE 
<6>[ 4250.201629] usb-storage 1-1:1.5: USB Mass Storage device detected 
<6>[ 4250.202141] scsi host2: usb-storage 1-1:1.5 
<6>[ 4250.202622] platform vpd: Driver vpd requests probe deferral 
<6>[ 4250.202965] usb-storage 1-1:1.6: USB Mass Storage device detected 
<6>[ 4250.205502] scsi host3: usb-storage 1-1:1.6 
<6>[ 4250.206440] platform vpd: Driver vpd requests probe deferral 
<6>[ 4250.233682] usbcore: registered new interface driver option 
<6>[ 4250.233739] usbserial: USB Serial support registered for GSM modem (1-port) 
<6>[ 4250.233868] option 1-1:1.0: GSM modem (1-port) converter detected 
<6>[ 4250.234384] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 
<6>[ 4250.234436] option 1-1:1.1: GSM modem (1-port) converter detected 
<6>[ 4250.234497] platform vpd: Driver vpd requests probe deferral 
<6>[ 4250.234768] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 
<6>[ 4250.234830] option 1-1:1.3: GSM modem (1-port) converter detected 
<6>[ 4250.234941] platform vpd: Driver vpd requests probe deferral 
<6>[ 4250.235110] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2 
<6>[ 4250.235153] platform vpd: Driver vpd requests probe deferral 
<6>[ 4250.235154] option 1-1:1.4: GSM modem (1-port) converter detected 
<6>[ 4250.235446] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3

Forgot to mention that both USB devices in comment #8 provide successful connectivity outside of the Arc container.

Re#7 We have our own Huawei E3131 can bring it to MTV40 to use for a while on Tuesday.

The exact USB device models that reproduce the condition per comment #8 are:
connection not available in the Arc container -- Huawei E3372 - CE0197
connection available in the Arc container -- Huawei EC315

Attaching the logs here.

Deleted: debug-logs_20170525-155046.tgz 2.0 MB

debug-logs_20170525-155046.tgz 2.0 MB Download

Deleted: debug-logs_20170525-155132.tgz 2.0 MB

debug-logs_20170525-155132.tgz 2.0 MB Download

Deleted: Screenshot 2017-05-25 at 3.24.57 PM.png 51.9 KB

	Screenshot 2017-05-25 at 3.24.57 PM.png 51.9 KB View Download

hey,

what's the latest on this bug?

#10 - has this dongle been tested in MTV40 back in May?  did this work / not?  if it did, did it get interfaced as ETH or mobile data connection?

#13 - what's the assessment on the logs (june 1st)?

there seems to be a good analysis of logs in #8 (early may).

so what are we doing with all this?  

[ Adding RBS M-61 to increase visibility. We need some kind of ETA on next steps ]

The next step was clear. We need to provide eng with a reprodcible set of steps. Since this seemed to invovled specfici hardware, we asked the sales folks to send us that hardware. That remains the next step, let's please not change that...

Ok.

I'll get on Amazon and buy one then.

Regards from my Mobile,
PeterK

[Lets reassign the bug then to the person doing the next step]

pkakasi@ were you able to source this part? Can we make this non-RBS till we have concrete repro steps?

Is there any progress with this issue that can be shared with customers?

Assigning to Dan as he owns this area now.

Eng had requested repro steps and the dongle in question was never provided. Please don't ping again unless there are updates as requested in Comment #16.

This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.