> Thank you very much, found it! I'll explain, maybe this solution is useful to
> someone. I need to reduce the time of reconnection because one of the
> internet connection is mobile phone. I have a private ip, the public IP is
> shared with others and I can not create the nat. To work around this
> problem, I created a reverse ssh from raspberry in this private network:
> ssh -N -R 45325:localhost:45325 user@... -p 44855
> In the configuration file remotetrx.conf of raspberry with a public IP, so
> it sets NetTx NetRx:
> HOST = 127.0.0.1
> TCP_PORT = 45325
> Thus it is established the connection between the two.
> I need to reduce the time because I implemented a control system ssh
> connection every 20 seconds, and even less. If for any reason the connection
> is lost, it recreates a new ssh connection in a short time. I want to
> reconnect remotetrx as quickly.
> Sorry for my English.
We have done that too and we solved it a different way:
We use OpenVPN to setup a VPN from the mobile system over the mobile network to the
repeater. The remote address of the OpenVPN connection is fixed by configuration on the
OpenVPN server (and the certificate used by the client).
Of course the issue arises when the mobile disconnects, then the OpenVPN reconnects,
and the svxlink connection has to be re-made when it has timed out in the meantime.
However, in practice when doing this, in main the network in our country, it does not occur that
often that you would have a problem with this.
We have a portable repeater setup we use on events and exhibitions, and it normally
stays connected for longer lengths of time (like hours). I know that this sometimes varies
between providers, I have experience with a cheaper mobile network where connections
seldomly last longer than 15-20 minutes before re-connecting and changing IP address.