|
Activation Codes and Methods, Hardware Details, Sniffing
-
DjJoakim
- Posts: 4
- Joined: 07 Nov 2021, 20:25
Post
by DjJoakim » 07 Nov 2021, 20:32
Hey!
First of all, i know there are a bunch of topics about the USB modems, i have read (not all) but alot of them, and i still can't get my modem to work as ethernet device.
My plan is to have the USB Modem to work as failover if my landline goes dead on PFsense.
So, when pfsense boots up my usb modem shows as cd1, as you can see here in the logs
Oct 24 21:04:17 kernel cd1: <HUAWEI Mass Storage 2.3M> Removable CD-ROM SCSI-2 device
Then, when i try to do
usb_modeswitch -v 12d1 -p 1f01 -c /usr/local/share/usb_modeswitch/12d1:1f01
The logs tell me this
Code: Select all Oct 24 21:10:21 kernel ugen3.3: <HUAWEIMOBILE HUAWEIMOBILE> at usbus3 (disconnected)
Oct 24 21:10:21 kernel umass0: detached
Oct 24 21:10:21 kernel (cd1:umass-sim0:0:0:0): Periph destroyed
Oct 24 21:10:21 kernel cd1: <HUAWEI Mass Storage 2.3M> s/n 0123456789ABCDEF detached
Oct 24 21:10:21 kernel cd1 at umass-sim0 bus 0 scbus6 target 0 lun 0
and then i have to reboot pfsense to see the device as cd1 again, after the usb_modeswitch action nothing happends..
Desperate for some help, i am pretty new to this!
This is how it looks like before i do usb_modeswitch
Code: Select all ugen3.3: <HUAWEIMOBILE HUAWEIMOBILE> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x0000 <Probed by interface class>
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0x12d1
idProduct = 0x1f01
bcdDevice = 0x0102
iManufacturer = 0x0001 <HUAWEI_MOBILE>
iProduct = 0x0002 <HUAWEI_MOBILE>
iSerialNumber = 0x0003 <0123456789ABCDEF>
bNumConfigurations = 0x0001
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x0020
bNumInterfaces = 0x0001
bConfigurationValue = 0x0001
iConfiguration = 0x0000 <no string>
bmAttributes = 0x0080
bMaxPower = 0x0001
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x0000
bAlternateSetting = 0x0000
bNumEndpoints = 0x0002
bInterfaceClass = 0x0008 <Mass storage>
bInterfaceSubClass = 0x0006
bInterfaceProtocol = 0x0050
iInterface = 0x0004 <Mass Storage>
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081 <IN>
bmAttributes = 0x0002 <BULK>
wMaxPacketSize = 0x0200
bInterval = 0x0000
bRefresh = 0x0000
bSynchAddress = 0x0000
Endpoint 1
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0001 <OUT>
bmAttributes = 0x0002 <BULK>
wMaxPacketSize = 0x0200
bInterval = 0x0001
bRefresh = 0x0000
bSynchAddress = 0x0000
Thanks!
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 08 Nov 2021, 04:02
usb_modeswitch is made to run under linux, it is not made to run under FreeBSD unix which pfSense runs on.
Some users has successfully used usb_modeswitch with pfSense but that may be modem or pfSense version dependent, there has recently been a couple of reports where pfSense seems to dislike the type of modem that switches into a eth device.
Search for pfSense in the forum search box (top right) and you will find those threads.
You have so far not convinced me that you have a usb_modeswitch switching problem, you have pasted what ugen shows about the modem before switching but not what it shows after switching.
After a successful switch the idProduct line should change, probably to 14db.
The few lines of log you pasted shows the modem starting to switch but not what happened thereafter..
-
DjJoakim
- Posts: 4
- Joined: 07 Nov 2021, 20:25
Post
by DjJoakim » 09 Nov 2021, 22:30
LOM wrote: ↑08 Nov 2021, 04:02
usb_modeswitch is made to run under linux, it is not made to run under FreeBSD unix which pfSense runs on.
Some users has successfully used usb_modeswitch with pfSense but that may be modem or pfSense version dependent, there has recently been a couple of reports where pfSense seems to dislike the type of modem that switches into a eth device.
Search for pfSense in the forum search box (top right) and you will find those threads.
You have so far not convinced me that you have a usb_modeswitch switching problem, you have pasted what ugen shows about the modem before switching but not what it shows after switching.
After a successful switch the idProduct line should change, probably to 14db.
The few lines of log you pasted shows the modem starting to switch but not what happened thereafter..
I see, well i posted it in Pfsense forum first, and one nice guy there tryed to help me get it right - but then he told me to get here for help, since he thougt it was becouse of usb modeswitch and not pfsense.
Well, since the device "dissapears" after i do the usb_modeswitch, i don't really know how to show what happends without that text from the log - device disconnected.. It dosen't show up anywhere..
Thanks
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 10 Nov 2021, 03:07
Include -W on your usb_modeswitch cmd line and post the output it creates.
-
DjJoakim
- Posts: 4
- Joined: 07 Nov 2021, 20:25
Post
by DjJoakim » 10 Nov 2021, 22:18
LOM wrote: ↑10 Nov 2021, 03:07
Include -W on your usb_modeswitch cmd line and post the output it creates.
Don't know if i did it right, but here is the outcome;
Code: Select all [2.5.2-RELEASE][root@Slave.home.arpa]/root: usb_modeswitch -v 12d1 -p 1f01 -c /usr/local/share/usb_modeswitch/12d1:1f01 -W
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.6.0 (C) Josua Dietze 2017
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x1f01
TargetVendor= 0x12d1
TargetProductList="14db,14dc"
HuaweiNewMode=1
Look for target devices ...
found USB ID 0000:0000
found USB ID 0000:0000
found USB ID 0000:0000
found USB ID 0000:0000
found USB ID 0627:0001
found USB ID 12d1:1f01
vendor ID matched
No devices in target mode or class found
Look for default devices ...
found USB ID 0000:0000
found USB ID 0000:0000
found USB ID 0000:0000
found USB ID 0000:0000
found USB ID 0627:0001
found USB ID 12d1:1f01
vendor ID matched
product ID matched
Found devices in default mode (1)
Access device 003 on bus 003
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
with class 8
Use endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI_MOBILE
Product: HUAWEI_MOBILE
Serial No.: 0123456789ABCDEF
-------------------------
Using standard Huawei switching message
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 ...
LIBUSB_FUNCTION: libusb_bulk_transfer enter
LIBUSB_FUNCTION: libusb_submit_transfer enter
LIBUSB_FUNCTION: libusb_submit_transfer leave 0
LIBUSB_FUNCTION: libusb_handle_events_timeout_completed enter
LIBUSB_FUNCTION: libusb10_handle_events_sub enter
LIBUSB_FUNCTION: libusb_handle_events_timeout_completed exit
LIBUSB_FUNCTION: libusb_handle_events_timeout_completed enter
LIBUSB_FUNCTION: libusb10_handle_events_sub enter
LIBUSB_TRANSFER: sync I/O done
LIBUSB_FUNCTION: libusb_handle_events_timeout_completed exit
LIBUSB_FUNCTION: libusb_bulk_transfer leave
OK, message successfully sent
Read the response to message 1 (CSW) ...
LIBUSB_FUNCTION: libusb_bulk_transfer enter
LIBUSB_FUNCTION: libusb_submit_transfer enter
LIBUSB_FUNCTION: libusb_submit_transfer leave 0
LIBUSB_FUNCTION: libusb_handle_events_timeout_completed enter
LIBUSB_FUNCTION: libusb10_handle_events_sub enter
LIBUSB_TRANSFER: sync I/O done
LIBUSB_FUNCTION: libusb_handle_events_timeout_completed exit
LIBUSB_FUNCTION: libusb_bulk_transfer leave
Response reading failed (error -99)
Device is gone, skip any further commands
-> Run lsusb to note any changes. Bye!
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 11 Nov 2021, 05:38
The verbose output from usb_modeswitch is as what is expected from a successful switch sequence, the old device is gone. usb_modeswitch has sent the switch message, the modem has received it and taken action.
I can only see two possible reasons why you don't get a new device afterwards, either the modem is faulty (check on another computer or check by booting a live linux distro from cd or flash drive) or there's a usb detection error in your FreeBSD kernel.
usb error like this has in the past sometimes been caused by an operating system not running directly on the hardware but running under a VM.
-
DjJoakim
- Posts: 4
- Joined: 07 Nov 2021, 20:25
Post
by DjJoakim » 11 Nov 2021, 19:20
LOM wrote: ↑11 Nov 2021, 05:38
The verbose output from usb_modeswitch is as what is expected from a successful switch sequence, the old device is gone. usb_modeswitch has sent the switch message, the modem has received it and taken action.
I can only see two possible reasons why you don't get a new device afterwards, either the modem is faulty (check on another computer or check by booting a live linux distro from cd or flash drive) or there's a usb detection error in your FreeBSD kernel.
usb error like this has in the past sometimes been caused by an operating system not running directly on the hardware but running under a VM.
Hmm well, that makes alot of sence now when you say it... And yes, the machine is running as a VM, so that may be the situation.. So, you don't think there is any solution to my problem here? Without changing from VM to hardware.
Thanks
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 12 Nov 2021, 04:12
DjJoakim wrote: ↑11 Nov 2021, 19:20
So, you don't think there is any solution to my problem here? Without changing from VM to hardware.
Thanks
I have no idea, I don't run things under VM's for the simple reason that they are just another layer that can only cause problems. It is difficult to 100% emulate hardware in software..
Another brand of VM?
Another, hopefully bugfixed, version of the same VM?
-
tommchris
- Posts: 3
- Joined: 04 Mar 2023, 11:01
Post
by tommchris » 31 Oct 2023, 08:48
Ensure that you have the correct drivers installed on your computer. Huawei E3372 may require specific drivers to work correctly. Download and install the official drivers for your device from Huawei's website.
Uno Online
-
jeffreestar
- Posts: 5
- Joined: 16 Nov 2023, 04:52
Post
by jeffreestar » 16 Nov 2023, 04:53
I understand that you are having trouble getting your USB modem to work as an Ethernet device on pfSense. I've reviewed the logs you provided and it seems like the issue might be related to the device being recognized as a CD-ROM drive instead of an Ethernet adapter.
backpack battles
-
namdosan1409
- Posts: 4
- Joined: 19 Dec 2023, 06:15
Post
by namdosan1409 » 19 Dec 2023, 06:17
The output you provided indicates that the USB modem is initially recognized as a Mass Storage device ("cd1") rather than a modem.
The usb_modeswitch command is typically used to switch USB modems from storage mode to modem mode. However, the command you provided seems to be missing some information. You may need to specify the target product ID for the modem mode.
Here's an example of how you might use usb_modeswitch:
bash
Copy code
usb_modeswitch -v 12d1 -p 1f01 -J
In this command:
-v specifies the vendor ID.
-p specifies the product ID.
-J indicates that the device should be treated as a modem. car games
-
celinedion
- Posts: 1
- Joined: 15 Apr 2023, 06:45
Post
by celinedion » 02 Jan 2024, 10:15
Some USB modems may require additional kernel drivers to switch to modem mode successfully. Check if there are any specific drivers needed for the Huawei E3372 modem on pfSense. You may need to load or install additional drivers.
mapquest
-
DirkAurich
- Posts: 12
- Joined: 02 Jan 2024, 07:24
Post
by DirkAurich » 23 Jan 2024, 12:34
DjJoakim wrote: ↑07 Nov 2021, 20:32
Hey!
First of all, i know there are a bunch of topics about the USB modems, i have read (not all) but alot of them, and i still can't get my modem to work as ethernet device.
My plan is to have the USB Modem to work as failover if my landline goes dead on PFsense.
So, when pfsense boots up my usb modem shows as cd1, as you can see here in the logs
Oct 24 21:04:17 kernel cd1: <HUAWEI Mass Storage 2.3M> Removable CD-ROM SCSI-2 device snaptik
Then, when i try to do
usb_modeswitch -v 12d1 -p 1f01 -c /usr/local/share/usb_modeswitch/12d1:1f01
The logs tell me this
Code: Select all Oct 24 21:10:21 kernel ugen3.3: <HUAWEIMOBILE HUAWEIMOBILE> at usbus3 (disconnected)
Oct 24 21:10:21 kernel umass0: detached
Oct 24 21:10:21 kernel (cd1:umass-sim0:0:0:0): Periph destroyed
Oct 24 21:10:21 kernel cd1: <HUAWEI Mass Storage 2.3M> s/n 0123456789ABCDEF detached
Oct 24 21:10:21 kernel cd1 at umass-sim0 bus 0 scbus6 target 0 lun 0
and then i have to reboot pfsense to see the device as cd1 again, after the usb_modeswitch action nothing happends..
Desperate for some help, i am pretty new to this!
This is how it looks like before i do usb_modeswitch
Code: Select all ugen3.3: <HUAWEIMOBILE HUAWEIMOBILE> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x0000 <Probed by interface class>
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0x12d1
idProduct = 0x1f01
bcdDevice = 0x0102
iManufacturer = 0x0001 <HUAWEI_MOBILE>
iProduct = 0x0002 <HUAWEI_MOBILE>
iSerialNumber = 0x0003 <0123456789ABCDEF>
bNumConfigurations = 0x0001
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x0020
bNumInterfaces = 0x0001
bConfigurationValue = 0x0001
iConfiguration = 0x0000 <no string>
bmAttributes = 0x0080
bMaxPower = 0x0001
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x0000
bAlternateSetting = 0x0000
bNumEndpoints = 0x0002
bInterfaceClass = 0x0008 <Mass storage>
bInterfaceSubClass = 0x0006
bInterfaceProtocol = 0x0050
iInterface = 0x0004 <Mass Storage>
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081 <IN>
bmAttributes = 0x0002 <BULK>
wMaxPacketSize = 0x0200
bInterval = 0x0000
bRefresh = 0x0000
bSynchAddress = 0x0000
Endpoint 1
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0001 <OUT>
bmAttributes = 0x0002 <BULK>
wMaxPacketSize = 0x0200
bInterval = 0x0001
bRefresh = 0x0000
bSynchAddress = 0x0000
Thanks!
Hello! I’m sorry to hear that you’re having trouble getting your USB modem to work as an ethernet device. Based on the information you provided, it seems like the modem is being recognized as a CD-ROM device instead of a modem. This is a common issue that can be resolved by running the usb_modeswitch command with the appropriate parameters.
-
lilycollins9
- Posts: 4
- Joined: 27 Jan 2024, 05:31
Post
by lilycollins9 » 06 Feb 2024, 10:18
Use caution when modifying system configurations such as usb_modeswitch. Consider creating a backup before continuing.
slope online
|
|