I'm configuring a server with linux Arch using Manjaro (I know, not ideal, but I have my valid reasons). The issue at hand is that I'm unable to change the resolution of the display from the configuration app (currently set at 480p). I tried using Xrandr to change the resolution but the last error I got was "xrandr: Configure crtc 0 failed". When I boot from a live USB with manjaro the resolution is set correctly (1280 x 720) and looks great, so I'm really lost about what the issue could be. clearly the video adapter is not the issue, could it be a issue with video drivers? if so, how do i check and change the propietary driver to an open source one. Info: Video Adapter: H1171x Series (iBCM) VGA controller CPU: 2X Xeon E5

I am trying to make a Huawei Brovi E3372-325 USB LTE model work with a Raspberry Pi. Out of the box, it shows as a CDROM when plugging it in. (This is apparently used to automatically run the driver installation on Windows.) So far, I found this post with a udev rules configuration file. That enables the modem when hotplugging it while the system is running by running usb_modeswitch. However, if the modem is plugged in on boot, it does not work, instead showing as a CD ROM. Therefore, I am now trying to write a system service to run usb_modeswitch on boot. As a step towards that, I booted with the modem plugged in and then tried executing the usb_modeswitch commands from the configuration file manually. However, that does not have the intended effect. The commands are /sbin/usb_modeswitch -v 3566 -p 2001 -W -R -w 400 /sbin/usb_modeswitch -v 3566 -p 2001 -W -R What do I need to do to make this work? Does the udev rules configuration trigger more actions that just the two listed commands? Or why do the seemingly same commands not have the same effect? **Update** Apparently, upon being powered on, the modem shows itself as a modem for a second, then switches to CDROM mode, but does not seem to accept commands switching it back to modem mode. The CDROM mode is intended for automatic driver installation in Windows. Though, that also means that when the driver is installed, the drive *can* be switched back to modem mode. So, it seems that usb_modeswitch and the Windows driver use different commands to switch to modem mode?

I have problem new USB LTE modem Brovi E3372-325 I can't get it to work on linux. When connected to a USB port, the modem identifies itself as:

# dmesg
...
[ 6731.401923] usb 1-3.4.4: new high-speed USB device number 22 using xhci_hcd
[ 6731.503252] usb 1-3.4.4: New USB device found, idVendor=3566, idProduct=2001, bcdDevice=ff.ff
[ 6731.503261] usb 1-3.4.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6731.503265] usb 1-3.4.4: Product: Mobile
[ 6731.503268] usb 1-3.4.4: Manufacturer: Mobile
[ 6731.503271] usb 1-3.4.4: SerialNumber: 123456789ABCD
[ 6731.505527] usb-storage 1-3.4.4:1.0: USB Mass Storage device detected
[ 6731.505830] scsi host1: usb-storage 1-3.4.4:1.0
[ 6732.534864] scsi 1:0:0:0: CD-ROM            Linux    File-Stor Gadget 0310 PQ: 0 ANSI: 2
[ 6732.535947] sr 1:0:0:0: Power-on or device reset occurred
[ 6732.536717] sr 1:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy
[ 6732.540429] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 6732.540983] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 6732.803382] ISO 9660 Extensions: RRIP_1991A

# lsusb -vvv
...
Bus 001 Device 028: ID 3566:2001 Mobile Mobile
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x3566 
  idProduct          0x2001 
  bcdDevice           ff.ff
  iManufacturer           2 Mobile
  iProduct                3 Mobile
  iSerial                 4 123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              1 Mass Storage
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000000
      (Missing must-be-set LPM bit!)
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x0004
      Device can operate at High Speed (480Mbps)
    bFunctionalitySupport   4
      Lowest fully-functional device speed is at an unknown speed!
    bU1DevExitLat           1 micro seconds
    bU2DevExitLat         500 micro seconds
Device Status:     0x0000
  (Bus Powered)

now I switch them to "modem": usb_modeswitch -v 3566 -p 2001 -X:

# dmesg
...
[ 6971.308148] usb 1-3.4.4: USB disconnect, device number 22
[ 6971.544052] usb 1-3.4.4: new high-speed USB device number 23 using xhci_hcd
[ 6971.645772] usb 1-3.4.4: New USB device found, idVendor=3566, idProduct=2001, bcdDevice=ff.ff
[ 6971.645787] usb 1-3.4.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 6971.645794] usb 1-3.4.4: Product: Mobile
[ 6971.645799] usb 1-3.4.4: Manufacturer: Mobile
[ 6971.645804] usb 1-3.4.4: SerialNumber: 123456789ABCD
[ 6971.647121] usb 1-3.4.4: Interface #0 referenced by multiple IADs
[ 6971.647643] usb 1-3.4.4: Interface #1 referenced by multiple IADs
[ 6971.678702] cdc_ncm 1-3.4.4:1.5: MAC-Address: c2:ab:11:ee:2f:15
[ 6971.679449] cdc_ncm 1-3.4.4:1.5 usb0: register 'cdc_ncm' at usb-0000:00:14.0-3.4.4, CDC NCM, c2:ab:11:ee:2f:15
[ 6971.743416] cdc_ncm 1-3.4.4:1.5 enxc2ab11ee2f15: renamed from usb0

# ip a s enxc2ab11ee2f15
14: enxc2ab11ee2f15:  mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether c2:ab:11:ee:2f:15 brd ff:ff:ff:ff:ff:ff

# mmcli -L
No modems were found

# lsusb -vvv
Bus 001 Device 029: ID 3566:2001 Mobile Mobile
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x3566 
  idProduct          0x2001 
  bcdDevice           ff.ff
  iManufacturer           2 Mobile
  iProduct                3 Mobile
  iSerial                 4 123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x00f9
    bNumInterfaces          7
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction              10 CDC Serial
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              8 CDC Abstract Control Model (ACM)
      ** UNRECOGNIZED:  05 24 00 10 01
      ** UNRECOGNIZED:  05 24 01 00 01
      ** UNRECOGNIZED:  04 24 02 02
      ** UNRECOGNIZED:  05 24 06 00 01
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              9 CDC ACM Data
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface             11 Marvell DIAG
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         3
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction              14 CDC Serial
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface             12 CDC Abstract Control Model (ACM)
      ** UNRECOGNIZED:  05 24 00 10 01
      ** UNRECOGNIZED:  05 24 01 00 04
      ** UNRECOGNIZED:  04 24 02 02
      ** UNRECOGNIZED:  05 24 06 03 04
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface             13 CDC ACM Data
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass      13 
      bFunctionProtocol       0 
      iFunction               0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass     13 
      bInterfaceProtocol      0 
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Union:
        bMasterInterface        5
        bSlaveInterface         6 
      CDC Ethernet:
        iMacAddress                     17 FE1EA1E4D9D7

        bmEthernetStatistics    0x00000000
        wMaxSegmentSize               1514
        wNumberMCFilters            0x0000
        bNumberPowerFilters              0
      CDC NCM:
        bcdNcmVersion        1.00
        bmNetworkCapabilities 0x01
          packet filter
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 
      bInterfaceProtocol      1 
      iInterface              0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 
      bInterfaceProtocol      1 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000000
      (Missing must-be-set LPM bit!)
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x0004
      Device can operate at High Speed (480Mbps)
    bFunctionalitySupport   4
      Lowest fully-functional device speed is at an unknown speed!
    bU1DevExitLat           1 micro seconds
    bU2DevExitLat         500 micro seconds
Device Status:     0x0000
  (Bus Powered)

But there is missing /dev interface (something like /dev/cdc*//dev/ttyUSB*). Tested on Ubuntu 22.04 with kernel 5.15 and Ubuntu 23.04 (daily build) with kernel 5.19. Without success. I tried dhclient enxc2ab11ee2f15, ip link enxc2ab11ee2f15 up - without success. For qmicli/mbimcli there is missing /dev/cdc* interface. On Windows 10 PC it connects automatically and gets IP from DHCP. It uses RNDIS driver. Can you please help me? How can I switch modem to the right mode?

I've been trying to install Fedora 34 Workstation on my Huawei Matebook D14 laptop. So, the problem is that wifi can show me other networks, but fails to connect each one of them. Network card is Realtek RTL8822CE Wireless Adapter.

I want a Huawei E3327 to work as a fallback on a Raspberry Pi 4B. The modem shows constant cyan light, which means that there es a 4G connection established (I previously configured APN using a windows machine). I successfully used usb_modeswitch to switch the modem in the right state, and a a new network interface eth1 shows up. I configured a static IP, my /etc/network/interfaces looks like: # Drop-in configs source interfaces.d/* # Ethernet allow-hotplug eth0 iface eth0 inet dhcp address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 #dns-nameservers 192.168.0.1 # WiFi allow-hotplug wlan0 iface wlan0 inet dhcp address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 #dns-nameservers 192.168.0.1 wireless-power off wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf # hotspot iface wlan1 inet static address 192.168.42.1 netmask 255.255.255.0 gateway 192.168.42.1 dns-nameservers 192.168.42.1 #HUAWEI E3372 allow-hotplug eth1 iface eth1 inet static address 192.168.8.100 netmask 255.255.255.0 network 192.168.8.0 broadcast 192.168.8.255 There is also the internal WiFi connection of the RasPi and an external USB WiFi dongle configured as a hotspot, which works. The problem: I can only ping 8.8.8.8 when there is a wifi connection. The huawei modem does not seem to work. Without the wifi connection I get Network is unreachable when I try ping 8.8.8.8 with established wifi connection, ip address shows: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d8:3a:dd:01:c0:55 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether d8:3a:dd:01:c0:56 brd ff:ff:ff:ff:ff:ff inet 192.168.0.136/24 brd 192.168.0.255 scope global dynamic wlan0 valid_lft 603872sec preferred_lft 603872sec 4: wlan1: mtu 2312 qdisc mq state UP group default qlen 1000 link/ether 34:60:f9:64:4f:98 brd ff:ff:ff:ff:ff:ff 5: eth1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff inet 192.168.8.100/24 brd 192.168.8.255 scope global eth1 valid_lft forever preferred_lft forever How can I make the modem work and act as a fallback when there is no WiFi connection?

Just this week I got the newest Matebook 14 2020 AMD with the 4800H. On windows I'm using an UtechSmart USB-C hub to output 4K@60Hz to my monitor so physically I know it's possible. Linux, however, is another story. I installed Kubuntu 20.04 LTS, but I could only boot to it (kernel 5.4 I believe) by going into recovery mode, and then selecting continue boot. Otherwise it would just hang on the Huawei logo. I installed the 5.8.15 kernel and everything seems to work fine, except I can't seem to set the display output to 60Hz, even though it's available in the settings, confirmed also by xrandr: > Screen 0: minimum 320 x 200, current 3840 x 3600, maximum 16384 x 16384 eDP connected primary 2160x1440+783+2160 (normal left inverted right x axis y axis) 296mm x 197mm 2160x1440 60.00*+ 1920x1200 60.00 1920x1080 60.00 1600x1200 60.00 1680x1050 60.00 1280x1024 60.00 1440x900 60.00 1280x800 60.00 1280x720 60.00 1024x768 60.00 800x600 60.00 640x480 60.00 HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) DisplayPort-2 disconnected (normal left inverted right x axis y axis) DisplayPort-3 disconnected (normal left inverted right x axis y axis) DisplayPort-4 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00 + 30.00* 2560x1440 59.95 1920x1080 60.00 59.94 1600x900 60.00 1280x1024 60.02 1280x800 59.81 1280x720 60.00 59.94 1024x768 60.00 800x600 60.32 720x480 60.00 59.94 640x480 60.00 59.94 However, running xrandr --output DisplayPort-4 --mode 3840x2160 --rate 60, I get xrandr: Configure crtc 1 failed I assumed this has something to do with the amdgpu drivers, so I went ahead and downloaded the latest 20.30 version, however, I get the following error: Loading new amdgpu-5.6.5.24-1109583 DKMS files... Building for 5.8.15-050815-generic Building for architecture x86_64 Building initial module for 5.8.15-050815-generic ERROR (dkms apport): kernel package linux-headers-5.8.15-050815-generic is not supported Error! Bad return status for module build on kernel: 5.8.15-050815-generic (x86_64) Consult /var/lib/dkms/amdgpu/5.6.5.24-1109583/build/make.log for more information. I even tried installing it on the 5.8.1 kernel with no luck. This is where I'm stuck right now, and I'm pretty sure I wrecked the whole installation. Any insight on how to fix my problems? **UPDATE**: As of kernel version 5.15, this has been fixed!

I run Fedora 24 as LiveCD (XFCE spin) and my 4G usb-modem works great. Then I installed Fedora on my hard disk and the modem does not work. On LiveCD NetworkManager automatically recognized the modem as mobile broadband, but if I run my system from hard disk, NetworkManager does not recognize my modem. By the way, I see my modem after lsusb command in the list. I do not understand why this happens, because the OS is the same. The modem type: Huawei E3372h

I have a modem usb stick **Huawei E3372H-320** and I'm trying to get it work with **AT Commands**. The problem is that I cannot see any ttyUSB inside /dev. The modem is recognized lsusb gives me: Bus 001 Device 006: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131 I'm using Ubuntu 20.04 (5.11.0-41-generic) Any suggestions?

A usb-modem connected to my Raspberry PI with Raspian lite. I've finally found a way to make it connect by issuing these two steps:

sudo socat - /dev/ttyUSB1

and from within Socat I just write:

AT^NDISDUP=1,1,"4g.tele2.se"

...to make my usb-modem connect. How can I now send this command using a shell script?

I have SSH public key (generated on my Mac) in OpenSSH format like this: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDXaDj1YGcvKIhUIgmjV/Mjz8so5O2tdxG9gVlTwCxuFLjcUOsciB5R+hZ28GZtb9tb0p4ZSGd8bLcUnI/tqFlVBfRKhfixbvJlDJkzh1eqzqjgCz7Sgd7vo/9pX4FNmajcdt4nsgMI0Q0NLZOWF0M90gTAkcpfCVyt561IIrHK0MpWPqQbp917X8hfRH23sgo8B471FhN6j3ghS18OcAG8LSzCQ5IjJzyqzRRYLpYVdGVyrqNKV0wBOP7dzmZAcpit4XCtRIESKdQGzPCMcctgh2doBPwFyP1AUcTCrq5skZgik6RjaJAlCm3rxPs0bJDGInWEg0lTnTc7hEmV4tf3 nameofthekey **And I need to convert to PKCS#1 in HEX with this formatting:** 30818602 8180E6B0 25E45C19 54F3DBAD D41C79BF 2054F2C9 33775177 6F60F3B0 9654B03D 02A6A30F B04A5D59 E9BA7846 32059FB6 1157F39B 2C60C890 9B92EFA6 CD566AE2 41621AEB 7BC30538 7065BD5A E3D2380E F1ABF4BF A8EFB0C9 E9BB06E0 8A060E0E 2022047C 009BA3F6 47257E1B B3498941 3C1281BA C5D64786 377B7426 2B5AA315 41C70201 25 and put in in my Huawei OLT terminal for SSH RSA key access. Thank you.

*Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials.* The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here , the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. WAP(Dopra Linux) # Now this is where it gets interesting, BusyBox is installed, but the help command doesn't actually work. WAP(Dopra Linux) # help ERROR::Command is not existed Hitting "?" again gives me another list of available commands which I've pasted here . They are pretty limited but I have access to ls and I can see that /bin actually has a lot of classic linux stuff in it , but I can't seem to run any of it, even busybox. It just throws the cheeky "Command is not existed" error message. **My question is: How can I access these commands (preferably cat and echo)?**

I've got a Huawei E173 USB dongle connected to a Raspberry PI. I'm trying to use the device to make and receive calls. For my purpose, it is needed (i) to save audio of the call to file and (ii) to send audio to the telephony call from an input file. As far as I understood (I can't find any official guide), the E173 dongle sets up three new devices (please correct me if I'm wrong): * /dev/ttyUSB0 for commands * /dev/ttyUSB1 for voice data * /dev/ttyUSB2 for notifications In order to enable phone calls, I run the following commands: AT+CLIP=1, AT+CRC=1, AT+CNMI=1,2 on /dev/ttyUSB0. Also, if I run AT^CVOICE? I get ^CVOICE:0,8000,16,20. Finally, when I make/receive calls, I run AT^DDSETEX=2 on /dev/ttyUSB0 to enable audio forward to the /dev/ttyUSB1 port. At this point, I'm stuck. I know there are other similar posts trying to redirect microphone input and speakers output to the dongle, but my aim is to save the conversation to file (during a call, I tried to run cat /dev/ttyUSB1 > filename.raw, but the file can't be opened with standard software, hence, how can I convert it?) and, simultaneously, to send voice from file (which format? I tried to send back the filename.raw to /dev/ttyUSB1 with cat filename.raw > /dev/ttyUSB1, but the entire system gets freezed). How can I save audio to file and send back audio from file? I found some resources on the Internet trying to explain, for similar devices, that audio has to be sent in mono, in digital frequency of 8000 Hz, and digitalized to 16 bit. By looking at the result of the AT^CVOICE? command, such parameters should be applied also in my case. Also, the same resource tells that "audio data should be fed to the modem audio port in batches of 320 bytes every 0.02 seconds". I've tried to apply even such approach, with no luck.

I have a 4G module that requires me to run echo '03f0 581d' > /sys/bus/usb-serial/drivers/generic/new_id after every startup/resume to make the modem visible. How should I make this automatic? - Add the VID&PID to usb-serial sources and recompile - Create script that run on startup/resume that adds them dynamically - Some sort of udev rule? What would be the best approach. I think the udev approach sounds the most reasonable. I assume that would work over suspend/resume too? The modem is a HP lt4112 LTE/HSPA+ Gobi 4G Modem (Huawei ME906E). Bonus question: Why does the command need to be re-run after a suspend/resume cycle. Does the kernel module get unloaded or somehow reset when the laptop gets suspended to RAM?

I have a Lenovo thinkpad x260 with a Huawei Embedded Modem(Model ME906s-158). I've been using it with debian 9 sucessfully. Had need to move to Debian 10. Since the move, it stopped working. Tried a fresh install of Debian 9 but i can't still use the modem. I keep seeing `"Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted"` when i check the logs of ModemManager. I am also so certain that there is a sim in the sim tray and it works on my mobile phone. `mmcli -L` Found 1 modems: /org/freedesktop/ModemManager1/Modem/0 [Huawei Technologies Co., Ltd.] HUAWEI Mobile `mmcli -m 0` /org/freedesktop/ModemManager1/Modem/0 (device id 'ccd68b9767f3e72175547f52f29f8f5ef765317b') Hardware | manufacturer: 'Huawei Technologies Co., Ltd.' | model: 'HUAWEI Mobile' | revision: '11.617.04.00.00' | H/W revision: 'ML1ME906SM' | supported: 'gsm-umts, lte' | current: 'gsm-umts, lte' | equipment id: 'XXX' System | device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3' | drivers: 'cdc_mbim, option1' | plugin: 'Huawei' | primary port: 'cdc-wdm0' | ports: 'ttyUSB0 (at), cdc-wdm0 (mbim), wwp0s20f0u3c3 (net)' Numbers | own : 'unknown' Status | lock: 'unknown' | unlock retries: 'unknown' | state: 'failed' | failed reason: 'sim-missing' | power state: 'on' | access tech: 'unknown' | signal quality: '0' (cached) Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none' | current: 'allowed: any; preferred: none' Bands | supported: 'unknown' | current: 'unknown' IP | supported: 'ipv4, ipv6, ipv4v6' SIM | path: 'none' Bearers | paths: 'none'

I have a Huawei E160E and a Huawei K3765 "GSM"-modem. The question is: How to send and receive audio data placing or receiving phone/ voice calls with those modems? Both seem to support voice calls, according to specifications (E160E , K3765 ) and according to AT-commands: Issuing AT^CVOICE? results in ^CVOICE:0,8000,16,20 OK (both modems the same). Both modems provide 3 USB ports, I will call them /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2 (assuming there is no other USB serial device present in the system). The K3765 additionally registers an cdc_etherethernet device. I am using Linux. On both /dev/ttyUSB0 and /dev/ttyUSB2 I can place AT-commands and receive their answers; additionally, /dev/ttyUSB2 reports status messages (like ^RSSI:23, ^BOOT:38021325,0,0,0,77, ^SIMST:1 or ^SRVST:2). The K3765 also reports by default when there is someone calling (RING), the E160E does not. On both modems, I can place calls with ATD; and I can pick up calls with ATA. /dev/ttyUSB1 seems to do nothing; simply writing to this file will get no data into it, reading from it gets no data out. How is it possible to get audio data in and out of the modem(s)? I already found this stackexchange question and the answer by Sai Chaitanya as well as the comment to use ffmpeg/ffplay. ffplay just stalls for me, and with the code snipped I can not make too much to try it out (not a programmer, and expecially not in C, though; and don't know if this applies to my modem(s) at all). In the internet I do not find information on how to actually get audio in and out of those devices, other than using big software packages (asterisk, for example) -- which I do not want, the question is on how to get it to work the basic way. So, how does audio communication work with (those) Huawei GSM modems? Modem information: Output of ATI-command: E160E: Manufacturer: huawei Model: E160X Revision: 11.609.10.02.432 IMEI: 354765038021325 +GCAP: +CGSM,+DS,+ES OK K3765: Manufacturer: huawei Model: K3765 Revision: 11.126.03.06.00 IMEI: 353142047899771 +GCAP: +CGSM,+DS,+ES OK

I have a Linux-based OS (Rasbian) running on Raspberry Pi 2+ and it is using **Huawei E3372s** 4G/LTE USB Stick for internet connection. All my outbound connections work perfectly (Huawei USB mode changed using usb_modeswitch-ruling and Udev/rules.d) but I am unable to receive any kind of inbound connection to the Raspi. **Incoming is just not working**. I **cannot receive** any packets or connections, which I have tracked realtime and from logs using tools provided by Raspbian package distributions. I have already confirmed with my 4G ISP that the extended service which allows two-way traffic is enabled, reseted and so much of their knowledge, to my 3G/4G subscription, working perfectly from their end but I am unable to receive any packets with the Raspi. **Huawei E3372s** (unlike most of the older sticks which use dialing like wvdial) uses **CDC_ETH** driver system which creates an ethernet-like device to the system (ETH1 in this case) and should work in this case flawlessly. I have cleared, re-created, tested, modified, re-cleared and again done all needed tasks with IPTables, checked, modified and tested Route several times as well as confirmed that there are no known blocking systems preventing connection through Huawei USB-stick, yet I still cannot receive even Ping to my system, although there are fully functional services running. I have also checked more simple and straightforward areas such as hosts allow/deny rules and have had no luck with them. It is not APN name either as all settings with the Huawei's internal configuration have been set correctly using it's web interface. I have, however, encountered on few occasion from random forums, that Huawei CDC_ETH solution may have flaws handling incoming connections with its driver. If any of you have experience with Debian/Rasbian/Linux incoming connection problems with **Huawei E3372s** or relative 3G/4G USB product which use **CDC_ETH** and have found solution to this problem

If I connect two usb wireless adaptors (via a usb hub), only one of them gets assigned an ip address. I want each to be assigned a different ip address to be able to use both wireless adapters at the same time, each from a separate network namespace. The two devices have the same mac address and I think this is the reason. When the two usb adapters are different models (which have different mac addresses), they both get different ip addesses assigned automatically. output of 'ip a': 48: eth1: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 0c:5b:8f:27:9a:64 brd ff:ff:ff:ff:ff:ff inet 192.168.8.100/24 brd 192.168.8.255 scope global dynamic noprefixroute eth1 valid_lft 86384sec preferred_lft 86384sec inet6 fe80::640:311a:de17:1163/64 scope link noprefixroute valid_lft forever preferred_lft forever 49: eth2: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 0c:5b:8f:27:9a:64 brd ff:ff:ff:ff:ff:ff UPDATE: I changed the MacAddressPolicy as suggested which successfully gives a random mac address to each of these devices, meaning that now when two of these devices are connected, they have different mac addresses. However, the ip address still only gets assigned to one of them: 59: eth1: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether fe:ef:a8:28:41:df brd ff:ff:ff:ff:ff:ff inet 192.168.8.100/24 brd 192.168.8.255 scope global dynamic noprefixroute eth1 valid_lft 86393sec preferred_lft 86393sec inet6 fe80::640:311a:de17:1163/64 scope link noprefixroute valid_lft forever preferred_lft forever 60: eth2: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ca:9e:d4:c1:61:b9 brd ff:ff:ff:ff:ff:ff Is there a way to get an ip address assigned to both? (I can't give it a static ip because the internet doesnt work if I do that.) Is this happening because both devices are telling the OS that it's ip is 192.168.8.100 and they can't both use the same ip? Or could it have anything to do with the fact that the mac address was assigned on the OS but the devices still have the same mac address on their chips?

I'm trying to get a expresscard / PCMCIA card modem to work in manjaro linux, but modemmanager is not detecting it at all, let alone let me configure a connection with it. The status light is blinking blue every 2 sec. or so. I know (because it worked on the same laptop under ubuntu) that it shows permanent green, if it's ready for use. Any pointers where to start, what to check, etc.? I also used modemmanager, but that doesn't detect anything either.

I have two interfaces with me as eth0 and wwan0. My both the interfaces have internet connectivity. But in my use case, I can plug and unplug any interface from my system. Ideally as soon I plug it again, if I add the gateway to route, my internet connection will resume. The problem here is that I always get information about default gateway only. Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 8.8.8.8 192.168.2.1 255.255.255.255 UGH 0 0 0 eth0 10.177.88.96 * 255.255.255.240 U 0 0 0 wwan0 59.144.127.17 192.168.2.1 255.255.255.255 UGH 0 0 0 eth0 192.168.0.0 * 255.255.252.0 U 0 0 0 eth0 192.168.2.1 * 255.255.255.255 UH 0 0 0 eth0 Here, I have the gateway for eth0 but gateway information for wwan0 is 0.0.0.0. **Setup:** I am having two interfaces as eth0 and wwan0. Both are having internet connectivity. **Problem:** Out of these two interfaces, I can ping only via one interface. I can ping only through the interface which is by default. Now to ping through another interface, I try to add the gateway to route and it works fine with this command route add default gw " + GW + wwan0/eth0 --> Depeneds on which one is not pinging In my route table for the interface which is not pinging, gateway information is 0.0.0.0. I am getting gateway information to add manually from dhcp.lease file but I need gateway information on fly so that via some script, I can achieve the same. Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 8.8.8.8 192.168.2.1 255.255.255.255 UGH 0 0 0 eth0 10.177.88.96 * 255.255.255.240 U 0 0 0 wwan0 59.144.127.17 192.168.2.1 255.255.255.255 UGH 0 0 0 eth0 192.168.0.0 * 255.255.252.0 U 0 0 0 eth0 192.168.2.1 * 255.255.255.255 UH 0 0 0 eth0 192.168.42.0 * 255.255.255.0 U 0 0 0 wlan0 **ip route** default via 192.168.2.1 dev eth0 8.8.8.8 via 192.168.2.1 dev eth0 10.177.88.96/28 dev wwan0 proto kernel scope link src 10.177.88.104 59.144.127.17 via 192.168.2.1 dev eth0 192.168.0.0/22 dev eth0 proto kernel scope link src 192.168.2.166 192.168.2.1 dev eth0 scope link 192.168.42.0/24 dev wlan0 proto kernel scope link src 192.168.42.1 **Ifconfig -a** eth0 Link encap:Ethernet HWaddr 70:B3:D5:9A:EF:FC inet addr:192.168.2.166 Bcast:192.168.3.255 Mask:255.255.252.0 inet6 addr: fe80::72b3:d5ff:fe9a:effc%1995519696/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15380 errors:0 dropped:0 overruns:0 frame:0 TX packets:269 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1866379 (1.7 MiB) TX bytes:27888 (27.2 KiB) wwan0 Link encap:Ethernet HWaddr 00:1E:10:1F:00:00 inet addr:10.177.88.104 Bcast:10.177.88.111 Mask:255.255.255.240 inet6 addr: fe80::21e:10ff:fe1f:0%1995519696/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38 errors:0 dropped:0 overruns:0 frame:0 TX packets:156 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6682 (6.5 KiB) TX bytes:16247 (15.8 KiB)

I'm trying to get a Huawei E398 3G USB modem to work on my Raspberry Pi 3 When I run wvdial I get the following response: pi@mypi:~ $ sudo wvdial --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ERROR --> Bad init string. This is my wvdial.conf: pi@mypi:~ $ cat /etc/wvdial.conf [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Modem Type = USB Modem ISDN = 0 New PPPD = yes Stupid Mode = yes Modem = /dev/ttyUSB0 Phone = *99# Username = internet Password = internet Baud = 115200 Anyone have any clue on what could cause this? I've tried every other init string I could come across, but every single one gives me the same error.