I tried to put the server on the public network, and the bankd end and my clients were on my intranet.
As shown below, my public network address is 45.135.135.32, my bankd-side intranet address is 192.168.2.224, and the client-side address is 192.168.2.173. My home broadband is 183.30.220.7I try to establish a connection.
root@lee:~# osmo-remsim-client-st2 -i 45.135.135.32 -V 1d50 -P 60e3 -C 1 -I 0 -H 1-1.2 -c 1 -n 1
DLINP NOTICE simtrace2_api.c:267 [0] <= osmo_st2_cardem_request_config(features=00000001)
DRSPRO INFO ../rspro_client_fsm.c:388 RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to server at 45.135.135.32:9998
DLINP NOTICE input/ipa.c:141 45.135.135.32:9998 connection done
DRSPRO NOTICE ../rspro_client_fsm.c:146 RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to 45.135.135.32:9998 UP
DMAIN INFO main_fsm.c:249 CLIENT_MAIN(main){UNCONFIGURED}: Rx configClientBankReq(183.30.220.7:9999 / B1:1)
DRSPRO INFO ../rspro_client_fsm.c:388 RSPRO_CLIENT(bankd){REESTABLISH}: Creating TCP connection to server at 183.30.220.7:9999
DRSPRO ERROR ../rspro_client_fsm.c:357 RSPRO_CLIENT(bankd){REESTABLISH_DELAY}: Event SRVC_E_KA_TERMINATED not permitted
Unable to establish connection
He has been connecting to my home broadband. How to solve this problem? Can anyone help? My dear friends!
Hello fellow SIM tracers,
I have my new incarnation of SIMtrace mostly working:
https://www.freecalypso.org/hg/simtrace-ice/
The Hg repository is named simtrace-ice, but the host program binaries
installed by the sw package are named simtrace3-*, following the
installed binary namespace usage convention established by previously
existing simtrace2-*.
Quoting from the README file at the top of the just-linked source
repository, FreeCalypso SIMtrace3 (aka SIMtrace-ice) is an alternative
implementation of Osmocom SIMtrace principal idea, using an iCE40 FPGA
instead of AT91SAMx MCU as the ISO 7816-3 sniffing receiver. The
signals going to the FPGA are outputs from a unidirectional voltage-
translating buffer (Nexperia 74LVC4T3144) whose inputs are connected
to the SIM interface being sniffed. The sniffing apparatus is thus
electrically clean, making only a Hi-Z connection to the SIM interface
being sniffed, and I expect it to work correctly with all voltages
from 1.8 to 5 V.
This new SIMtrace3 gadget is more than just a proposal - most parts of
it have already been implemented and proven working. The multivolt
sniffer board remains to be assembled/populated (I got the PCB and the
components on hand, I just need to make a visit to Technotronix to get
it assembled), but the FPGA gateware and the host programs receiving
and decoding the sniffed bits have already been proven working, using
an FCDEV3B forced into Class B voltage mode to work without the
mv-sniffer component.
The hardware setup is quite minimal: the FPGA board is off-the-shelf
Lattice iCEstick, readily available from various distributors, and the
SIMtrace3-specific custom hw bit will be reduced to just one very
simple board in the final version. The SIMtrace3 sniffer pod will
passively interconnect the SIM interface under study between the FPC
connector (existing SIMtrace FPC cables), a physical 2FF SIM socket
and the Hi-Z input pins of the dual-supply buffer, while the output
side of that buffer will go to header pins, to be connected to the
Icestick board. The 74LVC4T3144 buffer IC will be the only active
component on this board!
My initial emphasis is on sniffing, but my longer plans include cardem
too. I prefer having separate hw setups for the two functions, hence
my design calls for two separate "pod" boards, a sniffing pod and a
cardem pod. The cardem pod will be the sniffing pod (same multivolt
buffer, supporting all voltages) minus the SIM socket, plus a 74LVC1G07
OD buffer for driving the SIM I/O line from the FPGA-emulated card.
The FPGA gateware will of course be different too, but I expect it to
fit into the HX1K FPGA on the same iCEstick board.
It should also be noted that whether people like my design or not, the
name SIMtrace3 is now effectively claimed for this design whose
gateware and host software have already been implemented and whose hw
components are in the process of being finished and polished. If the
people behind SIMtrace1/2 (the original) totally dislike my idea and
would rather build some other successor to SIMtrace2, please call your
version SIMtrace4 - otherwise there will be two different designs each
claiming to be SIMtrace3, which won't help anyone.
M~
