1&1 XSstick W1208 (4g systems)

thomasschaefer · Post by **thomasschaefer** » 30 Apr 2019, 21:58

Hi,

I have got a new stick. It works with the Fritzbox (ipv4 only), Windows 10 (dualstack) and Linux in all modes as long the windows OS does the switch for Linux.

Any idea how to switch from

Code: Select all

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=2fd4 ProdID=9aff Rev=03.18
S:  Manufacturer=USB Modem
S:  Product=USB Modem
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

to:

Code: Select all

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=2fd4 ProdID=76b5 Rev=03.18
S:  Manufacturer=USB Modem
S:  Product=USB Modem
C:  #Ifs= 6 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 4 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I:  If#= 5 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim

with usb_modeswitch ?

Regards,
Thomas

Post by **LOM** » 01 May 2019, 05:52

It is probably a Qualcomm device and if the StandardEject doesn't work then the first switch messages to test should be those used by mfgr's with pid 1c9e and 1e0e.
Sorry but that's the best I can come up with due to the limited info and attributes given by the usb-devices script.

thomasschaefer · Post by **thomasschaefer** » 01 May 2019, 09:50

It's a mbim device.
Eject /dev/sr0 did not work.
- j didn't find a mbim configuration.
I would like to know what is the best tool at the moment to sniff windows 10 USB to get the right method.
Wireshark?
Any other suggestions which I could try manually with usbmode switch?

Post by **LOM** » 01 May 2019, 10:44

thomasschaefer wrote:It's a mbim device.
Eject /dev/sr0 did not work.
- j didn't find a mbim configuration.

Yes I see it is a mbim device and probably an early mbim implementation.
It doesn't follow the mbim standard which requires the mbim interfaces/configuration to be visible
immediately without the device morphing.

thomasschaefer wrote: I would like to know what is the best tool at the moment to sniff windows 10 USB to get the right method.
Wireshark?

You won't find a switch message for Win10, it is very likely that the device detects how Win8 and up does the initial probing and then morphs based on that.
Starting with Win8, external Connection Managers are not allowed, external drivers are not allowed so nothing is installed from the virtual cd-rom in 2fd4:9aff. The cd-rom contents is of no value for Win8 and up.

Win7 on the other hand will use the cd-rom contents and will switch the device with a switch message, that's what you have to log.

thomasschaefer wrote: Any other suggestions which I could try manually with usbmode switch?

I've already suggested that you look at the switch messages from vid's 1c9e and 1e0e and try them, there is a total of 4-5 different. You'll find them in the usb_modeswitch datapackage.

thomasschaefer · Post by **thomasschaefer** » 01 May 2019, 11:22

Ok I will look at the device you suggested.
But in point you are wrong. The device still starts in CD-ROM-mode in windows 10. Then it installs the driver. After reboot windows manages the connection.

Post by **LOM** » 01 May 2019, 14:32

thomasschaefer wrote:Ok I will look at the device you suggested.
But in point you are wrong. The device still starts in CD-ROM-mode in windows 10. Then it installs the driver. After reboot windows manages the connection.

Which driver?
MBIM is a native protocol in Win8 and up so doesn't need an external driver.

If it behaves like you say then it breaks Microsoft mbim rules for Win8/9/10 and can not get a Windows certification.

thomasschaefer · Post by **thomasschaefer** » 01 May 2019, 16:45

LOM wrote: Which driver?
MBIM is a native protocol in Win8 and up so doesn't need an external driver.

If it behaves like you say then it breaks Microsoft mbim rules for Win8/9/10 and can not get a Windows certification.

The driver may be generic by Microsoft. But I have had to start the LTE-Antenne.exe to leave the CD-ROM mode.
If here some rules are broken. That's not my problem. Windows runs excellent with that stick, Linux only if I Windows started before.

Post by **LOM** » 01 May 2019, 17:38

thomasschaefer wrote: If here some rules are broken. That's not my problem. Windows runs excellent with that stick, Linux only if I Windows started before.

It has become your problem that the mfgr has not followed Microsofts rules for a mbim device.
As I said initially I think this is a very early mbim device, if not then it is from a mfgr who either doesn't care about following specifications or is just plain stupid.

The right way to do it is to have 2 configs, the first one having the cd-rom containing drivers and connection managers for WinXP/Win7 and the second configuration containing the mbim function. Win8/9/10 would then see the mbim configuration immediately and be able to simply select that configuration.
WinXP/Win7 would send a switch message to the cd-rom making it morph into a new device with WinXP/Win7 type of net interfaces and not mbim interfaces.

But after you now have disclosed how you switch the device then I'd say that you can probably sniff it under Win10 with Wireshark as you suggested. The older snoop/sniff programs does not work under Win10 afaik. Good luck!

thomasschaefer · Post by **thomasschaefer** » 01 May 2019, 18:51

I tried the messages you suggested.
Unfortunately they don't switch at all or to an other/different device.
I attached the attempts.

The device must be quite new. AVM developed the driver for its fritzboxes in release 7.10 and some pre releases of that. The time stamps of the windows files are from 2018.

Code: Select all

 mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id '81beb7076e1c7708aab474c1d19b44306dc83c46')
  -------------------------
  Hardware |   manufacturer: 'Generic'
           |          model: 'MBIM [2FD4:76B5]'
           |       revision: 'LWDLV10.1.1_M131'
           |      supported: 'gsm-umts, lte'
           |        current: 'gsm-umts, lte'
           |   equipment id: '862234025609555'
  -------------------------
  System   |         device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2'
           |        drivers: 'cdc_mbim'
           |         plugin: 'Generic'
           |   primary port: 'cdc-wdm0'
           |          ports: 'cdc-wdm0 (mbim), wwan0 (net)'
  -------------------------
  Numbers  |           own : '++XXXXXXXXXX'
  -------------------------
  Status   |           lock: 'none'
           | unlock retries: 'sim-pin2 (3)'
           |          state: 'connected'
           |    power state: 'on'
           |    access tech: 'lte'
           | signal quality: '0' (cached)
  -------------------------
  Modes    |      supported: 'allowed: 2g, 3g, 4g; preferred: none'
           |        current: 'allowed: 2g, 3g, 4g; preferred: none'
  -------------------------
  Bands    |      supported: 'unknown'
           |        current: 'unknown'
  -------------------------
  IP       |      supported: 'ipv4, ipv6, ipv4v6'
  -------------------------
  3GPP     |           imei: '862234025609555'
           |  enabled locks: 'fixed-dialing'
           |    operator id: '26201'
           |  operator name: 'Telekom.de'
           |   subscription: 'unknown'
           |   registration: 'home'
  -------------------------
  SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'

  -------------------------
  Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'

thomas@linux-y7a7:~/w1208>

You are are right. They deliver an app which confuses windows. Yesterday it did run without it. Today windows and the app have a conflict, so the connection failed. But they still switch the modem in the correct mode, so i can use it under linux after reboot.

I will try wireshark and post the files here. At the moment I have to find, why windows wants "pin2".

Thank You!

thomasschaefer · Post by **thomasschaefer** » 01 May 2019, 20:10

The npcap driver/service from wireshark blocked the mobile internet connection.

But nevertheless(after removing this service) usb did sniff something.
Please have a look into the attached file.

Post by **LOM** » 02 May 2019, 02:22

766 21.756006 host 1.6.1 USBMS 58 SCSI Command: 0x06 LUN:0x00

contains the switch message.

1b 00 a0 69 00 8d 01 9a ff ff 00 00 00 00 09 00
00 01 00 06 00 01 03 1f 00 00 00 55 53 42 43 a0
69 00 8d 80 00 00 00 80 00 06 06 f5 04 02 52 71
00 00 00 00 00 00 00 00 00 00

It is almost the same switch msg as is currently used for vendor 1c9e, only one byte difference (70 vs 71) , and when you used that msg the device morphed but into a different USB id with a different composition compared to what you got when switching with the LTE-Antenne program.

thomasschaefer · Post by **thomasschaefer** » 02 May 2019, 19:04

LOM wrote:766 21.756006 host 1.6.1 USBMS 58 SCSI Command: 0x06 LUN:0x00

contains the switch message.

1b 00 a0 69 00 8d 01 9a ff ff 00 00 00 00 09 00
00 01 00 06 00 01 03 1f 00 00 00 55 53 42 43 a0
69 00 8d 80 00 00 00 80 00 06 06 f5 04 02 52 71
00 00 00 00 00 00 00 00 00 00

Thanks a lot!

Code: Select all

usb_modeswitch -v 2fd4 -p 9aff -V 2fd4 -P 76b5 -M "55534243a069008d8000000080000606f50402527100000000000000000000"
Look for target devices ...
 No devices in target mode or class found
Look for default devices ...
 Found devices in default mode (1)
Access device 005 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 8
Use endpoints 0x01 (out) and 0x81 (in)
Looking for active drivers ...
 OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Read the response to message 1 (CSW) ...
 Response successfully read (13 bytes), status 0
Reset response endpoint 0x81
Reset message endpoint 0x01
 Device is gone, skip any further commands
-> Run lsusb to note any changes. Bye!

dmesg:

Code: Select all

thomas@linux-y7a7:~/w1208> dmesg 
[ 1296.776025] usb 1-2: USB disconnect, device number 5
[ 1297.194459] usb 1-2: new high-speed USB device number 6 using xhci_hcd
[ 1297.357563] usb 1-2: New USB device found, idVendor=2fd4, idProduct=76b5
[ 1297.357582] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1297.357593] usb 1-2: Product: USB Modem
[ 1297.357602] usb 1-2: Manufacturer: USB Modem
[ 1297.456032] usbcore: registered new interface driver cdc_ncm
[ 1297.457547] usbcore: registered new interface driver cdc_wdm
[ 1297.499173] cdc_mbim 1-2:1.4: cdc-wdm0: USB WDM device
[ 1297.500581] cdc_mbim 1-2:1.4 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-2, CDC MBIM, da:c4:8a:95:c2:f9
[ 1297.501885] usbcore: registered new interface driver cdc_mbim

usb-devices:

Code: Select all

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  6 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=2fd4 ProdID=76b5 Rev=03.18
S:  Manufacturer=USB Modem
S:  Product=USB Modem
C:  #Ifs= 6 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 4 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I:  If#= 5 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim

modemmanager:

Code: Select all

mmcli -L

Found 1 modems:
        /org/freedesktop/ModemManager1/Modem/0 [Generic] MBIM [2FD4:76B5]

thomas@linux-y7a7:~> mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id '81beb7076e1c7708aab474c1d19b44306dc83c46')
  -------------------------
  Hardware |   manufacturer: 'Generic'
           |          model: 'MBIM [2FD4:76B5]'
           |       revision: 'LWDLV10.1.1_M131'
           |      supported: 'gsm-umts, lte'
           |        current: 'gsm-umts, lte'
           |   equipment id: '862234025609555'
  -------------------------
  System   |         device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2'
           |        drivers: 'cdc_mbim'
           |         plugin: 'Generic'
           |   primary port: 'cdc-wdm0'
           |          ports: 'cdc-wdm0 (mbim), wwan0 (net)'
  -------------------------
  Numbers  |           own : '++XXXXXXXXXXXXX'
  -------------------------
  Status   |           lock: 'none'
           | unlock retries: 'sim-pin2 (3)'
           |          state: 'connected'
           |    power state: 'on'
           |    access tech: 'lte'
           | signal quality: '51' (cached)
  -------------------------
  Modes    |      supported: 'allowed: 2g, 3g, 4g; preferred: none'
           |        current: 'allowed: 2g, 3g, 4g; preferred: none'
  -------------------------
  Bands    |      supported: 'unknown'
           |        current: 'unknown'
  -------------------------
  IP       |      supported: 'ipv4, ipv6, ipv4v6'
  -------------------------
  3GPP     |           imei: '862234025609555'
           |  enabled locks: 'fixed-dialing'
           |    operator id: '26201'
           |  operator name: 'Telekom.de'
           |   subscription: 'unknown'
           |   registration: 'home'
  -------------------------
  SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'

  -------------------------
  Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'

thomas@linux-y7a7:~> mmcli -b 0
Bearer '/org/freedesktop/ModemManager1/Bearer/0'
  -------------------------
  Status             |   connected: 'yes'
                     |   suspended: 'no'
                     |   interface: 'wwan0'
                     |  IP timeout: '20'
  -------------------------
  Properties         |         apn: 'XXXXXXX.telekom'
                     |     roaming: 'allowed'
                     |     IP type: 'ipv6'
                     |        user: 'tm'
                     |    password: 'none'
                     |      number: '*99#'
                     | Rm protocol: 'unknown'
  -------------------------
  IPv4 configuration |   method: 'unknown'
  -------------------------
  IPv6 configuration |   method: 'static'
                     |  address: '2a01:598:89f0:f03b:70af:f98f:2e51:9035'
                     |   prefix: '64'
                     |  gateway: '2a01:598:89f0:f03b:e1d8:8315:d317:9049'
                     |      DNS: '2a01:598:7ff:0:10:74:210:221', '2a01:598:7ff:0:10:74:210:222'
                     |      MTU: '1500'
  -------------------------
  Stats              |          Duration: '360'
                     |    Bytes received: 'N/A'
                     | Bytes transmitted: 'N/A'

cornholio21 · Post by **cornholio21** » 27 Aug 2019, 16:18

Hello,
is there any ability to disable permanently the cdrom mode on this 4G modem?
I saw few AT+... commands for other devices on several forums but not for this one.

My problem is - I got a TP Router (VR900v) that does work with the 4G Modems, but not working with this one since it has no usb_modeswitch function.

Thank you!

thomasschaefer · Post by **thomasschaefer** » 18 Nov 2019, 10:55

The latest data set release is more than two years old.
Any chance to include this modem in the next release?

Post by **Josh** » 21 Nov 2019, 09:07

I'm on it just now. Going slowly due to many other obligations but will be released in November.

1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)

Re: 1&1 XSstick W1208 (4g systems)