Thanks for the help! That is the last missing piece I needed. I was trying to solve this mapping issue before by trying to direct the client manually to bankd, which caused my original post. Once you explained that the server was essentially "handing off" the registered IP address of bankd it all made sense.
All I needed to was add '-i 192.168.70.241' (i.e. the LAN if IP address) to my bankd command and it worked perfect!
All is behaving well now and thank you again for the support!
Cheers,
Paul
|
From: Harald Welte <laforge@osmocom.org>
Sent: Tuesday, April 26, 2022 11:58 AM
To: Paul Nederveen <pnederveen@eseye.com>
Cc: simtrace@lists.osmocom.org
Subject: Re: remsim unknwon RSPRO PDU type
Hi Paul,
On Mon, Apr 25, 2022 at 03:42:06PM -0000, pnederveen@eseye.com wrote:
> Thank you for the response Harald. I do not have everything set up to locally recreate the build. I used apt to update but the change is not getting pulled in yet.
yes, it is not yet reviewed/merged I guess. In any case, it just improves error reporting and doesn't change any functionality.
> @ubuntu:~$ sudo osmo-remsim-server
all good here
> @ubuntu:~$ sudo osmo-remsim-bankd -b 1 -n 1
also looks good
> The command on the RPi (no manual server port included this time)
>
> pi@raspberrypi:~ $ sudo osmo-remsim-client-st2 --usb-vendor 1d50
> --usb-product 60e3 --usb-path 1-1.3 --usb-interface 0 --usb-config 1
> --usb-altsetting 0 --client-id 1 --client-slot 0 --server-ip
> 192.168.70.241 DRSPRO INFO ../rspro_client_fsm.c:307
> RSPRO_CLIENT(server){REESTABLISH}: Creating TCP connection to server
> at 192.168.70.241:9998 DLINP NOTICE simtrace2_api.c:271 [0] <=
> osmo_st2_cardem_request_config(features=00000001)
> DLINP NOTICE input/ipa.c:128 192.168.70.241:9998 connection done
> DRSPRO NOTICE ../rspro_client_fsm.c:127
> RSPRO_CLIENT(server){REESTABLISH}: RSPRO link to 192.168.70.241:9998
> UP DRSPRO INFO ../rspro_client_fsm.c:307
> RSPRO_CLIENT(bankd){REESTABLISH}: Creating TCP connection to server at
> 127.0.0.1:9999
So what happens here is that
* bankd connects to server (via 127.0.0.1)
* server stores that bankd is at 127.0.0.1
* client connects to server (192.168.70.241:9998)
* server tells client to use bankd @ 127.0.0.1
* client tries to connect to bankd @ 127.0.0.1, which fails, as it is not on localhost
So the problem in your setup is mixing loopback addresses with routed network addresses.
In case of doubt, start with running bankd + server on separate machines, and see if that works. If it does, try to migrate the working configuration to something where multiple components run on the same machine, but without using non-routable IP addresses.
--
- Harald Welte <laforge@osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)