[App_rpt-users] Re :__Problems_with_Echolink

Doug Crompton doug at crompton.com
Thu Feb 13 08:25:47 UTC 2014


Torben,

   When your public IP address changes you should check your echolink database sometime after (15-30 minutes)  to see if the IP address for your node has changed to the new address. If it has then that would indicate that it is updating properly. If not then maybe there is a code problem with the IP address change. My public IP does not change so I do not see the problem. Also check the database for stations you cannot connect to. You could also do a check on a windows computer to compare the results. There are sites where you can enter echolink node numbers or calls and see if it is online and other details.

You could also detect the IP address change and restart asterisk shortly after in a script. Not the best solution but it might work.

Also I am sure you know this but you cannot use more than one echolink connection on one public IP address unless you use a proxy. The port forwarding is to only one computer behind your router and in this case it would be your Allstar server.
73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: torben at klimt-online.com
To: doug at crompton.com
Date: Thu, 13 Feb 2014 08:17:42 +0100
Subject: AW: [App_rpt-users] Re :__Problems_with_Echolink









hi doug,
i will try if the problem come the next time. i think the problem is that the "database" don`t update any more. here in europe we get a new IP Adress every 24h from our provider and if the database-update don`t run any more then i
 have wrong IPs to the Calls
so i find out that if i connect to Call DB0CUX i get an answer from VK2XYZ or... i hope i can explain the problem with my english :-/
 
greetings and many tnx for your help
 
 
 
 
 


Von: app_rpt-users-bounces at ohnosec.org [app_rpt-users-bounces at ohnosec.org] im Auftrag von Doug Crompton [doug at crompton.com]

Gesendet: Mittwoch, 12. Februar 2014 16:17

An: app_rpt-users at ohnosec.org

Betreff: Re: [App_rpt-users] Re :__Problems_with_Echolink






Torben,



  I went back and looked at your original message and you talked about a database problem. I messaged back the method to check the echolink database. Did you do that? Is the call/IP address of the echolink station you want to call in your local database? If
 you are not getting the database it isn't going to work.



echolink dbget c WA3DSP-L



The call has to be exact including case but you can do 



echolink dbdump  



to see the entire database. It is hard to see in the client mode so at linux prompt do...



asterisk -rx "echolink dbdump" | more 



or



asterisk -rx "echolink dbdump" > filename



to save it to a file for viewing.



73 Doug

WA3DSP

http://www.crompton.com/hamradio







From: torben at klimt-online.com

To: mike at midnighteng.com; app_rpt-users at ohnosec.org

Date: Wed, 12 Feb 2014 11:22:41 +0100

Subject: Re: [App_rpt-users] Re :__Problems_with_Echolink





possible is of course everything but i don`t think that there is any problem with the router software BUT we have many problems with the internetconnection at the repeater location. sometimes there
 is no more signal so we must restart the router/modem (all included; AVM Fritzbox)
 
any other ideas or issues to solve the prob ?


Von: app_rpt-users-bounces at ohnosec.org [app_rpt-users-bounces at ohnosec.org] im Auftrag von mike at midnighteng.com [mike at midnighteng.com]

Gesendet: Dienstag, 11. Februar 2014 19:23

An: app_rpt-users at ohnosec.org

Betreff: Re: [App_rpt-users] Re :__Problems_with_Echolink











Just a hunch here....



It kinda sounds like a router issue as strange as that may seem but not exactly the router...



Is there anything else on the network (computers) that could have a piece of malware on it ?



I have seen many a "unidentified malware" exploit router security and play with the router settings in router ram without writing them to NVRam. This type of malware eventually uses the host as a forwarding hub for data they have collected elsewhere to
 hide source of where it is going. While it it easy to find the infected computer, much harder to find the files on that computer. Keeping router firmware up to date or using a newer router can help.








Just a thought if you are unable to locate the problem.





...mike/kb8jnm






-------- Original Message --------

Subject: Re: [App_rpt-users] Re :__Problems_with_Echolink

From: Doug Crompton <doug at crompton.com>

Date: Tue, February 11, 2014 12:44 pm

To: "app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>




The command is  'echolink dbdump"



[root at WA3DSP_Allstar wa3dsp]# asterisk -rx "echolink dbdump" | grep WA3DSP



147090|WA3DSP-L|50.191.8.33


You can also use  dbget



WA3DSP_Allstar*CLI> echolink dbget c WA3DSP-L

147090|WA3DSP-L|50.191.8.33



To dump the entire database so you can look at it do



asterisk -rx "echolink dbdump" > echolink.txt



echolink.txt can be any filename and directory you want. Then do



less  echolink.txt



To look through the file.





73 Doug

WA3DSP

http://www.crompton.com/hamradio







Date: Tue, 11 Feb 2014 11:50:32 -0500

From: petem001 at hotmail.com

To: torben at klimt-online.com; 
app_rpt-users at ohnosec.org

Subject: [App_rpt-users] Re : Problems with Echolink




I have the same problem. 



--- Message initial ---



De : torben at klimt-online.com

Envoyé : 11 février 2014 07:40

A : app_rpt-users at ohnosec.org

Objet : [App_rpt-users] Problems with Echolink







hi all,

i have problems with echolink on my node. after running allstar more then xx days it is not possible to connect out but it is possible to connect the node. ithink there is a file / database with the information nodenumber/ip/call and that
 file is not up to date. after restarting allstarlink all is working well

 

any ideas ?

 

tnx 73 de torben dh6mbt





_______________________________________________ App_rpt-users mailing list 
App_rpt-users at ohnosec.org 
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit

http://ohnosec.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 at ohnosec.org 
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit

http://ohnosec.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 at ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users



To unsubscribe from this list please visit 
http://ohnosec.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 at ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.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.


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140213/11d0c02f/attachment.html>


More information about the App_rpt-users mailing list