[pskmail] Re: Aprs servers and the no beacon issue

  • From: Rein Couperus <rein@xxxxxxxxxxxx>
  • To: pskmail@xxxxxxxxxxxxx
  • Date: Thu, 12 Nov 2009 11:40:11 +0100

To enable the radio beacon in server 0.9.23 set $nosession = "none"; in 
The @Beaconarray = (1 0 0 0 1); sets the minutes (0, 1 2 3 4) you want the 
beacon to go out.

For port 14580 (filter) on aprs tier2 servers, you can set a filter for packet 
types. To filter 
message and position packets as used by pskmail aprs, you can set the filter to 
'filter t/pm".

look at arq.pm line 479:
                           print $handle_out "user $ServerCall pass $passw vers 
$Version filter t/pm\n";

The use of the filter is explained on: http://www.aprs-is.net/javAPRSFilter.aspx

Normally the use of port 1314 (message port) is o.k., and needs no extra filter.


Rein PA0R

PS: I will change this in the next server version.

> -----Ursprüngliche Nachricht-----
> Von: "Per Crusefalk" <per@xxxxxxxxxxxx>
> Gesendet: 12.11.09 09:37:01
> An: pskmail@xxxxxxxxxxxxx
> Betreff: [pskmail] Aprs servers and the no beacon issue

> Hi all,
> Just updated to 0.9.23 and connected that to ahubswe as usual.
> I had a "no connection" message there and the server would not beacon.
> I tried connecting xastir and got a similar problem (could not connect)
> and I started to look into it. It seems the procedure when connecting to
> aprs servers is changing, for ahubswe you have to connect to port 14580
> (only answers that port) and give it a filter. For xastir I use a range
> filter. Anyway, connecting the pskmail server to netherlands aprs server
> port 1314 worked and I got beacons again. I guess its an issue we may
> have to look into, if they change all the servers then we have to follow
> that new routine.
> 73 de Per, sm0rwo


Other related posts: