Hi again,
On Mon, Apr 25, 2022 at 03:34:04PM +0200, Harald Welte wrote:
your remsim-server is running on port 9998 above, but
you're configuring remsim-client to connect to port
9999. I'm not sure about the IP addresses in your setup..
btw, the default listen port for the server is 9998 an the default --server-port
of the client is 9998, so if you don't specify the parameter, it will do the right
thing.
DRSPRO INFO
../rspro_client_fsm.c:307 RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to
server at 192.168.70.241:9999
DLINP NOTICE simtrace2_api.c:271 [0] <=
osmo_st2_cardem_request_config(features=00000001)
DLINP NOTICE input/ipa.c:128 192.168.70.241:9999 connection done
DRSPRO NOTICE ../rspro_client_fsm.c:127 RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to
192.168.70.241:9999 UP
DRSPRO ERROR remsim_client.c:121 RSPRO_CLIENT(server){CONNECTED}: Unknown/Unsupported
RSPRO PDU type: setAtrReq
This is because setAtrReq is permitted on the communication between
bankd and client, and not on the connection between server and client.
So you appear to have established the _control_ connection (between
client and server) to the bankd instead of the server.
The control connection between client and server will then, depending on
the current mappings configured, instruct the client to connect to the
bankd.
Admittedly, the error hadnling could be improved in this scenario. It's
just so "odd" to me that I had never thought of this ever occurring in
the first place :/
See
https://osmocom.org/issues/5548 +
https://gerrit.osmocom.org/c/osmo-remsim/+/27929
With that change it now logs the following in this situation:
DRSPRO ERROR remsim_client.c:105 RSPRO_CLIENT(server){ESTABLISHED}: Server connection to a
ComponentType(2) != RemsimServer? Check your IP/Port configuration
--
- Harald Welte <laforge(a)osmocom.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)