The root cause here looks like this message: [000 CONN_CLIENT] No slotmap (yet) for client C(1:1)
When you did the mapping, did the server or banks list any errors? I get errors if I have previous mappings and I try to reapply them without explicitly deleting the old mappings first.
On Mon, Jul 17, 2023 at 12:16 PM gmaillee@126.com wrote:
First of all thank you for your reply! My operation may be slightly different from yours. Because I put bankd. server. client-st2 is installed in three linux respectively. bankd and server are linux simulated by vm, and client-st2 is installed separately on a linux host debian@debian:/bin$ su 密码： root@debian:/bin# pcsc_scan Using reader plug'n play mechanism Scanning present readers... 0: HID Global OMNIKEY 6121 Smart Card Reader [OMNIKEY 6121 Smart Card Reader] 00 00
Mon Jul 17 16:43:49 2023 Reader 0: HID Global OMNIKEY 6121 Smart Card Reader [OMNIKEY 6121 Smart Card Reader] 00 00 Event number: 0 Card state: Card inserted, ATR: 3B 9C 95 80 1F C7 80 31 E0 73 FE 21 13 64 10 C0 C0 0F C4
ATR: 3B 9C 95 80 1F C7 80 31 E0 73 FE 21 13 64 10 C0 C0 0F C4
- TS = 3B --> Direct Convention
- T0 = 9C, Y(1): 1001, K: 12 (historical bytes) TA(1) = 95 --> Fi=512, Di=16, 32 cycles/ETU 125000 bits/s at 4 MHz, fMax for Fi = 5 MHz => 156250 bits/s TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
TD(2) = 1F --> Y(i+1) = 0001, Protocol T = 15 - Global interface bytes following
TA(3) = C7 --> Clock stop: no preference - Class accepted by the card: (3G) A 5V B 3V C 1.8V
- Historical bytes: 80 31 E0 73 FE 21 13 64 10 C0 C0 0F Category indicator byte: 80 (compact TLV data object) Tag: 3, len: 1 (card service data byte) Card service data byte: E0 - Application selection: by full DF name - Application selection: by partial DF name - BER-TLV data objects available in EF.DIR - EF.DIR and EF.ATR access services: by GET RECORD(s) command - Card with MF Tag: 7, len: 3 (card capabilities) Selection methods: FE - DF selection by full DF name - DF selection by partial DF name - DF selection by path - DF selection by file identifier - Implicit DF selection - Short EF identifier supported - Record number supported Data coding byte: 21 - Behaviour of write functions: proprietary - Value 'FF' for the first byte of BER-TLV tag fields: invalid - Data unit in quartets: 2 Command chaining, length fields and logical channels: 13 - Logical channel number assignment: by the card - Maximum number of logical channels: 4 Tag: 6, len: 4 (pre-issuing data) Data: 10 C0 C0 0F
- TCK = C4 (correct checksum)
Possibly identified card (using /root/.cache/smartcard_list.txt): NONE
Updating /root/.cache/smartcard_list.txt using http://ludovic.rousseau.free.fr/softwares/pcsc-tools/smartcard_list.txt This is the data from the reader part of my bankd side. On the bank side, I set it like this: osmo-emsim-band -i 192.168.2.128 -b 1 -n 1 debian@debian:/usr/bin$ su 密码： root@debian:/usr/bin# osmo-remsim-bankd -i 192.168.2.128 -b 1 -n 1 3511 DMAIN INFO bankd_pcsc.c:105 PC/SC slot name: 1/0 -> regex 'HID Global OMNIKEY 6121 Smart Card Reader [OMNIKEY 6121 Smart Card Reader] 00 00' 3511 DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to server at 192.168.2.128:9998 3512 DBANKDW INFO bankd_main.c:442 [000 INIT] Changing state to INIT 3512 DBANKDW INFO bankd_main.c:442 [000 INIT] Changing state to ACCEPTING 3511 DLINP NOTICE input/ipa.c:141 192.168.2.128:9998 connection done 3511 DRSPRO NOTICE ../rspro_client_fsm.c:127 RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to 192.168.2.128:9998 UP Then I started to configure another client on linux. I linked simtrace2 to this host before configuring, and linked simtrace2 to the mobile phone through fpc. The phone is turned off. root@openstick:~# lsusb Bus 001 Device 003: ID 1d50:60e3 OpenMoko, Inc. Osmocom SIMtrace 2 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@openstick:~# osmo-remsim-client-st2 --usb-vendor 1d50 --usb-product 60e3 --usb-interface 0 --usb-altsetting 0 --usb-address 3 --usb-path 1-1.1 --usb-config 1 --client-id 1 --client-slot 1 --server-ip 192.168.2.128 --server-port 9998 DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to server at 192.168.2.128:9998 DLINP NOTICE simtrace2_api.c:271 [0] <= osmo_st2_cardem_request_config(features=00000001) DLINP NOTICE input/ipa.c:141 192.168.2.128:9998 connection done DRSPRO NOTICE ../rspro_client_fsm.c:127 RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to 192.168.2.128:9998 UP then i turn on the phone DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 DST2 ERROR user_simtrace2.c:152 unknown simtrace msg type 0x00 This is what the system shows There should be a problem here. but i don't know why I continued to try the server part and got the following. root@debian:/bin# osmo-remsim-apitool -m 1 1 1 1 root@debian:/bin# osmo-remsim-apitool -s /slotmaps: {'slotmaps': [{'bank': {'bankId': 1, 'slotNr': 1}, 'client': {'clientId': 1, 'slotNr': 1}, 'state': 'ACTIVE'}]} root@debian:/bin# At this time, the client2 part displays DLINP NOTICE input/ipa.c:141 192.168.2.131:9999 connection done DRSPRO NOTICE ../rspro_client_fsm.c:127 RSPRO_CLIENT(bankd){REESTABLISH}: RSPRO link to 192.168.2.131:9999 UP DRSPRO ERROR ../rspro_client_fsm.c:297 RSPRO_CLIENT(bankd){REESTABLISH}: Event SRVC_E_KA_TERMINATED not permitted DRSPRO INFO ../rspro_client_fsm.c:302 RSPRO_CLIENT(bankd){REESTABLISH}: Destroying existing connection to server DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(bankd){REESTABLISH}: Creating TCP connection to server at 192.168.2.131:9999 DLINP NOTICE input/ipa.c:141 192.168.2.131:9999 connection done DRSPRO NOTICE ../rspro_client_fsm.c:127 RSPRO_CLIENT(bankd){REESTABLISH}: RSPRO link to 192.168.2.131:9999 UP DRSPRO ERROR ../rspro_client_fsm.c:297 RSPRO_CLIENT(bankd){REESTABLISH}: Event SRVC_E_KA_TERMINATED not permitted DRSPRO INFO ../rspro_client_fsm.c:302 RSPRO_CLIENT(bankd){REESTABLISH}: Destroying existing connection to server DRSPRO INFO ../rspro_client_fsm.c:307 RSPRO_CLIENT(bankd){REESTABLISH}: Creating TCP connection to server at 192.168.2.131:9999 DRSPRO ERROR ../rspro_client_fsm.c:360 RSPRO_CLIENT(bankd){REESTABLISH}: Event SRVC_E_KA_TERMINATED not permitted DRSPRO INFO ../rspro_client_fsm.c:364 RSPRO_CLIENT(bankd){REESTABLISH}: Destroying existing connection to server The display on the bankd side is 3512 DBANKDW INFO bankd_main.c:442 [000 CONN_WAIT_ID] Changing state to CONN_CLIENT 3512 DBANKDW INFO bankd_main.c:619 [000 CONN_CLIENT] No slotmap (yet) for client C(1:1) 3512 DBANKDW INFO bankd_main.c:450 [000 CONN_CLIENT] Changing state to CONN_CLIENT_WAIT_MAP (timeout=10) 3512 DBANKDW INFO bankd_main.c:967 [000 CONN_CLIENT_WAIT_MAP] Error -2 occurred: Cleaning up state 3512 DBANKDW INFO bankd_main.c:442 [000 CONN_CLIENT_WAIT_MAP] Changing state to ACCEPTING 3512 DBANKDW INFO bankd_main.c:955 [000 ACCEPTING] Accepted connection from 192.168.2.224:42813 3512 DBANKDW INFO bankd_main.c:442 [000 ACCEPTING] Changing state to CONN_WAIT_ID 3512 DBANKDW INFO bankd_main.c:655 [000 CONN_WAIT_ID] Rx RSPRO connectClientReq(T=0, N='openstick', SW='remsim-client', VER='1.0.0')
I want to use the method of exclusion. I want to make it clear that the name of my bankd is also in the csv file. Is it correct? Is there any problem with the configuration of bankd and client-st2? Also, when booting, does the content displayed by the client's linux mean that my mobile phone is not connected successfully?