RE: remsim unknwon RSPRO PDU type

Hi Harald, 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 Paul Nederveen Director of Technical Consulting t: +1 484 935 3130 | m: +19196496363 | w: eseye.com LinkedIn | Twitter | YouTube | Blog This email is from Eseye . Address: 2880 Zanker Rd, Suite 203, San Jose, California, 95134, United States. Registered in England and Wales - number 06397669. VAT: GB921298326. ISO 27001: 2013 Certified. If you are not the intended recipient, please notify the sender and delete this email and any attachments. Eseye, AnyNet, AnyNet Secure and Eseye Logos are registered trademarks. 2020 Eseye Limited. All rights reserved. ​ -----Original Message----- From: Harald Welte <laforge(a)osmocom.org> Sent: Tuesday, April 26, 2022 11:58 AM To: Paul Nederveen <pnederveen(a)eseye.com> Cc: simtrace(a)lists.osmocom.org Subject: Re: remsim unknwon RSPRO PDU type Hi Paul, On Mon, Apr 25, 2022 at 03:42:06PM -0000, pnederveen(a)eseye.com wrote: yes, it is not yet reviewed/merged I guess. In any case, it just improves error reporting and doesn't change any functionality. all good here also looks good 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(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)