search

asset-group / 5ghoul-5g-nr-attacks

5G NR Attacks against Qualcomm and Mediatek smartphones. Fuzzer included⚡
https://5ghoul.com
GNU General Public License v2.0
504 stars 85 forks source link

Modem not initialized #10

Open shuimoshusheng opened 9 months ago

shuimoshusheng commented 9 months ago

docker images：megarbelini/5ghoul:release-5g-x86_64 USRP: B210 UHD Version: UHD 4.4.0.HEAD-0-8e54b58d

command: sudo ./bin/5g_fuzzer --exploit=mac_sch_rrc_setup_crash_var --MCC=466 --MNC=92

[Open5GS] Subscribers registered to core network: 15
./3rd-party/hostapd/idemptables -A INPUT -i ogstun -j ACCEPT
./3rd-party/hostapd/idemptables -A FORWARD ! -i ogstun -o ogstun -j ACCEPT
./3rd-party/hostapd/idemptables -A FORWARD -i ogstun ! -o ogstun -j ACCEPT
./3rd-party/hostapd/idemptables -t nat -A POSTROUTING -s 45.45.0.0/16 ! -o ogstun -j MASQUERADE
[GlobalTimeout] Not enabled in config. file
[AnomalyReport] Added Logging Sink: PacketLogger
[AnomalyReport] Added Logging Sink: SvcReportSender
[USBHubControl] Disabled in config. file
[ReportSender] Credentials file not found: modules/reportsender/credentials.json
[ReportSender] Ready
[Optimizer] Optimization disabled. Using default population:
--------------------------------------------------------
[Optimizer] Iter=1  Params=[0.2,0.2,0.2,0.2,0.2,0.2,...,0.2]
[Optimizer] Fitness=1e+06  Adj. Fitness=-1e+06
--------------------------------------------------------
[Optimizer] Initialized with X Size=293, Population Size=5
[Main] Fuzzing not enabled! Running only target reconnection
[PacketHandler] Added "proto:nas-5gs", Dir:0, Realtime:0, TID:3034
[PacketHandler] Added "proto:nas-5gs", Dir:1, Realtime:0, TID:3035
[PacketHandler] Added "proto:pdcp-nr-framed", Dir:0, Realtime:1, TID:3036
[PacketHandler] Added "proto:pdcp-nr-framed", Dir:1, Realtime:1, TID:3037
[PacketHandler] Added "proto:mac-nr-framed", Dir:0, Realtime:1, TID:3048
[PacketHandler] Added "proto:mac-nr-framed", Dir:0, Realtime:1, TID:3050
[PacketHandler] Added "proto:mac-nr-framed", Dir:1, Realtime:0, TID:3056
[Main] eNB/gNB started!
[!] Waiting UE task to start...
[ModemManager] StartModemConnection: Modem not initialized
[ModemManager] Reconnection Timeout (4000 ms)
[ModemManager] StartModemConnection: Modem not initialized
[ModemManager] Reconnection Timeout (4000 ms)
[ModemManager] StartModemConnection: Modem not initialized
[ModemManager] Reconnection Timeout (4000 ms)
[ModemManager] StartModemConnection: Modem not initialized
[ModemManager] Reconnection Timeout (4000 ms)
[ModemManager] StartModemConnection: Modem not initialized
[ModemManager] Reconnection Timeout (4000 ms)
alphafox02 commented 9 months ago

It's set to be looking for a modem, needs either disabled or add I think --GlobalTimeout=false to the command line. I'd have to go back and look at past tickets, but I think it's the global_config.json down under Monitor where you can set enable to false?

lpj12121 commented 9 months ago

你好，我想借问一下，装这个5ghoul项目之前，需要先安装哪些软件环境呢，是open5gs和gnb吗

shuimoshusheng commented 9 months ago

@alphafox02 Okay, thank you. I'll give it a try.

Also, regarding the issue #9 , I saw the signaling for the NR RRC connection in the log. However, opening a saved PCAP package using Wireshark does not display NR RRC signaling as shown in the Readme 2.2 screenshot. Is there a Lua plugin that can display NR RRC signaling on the pcap message when the saved package is decoded by default using UDP?

shuimoshusheng commented 9 months ago

你好，我想借问一下，装这个5ghoul项目之前，需要先安装哪些软件环境呢，是open5gs和gnb吗

Using docker or building from source code，Please check README.

alphafox02 commented 9 months ago

I'm running into this problem and do need the modem to initilize because I'm actually using a modem. In this ticket here #3 it is mentioned that qmcli and mmcli will configure the modem. However, it appears neither libqmi-utils nor modemmanager is installed within the docker. I assume they are needed, but even after adding I'm getting a failure to initialize the modem.

alphafox02 commented 9 months ago

I blew away the docker and pulled it in fresh as I noticed it was stated that ModemManger was installed, plus I see it in the requirements.sh script. I'll look to see if I can figure out why my modem is not being picked up.

alphafox02 commented 9 months ago

While trying to further understand the design of the docker, I went into the 3rd-party/ModemManager/build/cli to find the mmcli. However, trying to run the command mmcli -L directly to find modems, I get the following error: couldn't find the ModemManager process in the bus Which may be expected, but I'm not certain. Is there possibly a problem with modemmanager?

alphafox02 commented 9 months ago

In global_config.json I've made sure that /dev/cdc-wdm1 is changed to wdm0. Under USBHunControl (was set to false, so maybe not needed) I changed it to true and set the VIPPID of the Quectel RM520N-GL in place of the original Quectel info that was there. Still there's the modem not initialized, so I think I'm running out of the options as to what I can change to utilize this new modem. Perhaps I will have to configure it manually and attempt further steps that way.

shuimoshusheng commented 9 months ago

In global_config.json I've made sure that /dev/cdc-wdm1 is changed to wdm0. Under USBHunControl (was set to false, so maybe not needed) I changed it to true and set the VIPPID of the Quectel RM520N-GL in place of the original Quectel info that was there. Still there's the modem not initialized, so I think I'm running out of the options as to what I can change to utilize this new modem. Perhaps I will have to configure it manually and attempt further steps that way.

Quectel RM520N-GL using usb serial port mode？

Matheus-Garbelini commented 9 months ago

@alphafox02 Hi all, sorry for the delay. I was unavailable during the holidays. Regarding the modem intialization, it seems there is some issue with docker not fully supporting systemd in older versions. Systemd is an initialization system and daemon fully required by ModemManager to work. You can try directly callinf the ModemManager binary in sbin folder: ./3rd-party/ModemManager/runtime/sbin/ModemManager

Go to the sbin folder first before calling modem manager. After this, you will receive many logs in the terminal, eventually you will see modem initialized if it works. mmcli can then work correctly.

If it does not work, I'd suggest running the container in podman, as it fully supports systemd. Originally this project was using podman, but we changed to docker to make installation easier. Nevertheless, I believe podman static can be used to get latest version of podman: https://github.com/mgoltzsche/podman-static Then, container.sh needs to be modified to use the podman binary instead of docker

I'm still traveling, but once I have access to my laptop this weekend, I will update the container.sh script to use podman instead of docker.

Alternatively you can try installing ModemManager on your host using ./requirements.sh 3gpp this will automatically install open5gs and eventually ModemManager in the system.

Matheus-Garbelini commented 9 months ago

@shuimoshusheng you need to use the builtin Wireshark from 5ghoul to open the logs correctly: './bin/wireshark logs/5gnr_gnb/capture_nr5g_gnb.pcapng'

Otherwise, you need to configure your own Wireshark to manually enable UDP heuristics and mac_nr_udp decoder to allow Wireshark to parse the 5G packets encapsulated within the UDP payload.

Documentation on how to manually configure Wireshark to decode 5g packets over UDP is available here: https://gitlab.eurecom.fr/oai/openairinterface5g/-/blob/develop/openair2/UTIL/OPT/README.txt?ref_type=heads

alphafox02 commented 9 months ago

In global_config.json I've made sure that /dev/cdc-wdm1 is changed to wdm0. Under USBHunControl (was set to false, so maybe not needed) I changed it to true and set the VIPPID of the Quectel RM520N-GL in place of the original Quectel info that was there. Still there's the modem not initialized, so I think I'm running out of the options as to what I can change to utilize this new modem. Perhaps I will have to configure it manually and attempt further steps that way.

Quectel RM520N-GL using usb serial port mode？

I'm actually learning a lot in the process here, I don't believe it's in usb serial port mode so good point. I'm going now to try what @Matheus-Garbelini mentioned.

Matheus-Garbelini commented 9 months ago

In global_config.json I've made sure that /dev/cdc-wdm1 is changed to wdm0. Under USBHunControl (was set to false, so maybe not needed) I changed it to true and set the VIPPID of the Quectel RM520N-GL in place of the original Quectel info that was there. Still there's the modem not initialized, so I think I'm running out of the options as to what I can change to utilize this new modem. Perhaps I will have to configure it manually and attempt further steps that way.

Quectel RM520N-GL using usb serial port mode？

I'm actually learning a lot in the process here, I don't believe it's in usb serial port mode so good point. I'm going now to try what @Matheus-Garbelini mentioned.

@alphafox02 Indeed Qualcomm modems normally connect first via QMI interface, which is Qualcomm proprietary (sort of). Although you can communicate with the modem via serial port using AT commands, this is done as a fallback if ModemManager cannot find or use any QMI interface.

Alternatively, if you disable UEModemManager and just start 5Ghoul without global timeout, you can try communicating with the modem yourself by using a serial monitor programa such as putty, cutecom, etc.

Normally, when you open serial port /dev/ttyUSB1 (or another), you can verify that the modem is communicating via serial if it replies AT or OK if you send command "AT". Then you can use other commands such as at+cops=? to search for mobile networks.

alphafox02 commented 9 months ago

I may need to try Podman. This is what occurs when trying to directly start ModemManager.

./ModemManager 
<info>  ModemManager (version 1.20.7) starting in system bus...
Plugin Dir: /home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager/
<warn>  could not acquire the 'org.freedesktop.ModemManager1' service name
<info>  ModemManager is shut down

This is in debug mode if it helps

./ModemManager --debug
<info>  [1704363856.870258] ModemManager (version 1.20.7) starting in system bus...
<debug> [1704363856.870270] [charsets] detecting platform iconv() support...
<debug> [1704363856.870373] [charsets]   UTF-8: iconv conversion to/from charset is supported
<debug> [1704363856.870385] [charsets]   UCS-2BE: iconv conversion to/from charset is supported
<debug> [1704363856.870410] [charsets]   ASCII: iconv conversion to/from charset is supported
<debug> [1704363856.870516] [charsets]   ISO8859-1: iconv conversion to/from charset is supported
<debug> [1704363856.870589] [charsets]   CP437: iconv conversion to/from charset is supported
<debug> [1704363856.870713] [charsets]   CP850: iconv conversion to/from charset is supported
<debug> [1704363856.870832] [charsets]   UTF-16BE: iconv conversion to/from charset is supported
<debug> [1704363856.871289] Full suspend/resume hooks enabled
<debug> [1704363856.871402] [sleep-monitor-systemd] singleton created
<debug> [1704363856.872318] bus acquired, creating manager...
Plugin Dir: /home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager/
<debug> [1704363856.874511] [auth-provider] singleton created
<debug> [1704363856.874644] [filter] created
<debug> [1704363856.874649] [filter]   explicit allowlist:         yes
<debug> [1704363856.874654] [filter]   explicit blocklist:         yes
<debug> [1704363856.874657] [filter]   plugin allowlist:           yes
<debug> [1704363856.874661] [filter]   qrtr devices allowed:       yes
<debug> [1704363856.874678] [filter]   virtual devices forbidden:  yes
<debug> [1704363856.874680] [filter]   net devices allowed:        yes
<debug> [1704363856.874682] [filter]   usbmisc devices allowed:    yes
<debug> [1704363856.874686] [filter]   rpmsg devices allowed:      yes
<debug> [1704363856.874703] [filter]   wwan devices allowed:       yes
<debug> [1704363856.874706] [filter]   tty devices:
<debug> [1704363856.874708] [filter]       platform driver check:    yes
<debug> [1704363856.874724] [filter]       driver check:             yes
<debug> [1704363856.874727] [filter]       cdc-acm interface check:  yes
<debug> [1704363856.874731] [filter]       with net check:           yes
<debug> [1704363856.874749] [filter]       default:                  forbidden
<debug> [1704363856.874787] [plugin-manager] looking for plugins in '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager/'
<debug> [1704363856.875231] [plugin-manager] loaded shared 'Novatel' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-novatel.so'
<debug> [1704363856.875442] [plugin-manager] loaded shared 'Foxconn' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-foxconn.so'
<debug> [1704363856.875651] [plugin-manager] loaded shared 'Telit' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-telit.so'
<debug> [1704363856.875849] [plugin-manager] loaded shared 'Sierra' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-sierra.so'
<debug> [1704363856.876007] [plugin-manager] loaded shared 'Intel' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-fibocom.so'
<debug> [1704363856.876226] [plugin-manager] loaded shared 'Xmm' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-xmm.so'
<debug> [1704363856.876434] [plugin-manager] loaded shared 'Icera' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-icera.so'
<debug> [1704363856.876605] [plugin-manager] loaded shared 'Option' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-option.so'
<debug> [1704363856.876914] [plugin-manager] loaded plugin 'simtech' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-simtech.so'
<debug> [1704363856.876923] [filter] registered plugin allowlist vendor id: 1e0e
<debug> [1704363856.877171] [plugin-manager] loaded plugin 'linktop' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-linktop.so'
<debug> [1704363856.877181] [filter] registered plugin allowlist vendor id: 230d
<debug> [1704363856.877378] [plugin-manager] loaded plugin 'generic' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-generic.so'
<debug> [1704363856.877625] [plugin-manager] loaded plugin 'novatel' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-novatel.so'
<debug> [1704363856.877646] [filter] registered plugin allowlist vendor id: 1410
<debug> [1704363856.877911] [plugin-manager] loaded plugin 'zte' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-zte.so'
<debug> [1704363856.877918] [filter] registered plugin allowlist vendor id: 19d2
<debug> [1704363856.878111] [plugin-manager] loaded plugin 'nokia' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-nokia.so'
<debug> [1704363856.878119] [filter] registered plugin allowlist vendor id: 0421
<debug> [1704363856.878381] [plugin-manager] loaded plugin 'option-hso' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-option-hso.so'
<debug> [1704363856.878578] [plugin-manager] loaded plugin 'iridium' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-iridium.so'
<debug> [1704363856.878584] [filter] registered plugin allowlist vendor id: 1edd
<debug> [1704363856.878774] [plugin-manager] loaded plugin 'tp-link' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-tplink.so'
<debug> [1704363856.878781] [filter] registered plugin allowlist vendor id: 2357
<debug> [1704363856.878962] [plugin-manager] loaded plugin 'Intel' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-intel.so'
<debug> [1704363856.878970] [filter] registered plugin allowlist vendor id: 8086
<debug> [1704363856.879172] [plugin-manager] loaded plugin 'motorola' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-motorola.so'
<debug> [1704363856.879180] [filter] registered plugin allowlist product id: 22b8:3802
<debug> [1704363856.879184] [filter] registered plugin allowlist product id: 22b8:4902
<debug> [1704363856.879417] [plugin-manager] loaded plugin 'novatel-lte' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-novatel-lte.so'
<debug> [1704363856.879424] [filter] registered plugin allowlist product id: 1410:9010
<debug> [1704363856.879602] [plugin-manager] loaded plugin 'telit' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-telit.so'
<debug> [1704363856.879609] [filter] registered plugin allowlist vendor id: 1bc7
<debug> [1704363856.879613] [filter] registered plugin allowlist subsystem vendor id: 17cb:1c5d
<debug> [1704363856.879882] [plugin-manager] loaded plugin 'fibocom' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-fibocom.so'
<debug> [1704363856.879889] [filter] registered plugin allowlist vendor id: 2cb7
<debug> [1704363856.879892] [filter] registered plugin allowlist vendor id: 1782
<debug> [1704363856.880121] [plugin-manager] loaded plugin 'anydata' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-anydata.so'
<debug> [1704363856.880128] [filter] registered plugin allowlist vendor id: 16d5
<debug> [1704363856.880282] [plugin-manager] loaded plugin 'broadmobi' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-broadmobi.so'
<debug> [1704363856.880289] [filter] registered plugin allowlist vendor id: 2020
<debug> [1704363856.880497] [plugin-manager] loaded plugin 'pantech' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-pantech.so'
<debug> [1704363856.880504] [filter] registered plugin allowlist vendor id: 106c
<debug> [1704363856.880716] [plugin-manager] loaded plugin 'dell' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-dell.so'
<debug> [1704363856.880723] [filter] registered plugin allowlist vendor id: 413c
<debug> [1704363856.880900] [plugin-manager] loaded plugin 'via' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-via.so'
<debug> [1704363856.881161] [plugin-manager] loaded plugin 'ericsson-mbm' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-ericsson-mbm.so'
<debug> [1704363856.881169] [filter] registered plugin allowlist tag: ID_MM_ERICSSON_MBM
<debug> [1704363856.881406] [plugin-manager] loaded plugin 'quectel' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-quectel.so'
<debug> [1704363856.881426] [filter] registered plugin allowlist vendor id: 2c7c
<debug> [1704363856.881430] [filter] registered plugin allowlist vendor id: 1eac
<debug> [1704363856.881661] [plugin-manager] loaded plugin 'longcheer' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-longcheer.so'
<debug> [1704363856.881668] [filter] registered plugin allowlist tag: ID_MM_LONGCHEER_TAGGED
<debug> [1704363856.881672] [filter] registered plugin allowlist vendor id: 1c9e
<debug> [1704363856.881676] [filter] registered plugin allowlist vendor id: 1bbb
<debug> [1704363856.881833] [plugin-manager] loaded plugin 'foxconn' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-foxconn.so'
<debug> [1704363856.881840] [filter] registered plugin allowlist vendor id: 0489
<debug> [1704363856.881846] [filter] registered plugin allowlist vendor id: 105b
<debug> [1704363856.882116] [plugin-manager] loaded plugin 'cinterion' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-cinterion.so'
<debug> [1704363856.882124] [filter] registered plugin allowlist vendor id: 1e2d
<debug> [1704363856.882129] [filter] registered plugin allowlist vendor id: 0681
<debug> [1704363856.882133] [filter] registered plugin allowlist vendor id: 1269
<debug> [1704363856.882391] [plugin-manager] loaded plugin 'thuraya' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-thuraya.so'
<debug> [1704363856.882411] [filter] registered plugin allowlist vendor id: 1a26
<debug> [1704363856.882612] [plugin-manager] loaded plugin 'nokia-icera' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-nokia-icera.so'
<debug> [1704363856.882789] [plugin-manager] loaded plugin 'd-link' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-dlink.so'
<debug> [1704363856.882796] [filter] registered plugin allowlist vendor id: 2001
<debug> [1704363856.882962] [plugin-manager] loaded plugin 'gosuncn' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-gosuncn.so'
<debug> [1704363856.882970] [filter] registered plugin allowlist vendor id: 305a
<debug> [1704363856.883118] [plugin-manager] loaded plugin 'samsung' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-samsung.so'
<debug> [1704363856.883126] [filter] registered plugin allowlist product id: 04e8:6872
<debug> [1704363856.883130] [filter] registered plugin allowlist product id: 04e8:6906
<debug> [1704363856.883298] [plugin-manager] loaded plugin 'haier' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-haier.so'
<debug> [1704363856.883306] [filter] registered plugin allowlist vendor id: 201e
<debug> [1704363856.883466] [plugin-manager] loaded plugin 'qcom-soc' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-qcom-soc.so'
<debug> [1704363856.883474] [filter] registered plugin allowlist tag: ID_MM_QCOM_SOC
<debug> [1704363856.883665] [plugin-manager] loaded plugin 'altair-lte' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-altair-lte.so'
<debug> [1704363856.883679] [filter] registered plugin allowlist product id: 216f:0047
<debug> [1704363856.883938] [plugin-manager] loaded plugin 'huawei' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-huawei.so'
<debug> [1704363856.883946] [filter] registered plugin allowlist vendor id: 12d1
<debug> [1704363856.884204] [plugin-manager] loaded plugin 'u-blox' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-ublox.so'
<debug> [1704363856.884212] [filter] registered plugin allowlist vendor id: 1546
<debug> [1704363856.884487] [plugin-manager] loaded plugin 'motorola' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-mtk.so'
<debug> [1704363856.884494] [filter] registered plugin allowlist tag: ID_MM_MTK_TAGGED
<debug> [1704363856.884684] [plugin-manager] loaded plugin 'option' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-option.so'
<debug> [1704363856.884691] [filter] registered plugin allowlist vendor id: 0af0
<debug> [1704363856.884695] [filter] registered plugin allowlist vendor id: 1931
<debug> [1704363856.884923] [plugin-manager] loaded plugin 'wavecom' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-wavecom.so'
<debug> [1704363856.884931] [filter] registered plugin allowlist vendor id: 114f
<debug> [1704363856.885246] [plugin-manager] loaded plugin 'x22x' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-x22x.so'
<debug> [1704363856.885253] [filter] registered plugin allowlist tag: ID_MM_X22X_TAGGED
<debug> [1704363856.885256] [filter] registered plugin allowlist vendor id: 0b3c
<debug> [1704363856.885433] [plugin-manager] loaded plugin 'sierra-legacy' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-sierra-legacy.so'
<debug> [1704363856.885653] [plugin-manager] loaded plugin 'sierra' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-sierra.so'
<debug> [1704363856.885661] [filter] registered plugin allowlist vendor id: 1199
<debug> [1704363856.885680] [plugin-manager] successfully loaded 40 plugins registering 6 subsystems: tty, net, usbmisc, wwan, rpmsg, qrtr
<debug> [1704363856.886021] [qrtr] socket lookup from 1:0
<debug> [1704363856.886408] [qrtr] initial lookup finished
<warn>  [1704363856.886661] could not acquire the 'org.freedesktop.ModemManager1' service name
<debug> [1704363856.886669] [base-manager] stopping connection in object manager server
<info>  [1704363856.913793] ModemManager is shut down
<debug> [1704363856.913814] [sleep-monitor-systemd] singleton disposed
<debug> [1704363856.913833] [auth-provider] singleton disposed

This is someone's comment from like 10 years ago with them making mention of it being their hw, but that's it.

https://bugzilla.redhat.com/show_bug.cgi?id=1109559

Someone else seems to say I need to copy something to the systemd directory (I tried). https://mail.gnome.org/archives/networkmanager-list/2013-August/msg00019.html

alphafox02 commented 9 months ago

In global_config.json I've made sure that /dev/cdc-wdm1 is changed to wdm0. Under USBHunControl (was set to false, so maybe not needed) I changed it to true and set the VIPPID of the Quectel RM520N-GL in place of the original Quectel info that was there. Still there's the modem not initialized, so I think I'm running out of the options as to what I can change to utilize this new modem. Perhaps I will have to configure it manually and attempt further steps that way.

Quectel RM520N-GL using usb serial port mode？

I'm actually learning a lot in the process here, I don't believe it's in usb serial port mode so good point. I'm going now to try what @Matheus-Garbelini mentioned.

@alphafox02 Indeed Qualcomm modems normally connect first via QMI interface, which is Qualcomm proprietary (sort of). Although you can communicate with the modem via serial port using AT commands, this is done as a fallback if ModemManager cannot find or use any QMI interface.

Alternatively, if you disable UEModemManager and just start 5Ghoul without global timeout, you can try communicating with the modem yourself by using a serial monitor programa such as putty, cutecom, etc.

Normally, when you open serial port /dev/ttyUSB1 (or another), you can verify that the modem is communicating via serial if it replies AT or OK if you send command "AT". Then you can use other commands such as at+cops=? to search for mobile networks.

Maybe this is the problem. I can connect with TIO to ttyUSB1 (tried 0, 2, and 3 as well but can't type) and type AT etc, but no response.

alphafox02 commented 9 months ago

This is shown under dmesg. I'll keep researching, this is interesting to learn how all this works. 

[461648.192057] usb 1-2: new high-speed USB device number 30 using xhci_hcd
[461648.342725] usb 1-2: New USB device found, idVendor=2c7c, idProduct=0801, bcdDevice= 5.04
[461648.342731] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[461648.342733] usb 1-2: Product: RM520N-GL
[461648.342734] usb 1-2: Manufacturer: Quectel
[461648.342735] usb 1-2: SerialNumber: xxxxxxxx
[461648.360609] option 1-2:1.0: GSM modem (1-port) converter detected
[461648.360752] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[461648.361089] option 1-2:1.1: GSM modem (1-port) converter detected
[461648.361169] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[461648.361428] option 1-2:1.2: GSM modem (1-port) converter detected
[461648.361507] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
[461648.361741] option 1-2:1.3: GSM modem (1-port) converter detected
[461648.361798] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB3
[461648.362810] qmi_wwan 1-2:1.4: cdc-wdm0: USB WDM device
[461648.363033] qmi_wwan 1-2:1.4 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-2, WWAN/QMI device, xxxxxxxxxx
Matheus-Garbelini commented 9 months ago

@alphafox02 some serial programs allows you to enable dtr and rts signals. Can you try enable these signals via some checkbox and try again? Latest cutecom allows these options to be set.

alphafox02 commented 9 months ago

Pulled cutecom from gitlab that showed an update two weeks ago. Built and ran and indeed RTS and DTR allow me to check the boxes after connecting. It still seems there is no response, although in the bottom of the cutecom display it mentions "Device Quectel RM520N-GL @ ttyUSB1 Connection: 115200 @ 8-N-1".

It shows this in the response window with little goofy looking images after the command. AT␍␊ at+cops=?␍␊

Matheus-Garbelini commented 9 months ago

I may need to try Podman. This is what occurs when trying to directly start ModemManager.

./ModemManager 
<info>  ModemManager (version 1.20.7) starting in system bus...
Plugin Dir: /home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager/
<warn>  could not acquire the 'org.freedesktop.ModemManager1' service name
<info>  ModemManager is shut down

This is in debug mode if it helps

./ModemManager --debug
<info>  [1704363856.870258] ModemManager (version 1.20.7) starting in system bus...
<debug> [1704363856.870270] [charsets] detecting platform iconv() support...
<debug> [1704363856.870373] [charsets]   UTF-8: iconv conversion to/from charset is supported
<debug> [1704363856.870385] [charsets]   UCS-2BE: iconv conversion to/from charset is supported
<debug> [1704363856.870410] [charsets]   ASCII: iconv conversion to/from charset is supported
<debug> [1704363856.870516] [charsets]   ISO8859-1: iconv conversion to/from charset is supported
<debug> [1704363856.870589] [charsets]   CP437: iconv conversion to/from charset is supported
<debug> [1704363856.870713] [charsets]   CP850: iconv conversion to/from charset is supported
<debug> [1704363856.870832] [charsets]   UTF-16BE: iconv conversion to/from charset is supported
<debug> [1704363856.871289] Full suspend/resume hooks enabled
<debug> [1704363856.871402] [sleep-monitor-systemd] singleton created
<debug> [1704363856.872318] bus acquired, creating manager...
Plugin Dir: /home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager/
<debug> [1704363856.874511] [auth-provider] singleton created
<debug> [1704363856.874644] [filter] created
<debug> [1704363856.874649] [filter]   explicit allowlist:         yes
<debug> [1704363856.874654] [filter]   explicit blocklist:         yes
<debug> [1704363856.874657] [filter]   plugin allowlist:           yes
<debug> [1704363856.874661] [filter]   qrtr devices allowed:       yes
<debug> [1704363856.874678] [filter]   virtual devices forbidden:  yes
<debug> [1704363856.874680] [filter]   net devices allowed:        yes
<debug> [1704363856.874682] [filter]   usbmisc devices allowed:    yes
<debug> [1704363856.874686] [filter]   rpmsg devices allowed:      yes
<debug> [1704363856.874703] [filter]   wwan devices allowed:       yes
<debug> [1704363856.874706] [filter]   tty devices:
<debug> [1704363856.874708] [filter]       platform driver check:    yes
<debug> [1704363856.874724] [filter]       driver check:             yes
<debug> [1704363856.874727] [filter]       cdc-acm interface check:  yes
<debug> [1704363856.874731] [filter]       with net check:           yes
<debug> [1704363856.874749] [filter]       default:                  forbidden
<debug> [1704363856.874787] [plugin-manager] looking for plugins in '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager/'
<debug> [1704363856.875231] [plugin-manager] loaded shared 'Novatel' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-novatel.so'
<debug> [1704363856.875442] [plugin-manager] loaded shared 'Foxconn' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-foxconn.so'
<debug> [1704363856.875651] [plugin-manager] loaded shared 'Telit' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-telit.so'
<debug> [1704363856.875849] [plugin-manager] loaded shared 'Sierra' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-sierra.so'
<debug> [1704363856.876007] [plugin-manager] loaded shared 'Intel' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-fibocom.so'
<debug> [1704363856.876226] [plugin-manager] loaded shared 'Xmm' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-xmm.so'
<debug> [1704363856.876434] [plugin-manager] loaded shared 'Icera' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-icera.so'
<debug> [1704363856.876605] [plugin-manager] loaded shared 'Option' utils from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-shared-option.so'
<debug> [1704363856.876914] [plugin-manager] loaded plugin 'simtech' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-simtech.so'
<debug> [1704363856.876923] [filter] registered plugin allowlist vendor id: 1e0e
<debug> [1704363856.877171] [plugin-manager] loaded plugin 'linktop' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-linktop.so'
<debug> [1704363856.877181] [filter] registered plugin allowlist vendor id: 230d
<debug> [1704363856.877378] [plugin-manager] loaded plugin 'generic' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-generic.so'
<debug> [1704363856.877625] [plugin-manager] loaded plugin 'novatel' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-novatel.so'
<debug> [1704363856.877646] [filter] registered plugin allowlist vendor id: 1410
<debug> [1704363856.877911] [plugin-manager] loaded plugin 'zte' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-zte.so'
<debug> [1704363856.877918] [filter] registered plugin allowlist vendor id: 19d2
<debug> [1704363856.878111] [plugin-manager] loaded plugin 'nokia' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-nokia.so'
<debug> [1704363856.878119] [filter] registered plugin allowlist vendor id: 0421
<debug> [1704363856.878381] [plugin-manager] loaded plugin 'option-hso' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-option-hso.so'
<debug> [1704363856.878578] [plugin-manager] loaded plugin 'iridium' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-iridium.so'
<debug> [1704363856.878584] [filter] registered plugin allowlist vendor id: 1edd
<debug> [1704363856.878774] [plugin-manager] loaded plugin 'tp-link' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-tplink.so'
<debug> [1704363856.878781] [filter] registered plugin allowlist vendor id: 2357
<debug> [1704363856.878962] [plugin-manager] loaded plugin 'Intel' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-intel.so'
<debug> [1704363856.878970] [filter] registered plugin allowlist vendor id: 8086
<debug> [1704363856.879172] [plugin-manager] loaded plugin 'motorola' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-motorola.so'
<debug> [1704363856.879180] [filter] registered plugin allowlist product id: 22b8:3802
<debug> [1704363856.879184] [filter] registered plugin allowlist product id: 22b8:4902
<debug> [1704363856.879417] [plugin-manager] loaded plugin 'novatel-lte' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-novatel-lte.so'
<debug> [1704363856.879424] [filter] registered plugin allowlist product id: 1410:9010
<debug> [1704363856.879602] [plugin-manager] loaded plugin 'telit' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-telit.so'
<debug> [1704363856.879609] [filter] registered plugin allowlist vendor id: 1bc7
<debug> [1704363856.879613] [filter] registered plugin allowlist subsystem vendor id: 17cb:1c5d
<debug> [1704363856.879882] [plugin-manager] loaded plugin 'fibocom' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-fibocom.so'
<debug> [1704363856.879889] [filter] registered plugin allowlist vendor id: 2cb7
<debug> [1704363856.879892] [filter] registered plugin allowlist vendor id: 1782
<debug> [1704363856.880121] [plugin-manager] loaded plugin 'anydata' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-anydata.so'
<debug> [1704363856.880128] [filter] registered plugin allowlist vendor id: 16d5
<debug> [1704363856.880282] [plugin-manager] loaded plugin 'broadmobi' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-broadmobi.so'
<debug> [1704363856.880289] [filter] registered plugin allowlist vendor id: 2020
<debug> [1704363856.880497] [plugin-manager] loaded plugin 'pantech' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-pantech.so'
<debug> [1704363856.880504] [filter] registered plugin allowlist vendor id: 106c
<debug> [1704363856.880716] [plugin-manager] loaded plugin 'dell' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-dell.so'
<debug> [1704363856.880723] [filter] registered plugin allowlist vendor id: 413c
<debug> [1704363856.880900] [plugin-manager] loaded plugin 'via' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-via.so'
<debug> [1704363856.881161] [plugin-manager] loaded plugin 'ericsson-mbm' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-ericsson-mbm.so'
<debug> [1704363856.881169] [filter] registered plugin allowlist tag: ID_MM_ERICSSON_MBM
<debug> [1704363856.881406] [plugin-manager] loaded plugin 'quectel' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-quectel.so'
<debug> [1704363856.881426] [filter] registered plugin allowlist vendor id: 2c7c
<debug> [1704363856.881430] [filter] registered plugin allowlist vendor id: 1eac
<debug> [1704363856.881661] [plugin-manager] loaded plugin 'longcheer' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-longcheer.so'
<debug> [1704363856.881668] [filter] registered plugin allowlist tag: ID_MM_LONGCHEER_TAGGED
<debug> [1704363856.881672] [filter] registered plugin allowlist vendor id: 1c9e
<debug> [1704363856.881676] [filter] registered plugin allowlist vendor id: 1bbb
<debug> [1704363856.881833] [plugin-manager] loaded plugin 'foxconn' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-foxconn.so'
<debug> [1704363856.881840] [filter] registered plugin allowlist vendor id: 0489
<debug> [1704363856.881846] [filter] registered plugin allowlist vendor id: 105b
<debug> [1704363856.882116] [plugin-manager] loaded plugin 'cinterion' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-cinterion.so'
<debug> [1704363856.882124] [filter] registered plugin allowlist vendor id: 1e2d
<debug> [1704363856.882129] [filter] registered plugin allowlist vendor id: 0681
<debug> [1704363856.882133] [filter] registered plugin allowlist vendor id: 1269
<debug> [1704363856.882391] [plugin-manager] loaded plugin 'thuraya' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-thuraya.so'
<debug> [1704363856.882411] [filter] registered plugin allowlist vendor id: 1a26
<debug> [1704363856.882612] [plugin-manager] loaded plugin 'nokia-icera' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-nokia-icera.so'
<debug> [1704363856.882789] [plugin-manager] loaded plugin 'd-link' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-dlink.so'
<debug> [1704363856.882796] [filter] registered plugin allowlist vendor id: 2001
<debug> [1704363856.882962] [plugin-manager] loaded plugin 'gosuncn' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-gosuncn.so'
<debug> [1704363856.882970] [filter] registered plugin allowlist vendor id: 305a
<debug> [1704363856.883118] [plugin-manager] loaded plugin 'samsung' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-samsung.so'
<debug> [1704363856.883126] [filter] registered plugin allowlist product id: 04e8:6872
<debug> [1704363856.883130] [filter] registered plugin allowlist product id: 04e8:6906
<debug> [1704363856.883298] [plugin-manager] loaded plugin 'haier' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-haier.so'
<debug> [1704363856.883306] [filter] registered plugin allowlist vendor id: 201e
<debug> [1704363856.883466] [plugin-manager] loaded plugin 'qcom-soc' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-qcom-soc.so'
<debug> [1704363856.883474] [filter] registered plugin allowlist tag: ID_MM_QCOM_SOC
<debug> [1704363856.883665] [plugin-manager] loaded plugin 'altair-lte' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-altair-lte.so'
<debug> [1704363856.883679] [filter] registered plugin allowlist product id: 216f:0047
<debug> [1704363856.883938] [plugin-manager] loaded plugin 'huawei' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-huawei.so'
<debug> [1704363856.883946] [filter] registered plugin allowlist vendor id: 12d1
<debug> [1704363856.884204] [plugin-manager] loaded plugin 'u-blox' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-ublox.so'
<debug> [1704363856.884212] [filter] registered plugin allowlist vendor id: 1546
<debug> [1704363856.884487] [plugin-manager] loaded plugin 'motorola' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-mtk.so'
<debug> [1704363856.884494] [filter] registered plugin allowlist tag: ID_MM_MTK_TAGGED
<debug> [1704363856.884684] [plugin-manager] loaded plugin 'option' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-option.so'
<debug> [1704363856.884691] [filter] registered plugin allowlist vendor id: 0af0
<debug> [1704363856.884695] [filter] registered plugin allowlist vendor id: 1931
<debug> [1704363856.884923] [plugin-manager] loaded plugin 'wavecom' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-wavecom.so'
<debug> [1704363856.884931] [filter] registered plugin allowlist vendor id: 114f
<debug> [1704363856.885246] [plugin-manager] loaded plugin 'x22x' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-x22x.so'
<debug> [1704363856.885253] [filter] registered plugin allowlist tag: ID_MM_X22X_TAGGED
<debug> [1704363856.885256] [filter] registered plugin allowlist vendor id: 0b3c
<debug> [1704363856.885433] [plugin-manager] loaded plugin 'sierra-legacy' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-sierra-legacy.so'
<debug> [1704363856.885653] [plugin-manager] loaded plugin 'sierra' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-sierra.so'
<debug> [1704363856.885661] [filter] registered plugin allowlist vendor id: 1199
<debug> [1704363856.885680] [plugin-manager] successfully loaded 40 plugins registering 6 subsystems: tty, net, usbmisc, wwan, rpmsg, qrtr
<debug> [1704363856.886021] [qrtr] socket lookup from 1:0
<debug> [1704363856.886408] [qrtr] initial lookup finished
<warn>  [1704363856.886661] could not acquire the 'org.freedesktop.ModemManager1' service name
<debug> [1704363856.886669] [base-manager] stopping connection in object manager server
<info>  [1704363856.913793] ModemManager is shut down
<debug> [1704363856.913814] [sleep-monitor-systemd] singleton disposed
<debug> [1704363856.913833] [auth-provider] singleton disposed

This is someone's comment from like 10 years ago with them making mention of it being their hw, but that's it.

https://bugzilla.redhat.com/show_bug.cgi?id=1109559

Someone else seems to say I need to copy something to the systemd directory (I tried). https://mail.gnome.org/archives/networkmanager-list/2013-August/msg00019.html

Indeed it's a docker problem (systemd services backend not working). Will need to update the container.sh to install and use podman instead. Since we deployed the container on docker after testing with phones, we didn't check again the modems on docker (only on podman). I will then keep podman as the final solution to facilitate 5ghoul use for everyone.

I'm your case, you can install the podman from that podman static repository using the latest version they have. After that you can update all commands from docker to podman. Simple word replacement should do it. I will stay out of internet for a while now, but will get back to your tests on 5th or 6th. Thanks a lot for your time on this 👍.

alphafox02 commented 9 months ago

No problems, this is enjoyable. I joke sometimes on X, but this is helping me learn more about modems. I think I have to figure out why though this new modem is not responding to AT commands. Have a great day !

Matheus-Garbelini commented 9 months ago

Pulled cutecom from gitlab that showed an update two weeks ago. Built and ran and indeed RTS and DTR allow me to check the boxes after connecting. It still seems there is no response, although in the bottom of the cutecom display it mentions "Device Quectel RM520N-GL @ ttyUSB1 Connection: 115200 @ 8-N-1".

It shows this in the response window with little goofy looking images after the command. AT␍␊ at+cops=?␍␊

Hum, do you get anything else after sending the command ATI? This is to sort of probe the firmware version of the modem. Also have you tried with cr+cl enabled and alternating one checkbox at a time? Not sure if this modem needs both signals enabled or just one.

alphafox02 commented 9 months ago

Messing around now, it's odd that this link (waveshare) talks about the modem but mentions that ttyUSB2 is for AT. That does not seem the case for this GL INET, as USB1 allows connection but 2 does not. https://www.waveshare.com/wiki/RM520N-GL_5G_HAT

I'm clicking on and off options now and when I set the input to CR and type in AT, it does look at this a response is occurring. This is also with RTS and DTR checked. It's not readable what is coming back though, if that little icon even means anything.

AT ␍ ␊

alphafox02 commented 9 months ago

Well, so now I think I'm getting a little off topic, but the GL-INET forums has people talking about the modem and there's a picture where someone is sending commands from the router. Interestingly it shows USB2 being used.

https://forum.gl-inet.com/t/m2-5g-development-board/36252/12

alphafox02 commented 9 months ago

Got it, just needed to have tio /dev/ttyUSB2 up and running, then I plugged in the modem. I get responses now. So maybe something else is claiming control of the modem on my host after it's plugged in. I'll now go try Cutecom again.

alphafox02 commented 9 months ago

Pulled cutecom from gitlab that showed an update two weeks ago. Built and ran and indeed RTS and DTR allow me to check the boxes after connecting. It still seems there is no response, although in the bottom of the cutecom display it mentions "Device Quectel RM520N-GL @ ttyUSB1 Connection: 115200 @ 8-N-1". It shows this in the response window with little goofy looking images after the command. AT␍␊ at+cops=?␍␊

Hum, do you get anything else after sending the command ATI? This is to sort of probe the firmware version of the modem. Also have you tried with cr+cl enabled and alternating one checkbox at a time? Not sure if this modem needs both signals enabled or just one.

With Auto-Reconnect on, RTS/DTR checked and CR/LF in input. I just need to obtain control over ttyUSB2 right away it seems. 

Quectel␍␊
RM520N-GL␍␊
Revision: RM520NGLAAR01A07M4G␍␊
alphafox02 commented 9 months ago

Follow up, after switching to podman and redoing things, I am showing ModemManager finding the modem

[ModemManger] Got Modem at /dev/cdc-wdm0.

If I let things run for a few minutes or so it will sometimes spit out commands as thought it's telling the modem to do various things. I posted some pictures to X. However, tomorrow I think I need to swith from doing this within a VM to my host (didn't want to remove docker).

It's also odd, I swear I saw activtiy on/around 3600Mhz from the B210 I'm borrowing, but once I got the modem working I'm not seeing any activity on a SpecA from the B210 (red tx light is on).

Getting closer!

Matheus-Garbelini commented 9 months ago

Hi @alphafox02 that's great to know. You can try enabling UEModemManager again as you confirmed that modem manager was able to detect the modem. Basically the fuzzer will run modemmanager for you and call some commands like the following:

Useful mmcli commands:

# Disable modem at+cfun=0
sudo mmcli -m any --disable
# Enable modem at+cfun=1
sudo mmcli -m any --enable
# Configure prefered modem mode to 5g
sudo mmcli -m any --set-allowed-modes '4g|5g'  --set-preferred-mode '5g'
# Set modem band to channel n78 (5G)
sudo mmcli -m any --set-current-bands='ngran-78'
# Connect to 90170
sudo mmcli -m any --simple-connect='apn=internet,ip-type=ipv4,allow-roaming=yes,operator-id=90170'
# Connect to 00101
sudo mmcli -m any --simple-connect='apn=internet,ip-type=ipv4,allow-roaming=yes,operator-id=00101'
# Disconnect
# Loop the commands below
sudo mmcli -m any --simple-disconnect
# Force disconnection (LOW power mode)
sudo mmcli -m any --set-power-state-low
# Reconnect (ON power mode)
sudo mmcli -m any --set-power-state-on

Useful qmicli commands:

# Get APN profile list
sudo qmicli -d /dev/cdc-wdm2 -p --wds-get-profile-list=3gpp
# Change 1st APN profile
sudo qmicli -d /dev/cdc-wdm2 -p --wds-modify-profile="3gpp,1,apn=,pdp-type=ipv4"
# Delete 2nd APN profile
sudo qmicli -d /dev/cdc-wdm2 -p --wds-delete-profile="3gpp,2"
# Allow autoconnection
sudo qmicli -d /dev/cdc-wdm2 -p --wds-set-autoconnect-settings=enabled,roaming-allowed

Note that you can check what frequency bands are enabled from your 5G modem by running the following command after executing modemmanager (or the fuzzer with UEModemManager enabled): sudo mmcli -m any

Also, what what's the default MCC MNC that your sysmocom simcard is? You also need to configure it them in https://github.com/asset-group/5ghoul-5g-nr-attacks/blob/master/configs/5gnr_gnb_config.json#L25-L26 (or use the --MCC=XXX --MNC=XX arguments.

Notably, to change your SIM card to 001/01 you'd need a SIM card programmer such as this. But since you are using a 5G modem, it should not restrict you on this (works very well under linux using pysim project). Anyway, you can confirm this by checking the output of mmcli -m any and see if there is any 5G (NR) band listed there.

Follow up, after switching to podman and redoing things, I am showing ModemManager finding the modem

[ModemManger] Got Modem at /dev/cdc-wdm0.

If I let things run for a few minutes or so it will sometimes spit out commands as thought it's telling the modem to do various things. I posted some pictures to X. However, tomorrow I think I need to swith from doing this within a VM to my host (didn't want to remove docker).

It's also odd, I swear I saw activtiy on/around 3600Mhz from the B210 I'm borrowing, but once I got the modem working I'm not seeing any activity on a SpecA from the B210 (red tx light is on).

Getting closer!

Yes, modemmanager will communicate with the modem in the background, but it's mmcli or qmicli that will start some action such as connecting to a network or configuring modem settings. As for the lack of activity on spectrum 3.6Ghz, I'm not sure. You can try manually scanning for 5G network by using AT+COPS=? serial command. Note that configuring which bands the modem should look for, can greatly accelerates the process to scan 4G/5G networks: sudo mmcli -m any --set-allowed-modes '4g|5g' --set-preferred-mode '5g'

alphafox02 commented 9 months ago

Wait before you make changes from docker to podman.. I left my host machine running for awhile that's using docker and guess what.. this suddenly happened. I'm not sure why or how though.

[ModemManager] Modem Initialized [ModemManager] Configuring Modem... [ModemManager] [1/7] Disconnecting Modem from any base-station [ModemManager] UE Command: Disconnect (AT+COPS=2) [ModemManager] [2/7] Enabling Modem adb: no devices/emulators found

alphafox02 commented 9 months ago

All this is happening on the host now that has 5ghoul running with docker. I was messing with the timeout, so ignore that. I've yet to see the modem connect to the enb. I can see what looks like the enb while centered on 3616Mhz.

[ModemManager] Modem Initialized
[ModemManager] Configuring Modem...
[ModemManager] [1/7] Disconnecting Modem from any base-station
[ModemManager] UE Command: Disconnect (AT+COPS=2)
[ModemManager] [2/7] Enabling Modem
adb: no devices/emulators found
adb: protocol fault (couldn't read status): Connection reset by peer
adb: no devices/emulators found
[ModemManager] [3/7] --set--allowed-modes="4g|5g" --set-preferred-mode="5g"
[ModemManager] [4/7] Deleting unused APNs
adb: no devices/emulators found
[ModemManager] [5/7] Setting APN to internet
[ModemManager] [6/7] Enabling APN autoreconnection
[ModemManager] [7/7] Releasing ModemManager control (--disable)
adb: no devices/emulators found
[ModemManager] Starting Automatic Modem Connection/Reconnection
[ModemManager] Disabling Fuzzing Parameters for first connection
[ModemManager] UE Command: Connect (AT+COPS=1,2,90170,12)
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
[ModemManager] Fuzzing Parameters Recovered
[ModemManager] Modem configured and ready to accept commands!
[ModemManager] Reconnection Timeout (8000 ms)
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
[ModemManager] UE Command: Disconnect (AT+COPS=2)
[ModemManager] UE Command: Connect (AT+COPS=1,2,90170,12)
[ModemManager] Reconnection Timeout (8000 ms)
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
[ModemManager] UE Command: Disconnect (AT+COPS=2)
[ModemManager] UE Command: Connect (AT+COPS=1,2,90170,12)
[ModemManager] Reconnection Timeout (8000 ms)
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
[ModemManager] UE Command: Disconnect (AT+COPS=2)
[ModemManager] UE Command: Connect (AT+COPS=1,2,90170,12)
[ModemManager] Reconnection Timeout (8000 ms)
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
adb: no devices/emulators found
[ModemManager] UE Command: Disconnect (AT+COPS=2)
[ModemManager] UE Command: Connect (AT+COPS=1,2,90170,12)
[ModemManager] Reconnection Timeout (8000 ms)
adb: no devices/emulators found
alphafox02 commented 9 months ago

sudo mmcli -m any --simple-connect='apn=internet,ip-type=ipv4,allow-roaming=yes,operator-id=99970'

I find that command to hang when trying to run it manually. I realized my sim cards, according to the site, after 2021 are programmed to 99970. However, I've yet to see a connection. I'm assuming maybe nothing will show up unless I program the sim details into the 5ghoul conf file, just figured maybe I'd see an attempted connection.

Matheus-Garbelini commented 9 months ago

Hi @alphafox02 that might be the issue (perhaps you can use --MCC=999 --MNC=70 to start 5ghoul). However, you can check if you modem lists any 5G networks nearby while 5Ghoul is running with UEModemManager disabled. You can simply send this command via serial port: AT+COPS=? (ttyUSB2), the modem shall return a network entry with 12 within an entry to indicate 5G (might take a minute to get a reply). You can also try inserting a commercial SIM card that you have to check if this is an issue with Modem locking some IMSI types to 4G only.

Also, do you get to see indications of 5G bands when running command sudo mmcli -m any? Usually it shows many bands such as nr-78 or similar. It also shows your SIM IMSI in case you are wondering if it's indeed programmed to 99970 by default. Note that the command mmcli -m any --simple-connect expects the operator-id of the network, not the SIM card. So in your situation you can try running 5Ghoul with --MCC=999 --MNC=70 and then use sudo mmcli -m any --simple-connect='apn=internet,ip-type=ipv4,allow-roaming=yes,operator-id=99970'. Otherwise, you can use --MCC=001 --MNC=01 and then sudo mmcli -m any --simple-connect='apn=internet,ip-type=ipv4,allow-roaming=yes,operator-id=00101'. But for initial tests I just send a serial command to the modem to connect to 001/01: AT+COPS=1,2,00101,12.

Wait before you make changes from docker to podman. I left my host machine running for awhile that's using docker and guess what.. this suddenly happened. I'm not sure why or how though.

If you your host is running ModemManager in the background it can indeed interfere with ModemManager inside the container or use of serial port as you pointed before. Usually I disable the host's system manager via this commands: sudo systemctl stop ModemManager.service and sudo systemctl disable ModemManager.service

All this is happening on the host now that has 5ghoul running with docker. I was messing with the timeout, so ignore that. I've yet to see the modem connect to the enb. I can see what looks like the enb while centered on 3616Mhz.

You can disable this message adb: no devices/emulators found by setting this entry in the config. file to false: https://github.com/asset-group/5ghoul-5g-nr-attacks/blob/3e61d51b0eea21c1743d027b0a8965b925881703/configs/5gnr_gnb_config.json#L205

Got it, just needed to have tio /dev/ttyUSB2 up and running, then I plugged in the modem. I get responses now. So maybe something else is claiming control of the modem on my host after it's plugged in. I'll now go try Cutecom again.

You can use fuser to see who is using certain serial ports: sudo fuser /dev/ttyUSB2 It should return the PID of the process using the serial port, otherwise it will return nothing if the port is free.

alphafox02 commented 9 months ago

Here's where I'm at and I'll try and make sure I hit everything. 


I'm going to go do more testing, but when you reference mmcli commands above - how are you running them within the docker? ModemManager does not appear to be installed system wide in the docker and when I navigate to the 3rd party directory and find mmcli in the cli folder to call it directly, it complains that error: couldn't find the ModemManager process in the bus and I've yet to manually be able to start the ModemManager in the docker myself (except for when the UEmanager is doing it, I think).
Matheus-Garbelini commented 9 months ago

AT+COPS=? always returns +CME ERROR: 3 which I believe is also the case with the Tmobile 5G sim in as well

@alphafox02 Hum, the modem might be busy attempting to do an auto re-connection and returns an errors when scanning. You can try the following commands to force the modem to disconnect from any network and get back to an idle state (modem manager cannot be running when issuing this commands, otherwise, it blocks the serial port or issue conflicting commands to the modem): AT+CFUN=0 - Disable the modem (similar to airplane mode in phones) AT+CFUN=1 - Enable modem AT+COPS=2 - Disconnect modem from any networks AT+COPS=? - Scan networks in a fresh modem state

how are you running them within the docker?

I got back to podman. podman-static to be precise (installing it system-wide is a mess), but let me know if ModemManager works for you inside a docker container. Then, I run the following commands in 2 terminals:

# Terminal 1
cd ./3rd-party/ModemManager/runtime/sbin/ && sudo ./ModemManager --debug
# Terminal 2
cd ./3rd-party/ModemManager/runtime/bin/
sudo ./mmcli -m any

The modem manager is not installed in the container systems as you pointed out, but rather into folder ./3rd-party/ModemManager/runtime/. When you start 5ghoul with UEModemManager ON, the fuzzer simply executes the ModemManager binary before issuing any mmcli commands.

alphafox02 commented 9 months ago

I had high hopes, but after making absolutely sure the ModemManager was not running on my host, I used CuteCom to issue the following to the modem while it had a Tmobile 5g capable Sim inserted (tested the sim in a phone at the same location and it showed as though it connected to a 5G signal)

AT+CFUN=0 - Disable the modem (similar to airplane mode in phones)
AT+CFUN=1 - Enable modem
AT+COPS=2 - Disconnect modem from any networks
AT+COPS=? - Scan networks in a fresh modem state

Each time it comes back with the CME ERROR:3 - which I'm not sure if it's a bad error or just returning that because it can't see a network?

Now for the ModemManager in docker with your steps it does start! So maybe the before issue was I had it running on host? I should check that. mmcli -m any also worked within the container, but I did unplug the usb and plug it back in form the modem and observed the ModemManager window spit out a ton of info before I then ran the mmcli command.

I feel like I'm so close? screen04

Matheus-Garbelini commented 8 months ago

Hi @alphafox02 this is a bit weird since scanning is always a basic functionality of any modem. Can you try just unplugging and plugging the modem on your host PC and issuing this AT+COPS=? command again? 5Ghoul does not need to be running. CME ERROR:3 basically means Modem Hanging/Busy or operation not allowed. You can try this commands with different SIM cards that you have.

alphafox02 commented 8 months ago

I agree, very strange. It happens with the programmable sim cards and the Tmobile 5g sim card. In each case it comes back with the error. The only technique that's seemed semi promising is the mmcli commands and observing the debug output of ModemManager. In a few days I will have a GL INET router and will see what happens when I use it with the modem. I'm beginning to think a sim issue or I'm just unlucky!

alphafox02 commented 8 months ago

So after all this, I went and found my older orangeish sysmocom sims that are 90170.. and guess what?

sudo ./mmcli -m any --simple-connect='apn=internet,ip-type=ipv4,allow-roaming=yes,operator-id=90170'

And the modem attempts to connect to the gNB. I now have to program in my details to allow connection as it's getting the registration reject. I bet the AT Scan failure code is maybe something with the sim? I'll have to try this sim that I have in now.

alphafox02 commented 8 months ago 
[Main] eNB/gNB started!
[!] Waiting UE task to start...
--------------------------------------------------------
[Optimizer] Iter=1  Params=[0.2,0.2,0.2,0.2,0.2,0.2,...,0.2]
[Optimizer] Fitness=2  Adj. Fitness=-2
--------------------------------------------------------
[!] 1/2 UE connected to eNB/gNB
Matheus-Garbelini commented 8 months ago

Hi @alphafox02 that's great to know. Indeed this modem seems to not work properly with previous SIM cards (programmed or Tmobile 5g). I will update the documentation accordingly to require the SIM card and programmer for those who are having problems with their SIM cards.

And the modem attempts to connect to the gNB. I now have to program in my details to allow connection as it's getting the registration reject. I bet the AT Scan failure code is maybe something with the sim? I'll have to try this sim that I have in now.

So, as for registration reject, you just need update any of the IMSI entries in "NR5G->Subscribers" of file configs/5gnr_gnb_config.json to match your SIM card: https://github.com/asset-group/5ghoul-5g-nr-attacks/blob/3e61d51b0eea21c1743d027b0a8965b925881703/configs/5gnr_gnb_config.json#L36-L41

Note that you don't need to use the correct "K", "OPC", or "APN" paremeters since 5Ghoul attacks work before authentication, thus inserting the IMSI is enough to avoid the stack to drop the UE early.

However, if you would like to use 5Ghoul as a fully working legitimate 5G base-station with internet connectivity, then inserting the correct key parameters is necessary.

shuimoshusheng commented 7 months ago

I downloaded ModermManager (host ubuntu 18.04) using the aptcommand inside the docker container, and checked the output using the systemctl status ModermManager command inside the container as follows： ModemManager.service - Modem Manager Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled) Active: inactive (dead) The fuzz program still outputs the following content： [ModemManager] StartModemConnection: Modem not initialized [ModemManager] Reconnection Timeout (4000 ms)

Container launched using Docker Run command instead of Podman.

alphafox02 commented 7 months ago

ModemManger doesn’t need installed with apt inside the docker, however, it does need stopped on the host if its installed and running there. Inside the docker modem manager is found and started as mentioned above like this 

# Terminal 1
cd ./3rd-party/ModemManager/runtime/sbin/ && sudo ./ModemManager --debug

Hope that helps.

shuimoshusheng commented 7 months ago

ModemManger doesn’t need installed with apt inside the docker, however, it does need stopped on the host if its installed and running there. Inside the docker modem manager is found and started as mentioned above like this

# Terminal 1
cd ./3rd-party/ModemManager/runtime/sbin/ && sudo ./ModemManager --debug

Hope that helps.

Thanks a lot, I ran this command sudo ./ModemManager --debug inside the docker container， Part of the log is as follows： ` [1709081688.338669] [plugin-manager] loaded plugin 'qcom-soc' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-qcom-soc.so'

[1709081688.338673] [filter] registered plugin allowlist tag: ID_MM_QCOM_SOC [1709081688.338745] [plugin-manager] loaded plugin 'anydata' from '/home/user/wdissector/3rd-party/ModemManager/runtime/sbin/../lib/x86_64-linux-gnu/ModemManager//libmm-plugin-anydata.so' [1709081688.338748] [filter] registered plugin allowlist vendor id: 16d5 [1709081688.338751] [plugin-manager] successfully loaded 40 plugins registering 6 subsystems: tty, net, usbmisc, wwan, rpmsg, qrtr [1709081688.339893] could not acquire the 'org.freedesktop.ModemManager1' service name [1709081688.339899] [base-manager] stopping connection in object manager server [1709081688.340378] ModemManager is shut down [1709081688.340396] [sleep-monitor-systemd] singleton disposed [1709081688.340400] [auth-provider] singleton disposed ` ![image](https://github.com/asset-group/5ghoul-5g-nr-attacks/assets/15867686/3f4576cb-b563-49ef-bda5-827a1a3e35b9)