Again, the large majority of ham EchoLink users in the world are on the commercial IP links and, on the contrary, very few 44net users/systems are using it. Now the failure is beyond of systems like the mine.
Problems and solutions described by Jann DG8NGN are very effective and should be followed by everyone.
Also, see another log coming from tests conducted by DG8NGN, in particular note the '*** WARNING' lines, then the simple solution appears that which use the a unique 44net to do the EchoLink job or for other Susop having good experience on networks to adapt their gateways to overcome this failure. i'm not experienced to help on this field.
------------ Tue May 15 09:29:01 2018: Incoming EchoLink connection from DG8NGN (Jann) at 44.130.120.3 Tue May 15 09:29:01 2018: *** WARNING: Ignoring incoming connection from DG8NGN since the IP address registered in the directory server (44.137.75.208) is not the same as the remote IP address (44.130.120.3) of the incoming connection Tue May 15 09:29:01 2018: Incoming EchoLink connection from DG8NGN (Jann) at 44.130.120.3 Tue May 15 09:29:01 2018: *** WARNING: Ignoring incoming connection from DG8NGN since the IP address registered in the directory server (44.137.75.208) is not the same as the remote IP address (44.130.120.3) of the incoming connection Tue May 15 09:29:06 2018: Spurious audio packet received from 44.130.120.3 Tue May 15 09:29:06 2018: Incoming EchoLink connection from DG8NGN (Jann) at 44.130.120.3 Tue May 15 09:29:06 2018: SimplexLogic: Activating module EchoLink... Tue May 15 09:29:06 2018: DG8NGN: Accepting connection. EchoLink ID is 4542... Tue May 15 09:29:06 2018: DG8NGN: EchoLink QSO state changed to CONNECTED Tue May 15 09:29:06 2018: Tx1: Turning the transmitter ON Tue May 15 09:29:12 2018: --- EchoLink info message received from DG8NGN --- Tue May 15 09:29:12 2018: Station DG8NGN Tue May 15 09:29:12 2018: Tue May 15 09:29:12 2018: Jann Tue May 15 09:29:12 2018: jn55lj Tue May 15 09:29:12 2018: Tue May 15 09:29:13 2018: Tx1: Turning the transmitter OFF Tue May 15 09:30:20 2018: DG8NGN: EchoLink QSO state changed to DISCONNECTED Tue May 15 09:30:20 2018: SimplexLogic: Deactivating module EchoLink...
73 and ciao, gus i0ojj/ir0aab
On 05/15/2018 01:17 PM, Tony Langdon wrote:
On 15/05/18 19:20, Jann Traschewski wrote:
On 15.05.2018 10:37, Tony Langdon wrote:
Info: IR0AAB-R is an Echolink Repeater on a "dual homed" system: Internet IP: 80.181.234.93 AMPRNet IP: 44.134.32.240 IR0AAB-R is registered to the Echolink System with 80.181.234.93
To me, this is the key to the problem.
The solution has been proposed with 44.190.0.0/16.
For this particular problem, a bit of a workaround. Because of the way Echolink works, no node should be listening on multiple IPs.