Try traceroute -U {ip address} port 5198 and/or traceroute -U {ip address} port 5199 and/or traceroute -T {ip address} port 5200 My guess echolink servers are blocking ICMP pings. Google "Linux traceroute command" David -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson On Fri, Jul 20, 2018 at 5:41 PM, Mike <mm@midnighteng.com> wrote:

Do to the fact that some may have issues while others may not,

It should be considered that the DNS/routing issues as handled (and sometimes interrupted) by the ISP can also be a issue.

So, I might suggest when seeking help with echolink network issues, provide some additional data like DNS and ISP and perhaps we might see a link.

...mike/kb8jnm

On 7/20/2018 4:20 PM, Michael Wolthuis wrote:

John,

I have had all kinds of issues with Echolink’s nameservers in the last several weeks. I used to use server1, server2, server3, server4. However, Server2 and Server 3 have same IP address now. Not sur about all yours below, I didn’t look them up. However, I am having this issue on items that are regular Echolink as well – especially if coming from an AMPRNet IP address on the 44.x.x.x network.

It's time we all got together and built a user app around Allstar that can replace the Echolink client if you ask me.

Wish I had a solution, but I haven’t found a good one yet.

Mike

Kb8zgl

*From: *App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> <app_rpt-users-bounces@lists.allstarlink.org> on behalf of John Rudolph- N2YP <John@n2yp.com> <John@n2yp.com> *Reply-To: *Users of Asterisk app_rpt <app_rpt-users@lists. allstarlink.org> <app_rpt-users@lists.allstarlink.org> *Date: *Friday, July 20, 2018 at 4:11 PM *To: *"app_rpt-users@lists.allstarlink.org" <app_rpt-users@lists.allstarlink.org> <app_rpt-users@lists. allstarlink.org> <app_rpt-users@lists.allstarlink.org> *Subject: *Re: [App_rpt-users] Echolink timeout

I've tried pinging them all includeding echolink.org from my node server, my cellphone via WiFi, my cell via Verizon, my laptop and all my pings come back as 10,000+ ms pings or completely lost packets. I'm guessing this is causing the issue. If I use a website to do the ping it goes quick which I find interesting since I've tried it on two different networks, Spectrum-Time Warner and Verizon. Does anyone else this problem when trying to ping echolink? Is it possible it's a regional issue?

I've tried echolink.org, naeast.echolink. org, nasouth.echolink.org, servers.echolink.org, aprs.echolink.org. John Rudolph Amateur Radio Op N2YP Unadilla,NY

_______________________________________________ App_rpt-users mailing listApp_rpt-users@lists.allstarlink.orghttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/ cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.