Re: [Svxlink-devel] Client can't reconnect when Relay/Proxy IP address changes

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

On Monday 03 March 2014 20:25:18 Jason Knight wrote:
> To add to this, I wanted to note that when operating either the Android or
> iPhone Echolink app, there are caveats.  When it runs in the background,
> and you switch back to open Echolink (running in the notification bar of
> Android, and background of iPhone), it will reconnect to the next nearest
> relay server.  It's just the nature of Echolink.  The same goes for using
> public proxies, it will randomly choose one each time.  Being that this is
> the nature of Echolink, this is a major problem in svxlink, and I'm
> surprised more users have not posted about this.  Maybe a lot of people are
> connecting to different Echolink nodes, but as for myself and my dad, we
> connect to one another constantly.  We will soon have node to node, and
> ultimately radio to radio communications going as soon as I get my node up,
> but for now I'm trapped with an Android only.  If I use my custom proxy
> that has a static pulic IP, I can continuously reconnect to the same node
> without problems.  The same would hold true for PC users, unless they are
> using direct mode, and even then many ISP's use dynamic IP addressing,
> though it doesn't change as often.  But if using relay or public proxy, you
> would see the same problem.

I guess this is a bigger problem than I thought it was, at least when using 
public proxies. Please report the problem in the SourceForge issue tracker so 
that it is not forgotten:

	http://sourceforge.net/p/svxlink/bugs/

73's de SM0SVX / Tobias

> 
> 
> 
> On Monday, March 3, 2014 2:50 PM, Jason Knight <n5...@ya...> wrote:
> 
> I'm following up an an email that was sent to the mailing list back in
> October of 2013 (see inline message).  I am having this issue with both
> 13.07 as well as 13.12.  The default connection type with Android is
> "relay", and I'm seeing this issue randomly, even after killing and
> restarting svxlink.  It seems to hold on to that old address for longer
> than 10 minutes as well.  Is there a way to force a refresh with the
> directory?  I have my own proxy server running with a static public IP
> address, that may be better for me to use since the IP doesn't change, but
> many people use relay, and the IP changes quite a bit, standard operation
> for Android.
> 
> 73's
> N5OJJ
> 
> On Saturday 12 October 2013 13:02:31 David McKenzie wrote:
> > Hi all,
> > 
> > I've run in to what looks like it may be a bug with the QSO registration.
> > I
> > am currently testing using version 13.07 and basic SimplexLogic simplex
> > node config. The client I am currently testing with is the Android version
> > of EchoLink. With the client application set to "relay" (which appears to
> > mean EL Proxy), I can connect successfully and everything seems to be
> > fine.
> > If I disconnect and try to reconnect later and it picks a different relay,
> > it appears that svxlink "remembers" the old IP address. I'm not sure if
> > the
> > mismatch is on the EchoLink server side or on the svxlink side, however.
> > If the IP address of an incoming connection does not match the one
> > registered
> in the EchoLink directory for the callsign, the connection will be rejected.
> SvxLink refresh the directory listing every ten minutes. The IP address for
> a station does not normally suddenly change but I guess SvxLink could be
> improved to cover this case as well. That should actually not be very hard
> to do since similar handling is already done for incoming connections for
> calls that are missing in the list. If a call is missing, a refresh is
> triggered. 73's de SM0SVX / Tobias >
> > Test steps and output:
> > 
> > 1. Install and configure EchoLink for Android
> > 2. Connect to my node:
> > 
> > Sat Oct 12 16:34:27 2013: Spurious audio packet received from 107.23.158.3
> > Sat Oct 12 16:34:27 2013: Incoming EchoLink connection from K1FSY (Dave)
> > at
> > 107.23.158.3
> > Sat Oct 12 16:34:27 2013: ### Delete K1FSY from watchlist
> > Sat Oct 12 16:34:27 2013: ### Register incoming station, count 1 of 3
> > possible number of connects
> > Sat Oct 12 16:34:27 2013: SimplexLogic: Activating module EchoLink...
> > Sat Oct 12 16:34:27 2013: K1FSY: Accepting connection. EchoLink ID is
> > 851853...
> > Sat Oct 12 16:34:27 2013: K1FSY: EchoLink QSO state changed to CONNECTED
> > Sat Oct 12 16:34:27 2013: Tx1: Turning the transmitter ON
> > Sat Oct 12 16:34:27 2013: --- EchoLink info message received from K1FSY
> > ---
> > Sat Oct 12 16:34:27 2013: Station K1FSY
> > Sat Oct 12 16:34:27 2013: Dave mobile
> > Sat Oct 12 16:34:27 2013:
> > Sat Oct 12 16:34:27 2013: Waterbury, Connecticut FN31
> > Sat Oct 12 16:34:27 2013:
> > Sat Oct 12 16:34:27 2013: K1FSY is running EchoLink for Android on a
> > samsung SCH-I535, with Android version 4.2.2.
> > Sat Oct 12 16:34:33 2013: Tx1: Turning the transmitter OFF
> > 
> > 3. Disconnect:
> > 
> > Sat Oct 12 16:35:15 2013: K1FSY: EchoLink QSO state changed to
> > BYE_RECEIVED
> > Sat Oct 12 16:35:15 2013: K1FSY: EchoLink QSO state changed to
> > DISCONNECTED
> > Sat Oct 12 16:35:15 2013: SimplexLogic: Deactivating module EchoLink...
> > 
> > 4. Uninstall and reinstall the app to make sure it picks a different
> > random
> > proxy from the pool
> > 5. Reconnect:
> > 
> > Sat Oct 12 16:59:23 2013: Spurious audio packet received from
> > 107.23.109.134 Sat Oct 12 16:59:23 2013: Incoming EchoLink connection
> > from K1FSY (samsung) at 107.23.109.134
> > Sat Oct 12 16:59:23 2013: *** WARNING: Ignoring incoming connection from
> > K1FSY since the IP address registered in the directory server
> > (107.23.146.139) is not the same as the remote IP address (107.23.109.134)
> > of the incoming connection
> > 
> > 
> > As you can see, it still knows about the "old" IP address. However, I
> > disconnect from the EchoLink servers and have to re-register to connect
> > after a fresh installation of the app on the phone. Also, if i kill
> > svxlink
> > and restart it w/o exiting the client on the phone (so that it uses the
> > same relay), it reconnects properly:
> > 
> > Sat Oct 12 16:59:46 2013: Spurious audio packet received from
> > 107.23.109.134 Sat Oct 12 16:59:46 2013: Incoming EchoLink connection
> > from K1FSY (samsung) at 107.23.109.134
> > Sat Oct 12 16:59:46 2013: ### Register incoming station, count 1 of 3
> > possible number of connects
> > Sat Oct 12 16:59:46 2013: SimplexLogic: Activating module EchoLink...
> > Sat Oct 12 16:59:46 2013: K1FSY: Accepting connection. EchoLink ID is
> > 851853...
> > Sat Oct 12 16:59:46 2013: K1FSY: EchoLink QSO state changed to CONNECTED
> > 
> > Question: Does svxlink cache the directory service information for a
> > client
> > or does it ask for it every time they try to connect? I believe the
> > directory service is being updated with the new relay IP every time I
> > connect, but I have not yet verified that. Anybody see any similar
> > behavior? Do I have something misconfigured?
> > 
> > Regards,
> > Dave K1FSY