Ok, so I give, how do you update the firmware on one of these? I have the same issue from time to time, what solves it is to point the rtcm to some fictitious IP address for about 3-5 minutes and then back to the correct address and then all will work just fine. What's odd about when it happens is that the packets are still coming to the allstar server, and being authenticated, but the rtcm never see them returned. I'm sure it has to do with the udp packet traversal stuff. Alan From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim Duuuude Sent: Monday, September 24, 2012 4:18 PM To: jeff.carrier@rmsmsecurity.com; app_rpt mailing list Subject: Re: [App_rpt-users] RTCM are you using the latest firmware and app_rpt sources from SVN?
Date: Mon, 24 Sep 2012 13:41:07 -0600 From: jeff.carrier@rmsmsecurity.com To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] RTCM
Can anyone provide any guidance on this issue?
<System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35) <System Time Not Set> ERROR! Host response timeout <System Time Not Set> Host Connection Lost (Pri) (10.0.0.35) <System Time Not Set> Host Connection established (Pri) (10.0.0.35)
I've changed the buflen parameter and still no joy. Ping times are no more than 150 ms between the server and rtcm.
Thanks K0JSC
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ramesh Dhami (VA3UV) Sent: Saturday, September 22, 2012 9:17 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Configuration of multiple nodes
On 22/09/2012 10:50 PM, Matthew Pitts wrote:
Good evening,
I will be using the ACID installation cd to set up my first permanent AllStar Link server and am wondering how to configure the system so that the hub node and its three branch nodes come up connected from the beginning. I have been running a single node in a virtual machine off and on for about a month now and uave most of the parts ready to do the live system. Feel free to give suggestions; I'm willing to learn the best way to do things, even though I've been around Linux almost 18 years.
<-- In the node stanza in rpt.conf add the following:
startup_macro=*5100
Then edit or create a new [macro] stanza - example:
[macro] 100 = *912329#
In this example, the node @ start-up will call macross 100; macro 100 creates a permanent link to node 2329. Since you want to link to 3 branch nodes, you can add multiple nodes in the macro - e.g:
100 = *912329*911200*911300#
HTH.
Cheers,
Ramesh. www.freestar.us
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (1)
-
Alan Adamson